Last release 2 days ago
01 Sep 2026
Release timing varies
gaps range from 8 days to 6 weeks
Nearly every release is documented
notes for 60 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
7 years old
6097 releases · first in 2019
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.
Nothing published for this version
Nothing published for this version
b18a0319f
Thanks @renovate! - dependencies updates:
@whatwg-node/fetch@^0.3.0 ↗︎ (from
^0.2.3, in dependencies)Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
6c7d3e54b]:
1c7a8c0ad
Thanks @charlypoly! - fix(ci): regression on error outputNothing published for this version
Nothing published for this version
#8189
b408f8238
Thanks @n1ru4l! - Fix CommonJS TypeScript resolution with
moduleResolution node16 or nodenext
Updated dependencies
[b408f8238]:
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
@whatwg-node/fetch to fix vulnerabilityNothing published for this version
.js extension.Nothing published for this version
Nothing published for this version
Nothing published for this version
--check cli flag--verbose and --debug flags68bb30e19: Attach .js extension to imports starting with either a . or / character.
d84afec09: Support TypeScript ESM modules ("module": "node16" and "moduleResolution": "node16").
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
2cbcbb371: Add new flag to emit legacy common js imports. Default it will be true this way it ensure that generated code works with non-compliant bundlers.
You can use the option in your config:
schema: 'schema.graphql'
documents:
- 'src/**/*.graphql'
emitLegacyCommonJSImports: true
Alternative you can use the CLI to set this option:
$ codegen --config-file=config.yml --emit-legacy-common-js-imports
32c1560f1: getPluginByName fails unexpectedly when plugin is not prefixed with @graphq-codegen in ESM context
MODULE_NOT_FOUND is the error code you receive in a CommonJS context when you require() a module and it does not exist. ERR_MODULE_NOT_FOUND is the error code you receive in an ESM context when you import or import() ad module that does not exist.
Updated dependencies [2cbcbb371]
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
tslib as a dependency. See https://github.com/dotansimha/graphql-code-generator/issues/8075Nothing published for this version
Nothing published for this version
d84afec09: Add bin CLI command for running graphql-code-generator in ESM mode. You can now use graphql-codegen-esm instead of graphql-codegen.
GraphQL Code Generator will continue supporting both ESM and CommonJS in parallel.
d84afec09: Support TypeScript ESM modules ("module": "node16" and "moduleResolution": "node16").
8e44df58b: Add new config option to not exit with non-zero exit code when there are no documents.
You can use this option in your config:
schema: 'schema.graphql'
documents:
- 'src/**/*.graphql'
ignoreNoDocuments: true
Alternative you can use the CLI to set this option:
$ codegen --config-file=config.yml --ignore-no-documents
e7870ac28: Fix security vulnerability by removing latest-version dependency.
dce40edeb: Allow to disable watch mode from CLI to overwrite the config. Now you can do:
$ graphql-codegen --watch=false
2e86ecb65: ### Summary
listr2listrlistr is not actively maintained and we have to maintain our custom renderer for it to display errors. Migrating to listr2 it just works out of the almost similar to how it was working in past and is a actively maintained.
Big change for us is how errors were collected. In listr errors were thrown and were caught in the end function of our custom listr Renderer but with listr2 we don't really get Error in end function always so instead we use the context to collect errors from all the tasks and then show them after all the tasks are finished.
Updated dependencies [d84afec09]
Updated dependencies [a4fe5006b]
Updated dependencies [8e44df58b]
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version