TypeScript MongoDB
GraphQL Code Generator plugin for generating TypeScript types for MongoDB models. This plugin generates TypeScript types for MongoDB models, which makes it relevant for server-side development only. It uses GraphQL directives to declare the types you want to generate and use in your MongoDB backend.
- Version
- 4.0.2
- Weekly downloads
- 10k
- License
- MIT
- Updated
- Apr 19, 2026
Installation
npm i -D @graphql-codegen/typescript-mongodb
yarn add -D @graphql-codegen/typescript-mongodb
pnpm add -D @graphql-codegen/typescript-mongodb
bun add -D @graphql-codegen/typescript-mongodb
Config API Reference
dbTypeSuffix
type: string
Customize the suffix for the generated GraphQL types.
Default value: “DbObject”
dbInterfaceSuffix
type: string
Customize the suffix for the generated GraphQL interfaces.
Default value: “DbObject”
objectIdType
type: string
Customize the type of _id fields. You can either specify a type name, or specify module#type.
Default value: “mongodb#ObjectId”
idFieldName
type: string
Customize the name of the id field generated after using @id directive over a GraphQL field.
Default value: “_id”
enumsAsString
type: boolean
Replaces generated enum values with string.
Default value: “true”
avoidOptionals
type: boolean
This will cause the generator to avoid using TypeScript optionals (?),
so the following definition: type A { myField: String } will output myField: Maybe<string>
instead of myField?: Maybe<string>.
Default value: “false”
strictScalars
type: boolean
Makes scalars strict.
If scalars are found in the schema that are not defined in scalars
an error will be thrown during codegen.
Default value: “false”
defaultScalarType
type: string
Allows you to override the type that unknown scalars will have. Default value: “any”
scalars
type: object
Extends or overrides the built-in scalars and custom GraphQL scalars to a custom type.
namingConvention
type: object
Allow you to override the naming convention of the output.
You can either override all namings, or specify an object with specific custom naming convention per output.
The format of the converter must be a valid module#method.
Allowed values for specific output are: typeNames, enumValues.
You can also use “keep” to keep all GraphQL names as-is.
Additionally, you can set transformUnderscore to true if you want to override the default behavior,
which is to preserve underscores.
Available case functions in change-case-all are camelCase, capitalCase, constantCase, dotCase, headerCase, noCase, paramCase, pascalCase, pathCase, sentenceCase, snakeCase, lowerCase, localeLowerCase, lowerCaseFirst, spongeCase, titleCase, upperCase, localeUpperCase and upperCaseFirst
See more
Default value: “change-case-all#pascalCase”
typesPrefix
type: string
Prefixes all the generated types. Default value: ""
typesSuffix
type: string
Suffixes all the generated types. Default value: ""
skipTypename
type: boolean
Does not add __typename to the generated types, unless it was specified in the selection set.
Default value: “false”
nonOptionalTypename
type: boolean
Automatically adds __typename field to the generated types, even when they are not specified
in the selection set, and makes it non-optional
Default value: “false”
useTypeImports
type: boolean
Will use import type {} rather than import {} when importing only types. This gives
compatibility with TypeScript’s “importsNotUsedAsValues”: “error” option
Default value: “false”
inlineFragmentTypes
type: string
Whether fragment types should be inlined into other operations. “inline” is the default behavior and will perform deep inlining fragment types within operation type definitions. “combine” is the previous behavior that uses fragment type references without inlining the types (and might cause issues with deeply nested fragment that uses list types). “mask” transforms the types for use with fragment masking. Useful when masked types are needed when not using the “client” preset e.g. such as combining it with Apollo Client’s data masking feature. Default value: “inline”
emitLegacyCommonJSImports
type: boolean
Emit legacy common js imports.
Default it will be true this way it ensure that generated code works with non-compliant bundlers.
Default value: “true”
importExtension
type: object
Append this extension to all imports. Useful for ESM environments that require file extensions in import statements.
extractAllFieldsToTypes
type: boolean
Extract all field types to their own types, instead of inlining them. This helps to reduce type duplication, and makes type errors more readable. It can also significantly reduce the size of the generated code, the generation time, and the typechecking time. Default value: “false”
printFieldsOnNewLines
type: boolean
If you prefer to have each field in generated types printed on a new line, set this to true. This can be useful for improving readability of the resulting types, without resorting to running tools like Prettier on the output. Default value: “false”
includeExternalFragments
type: boolean
Whether to include external fragments in the generated code. External fragments are not defined in the same location as the operation definition. Default value: “false”
This plugin generates TypeScript types for MongoDB models, which makes it relevant for server-side development only. It uses GraphQL directives to declare the types you want to generate and use in your MongoDB backend.
What this plugin does?
Given the following GraphQL declaration:
We can have the following TypeScript output:
This interface can be used for db read/write purposes, thus making communication with the db much more consistent.
Usage Example
Once installed, add the directives’ declaration to your GraphQL Schema definition:
And generate code using gql-gen:
At this point, you can add the directives to your GraphQL definitions, and generate your MongoDB models file.
Directives
@entity(additionalFields: [AdditionalEntityFields]) (on OBJECT)
Use this directive to specify which GraphQL type should have generated MongoDB models.
embedded: Boolean- use this option to declare target entity as child of a greater entity. For example, given the following structure{ _id: string, username: string, profile: { name: string }}, the GraphQL typeProfileshould be declared as embedded.additionalFields: [AdditionalEntityFields]- specify any additional fields that you would like to add to your MongoDB object, and are not a part of your public GraphQL schema.
@column(overrideType: String) (on FIELD_DEFINITION)
Use this directive to declare a specific GraphQL field as part of your generated MongoDB type.
overrideType: String- use this to override the type of the field; for example, if you store dates asDatebut expose them asString.
@id (on FIELD_DEFINITION)
Use this directive on the filed that should be mapped to a MongoDB _id. By default, it should be
the id field of the GraphQL type.
@link (on FIELD_DEFINITION)
Use this directive to declare that a specific field is a link to another type in another table. This
will use the ObjectId type in the generated result.
@embedded (on FIELD_DEFINITION)
use this option to declare target entity as child of a greater entity.
@map(path: String) (on FIELD_DEFINITION)
Use this directive to override the path or the name of the target field. This would come in handy
whenever we would like to create a more complex object structure in the database; for example, if
you wish to project a field as username on your schema, but store it as credentials.username in
your DB. You can either specify the name of the field, or a path to which will lead to its
corresponding field in the DB.
Given the following GraphQL schema:
The output should be:
@abstractEntity(discriminatorField: String!) (on INTERFACE)
Use this directive on a GraphQL interface to mark it as a basis for other database types. The
discriminatorField argument is mandatory and will tell the generator what field name in the
database determines what interface the target object is implementing.
For example:
This way, you will get:
@union(discriminatorField: String) (on UNION)
This directive is similar to @abstractEntity, but for unions (that don’t necessarily have any
common fields). The discriminatorField argument is mandatory and will tell the generator what
field name in the database determines what interface the target object is implementing.
Given the following GraphQL schema:
The output should be:
Example
Given the following GraphQL types:
The generated MongoDB models should look like so: