npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

graphql-codegen-typescript-no-pascal-template

v0.10.10

Published

This template generates TypeScript typings for both client side and server side.

Downloads

12

Readme

TypeScript template

This template generates TypeScript typings for both client side and server side.

Generator Config

This generator supports custom config and output behavior. Use to following flags/environment variables to modify your output as you wish:

printTime (or CODEGEN_PRINT_TIME, default value: false)

Setting this to true will cause the generator to add the time of the generated output on top of the file.

prepend ( default value: null )

Will add the elements of this on top of the file.

    prepend: [
        "// My Comment",
        "// My Other Comment"
    ]

scalars ( default value: null )

Will map scalars to the predefined types

    scalars: {
        "Date": "Date"
    }

Combination of prepend and scalars

prepend and scalars options can be combined to map custom types to scalars.

    prepend: [
        "import { CustomScalarType } from './custom-types';"
        "import { AnotherCustomScalarType } from './another-custom-types';"
    ],
    scalars: {
        "CustomScalar": "CustomScalarType",
        "AnotherCustomScalar": "AnotherCustomScalarType"
    }

avoidOptionals (or CODEGEN_AVOID_OPTIONALS, default value: false)

This will cause the generator to avoid using TypeScript optionals (?), so the following definition: type A { myField: String } will output myField: string | null instead of myField?: string | null.

enumsAsTypes (or CODEGEN_ENUMS_AS_TYPES, default value: false)

Will generate the declared enums as TypeScript type instead of enums. This is useful if you can't use .ts extension.

immutableTypes (or CODEGEN_IMMUTABLE_TYPES, default value: false)

This will cause the codegen to output readonly properties and ReadonlyArray.

resolvers (or CODEGEN_RESOLVERS, default value: true)

This will cause the codegen to output types for resolvers.

noNamespaces (or CODEGEN_SCHEMA_NO_NAMESPACES, default value: null)

This will cause the codegen not to use namespace in typings

schemaNamespace (or CODEGEN_SCHEMA_NAMESPACE, default value: null)

This will cause the codegen to wrap the generated schema typings with a TypeScript namespace.

interfacePrefix (or CODEGEN_INTERFACE_PREFIX, default value: null)

This will cause the codegen to prefix graphql type interfaces with a value (if I is defined as prefix, type Foo will be generated as an interface named IFoo)

Use this feature if you need to run the codegen on multiple schemas, but getting a unified types (read more here)