NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm
npm, #4105 most downloaded on npm
Latest stable
8.0.0
Last release 15 days ago
07 Nov 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
8 years old
6242 releases · first in 2019
Drag across the ruler to compare, or tap a release to open it.
@graphql-codegen/visitor-plugin-common@8.0.0
@graphql-codegen/visitor-plugin-common@8.0.0
#11075
fa49a37
Thanks @eddeee888! - BREAKING CHANGE: GraphQL 14 and 15 are no
longer supported. The graphql peer dependency is now ^16.0.0 || ^17.0.0, so upgrade graphql
to version 16 or 17 before updating to this version.
#11075
fa49a37
Thanks @eddeee888! - BREAKING CHANGE: Node.js versions below
22.18.0 are no longer supported. Upgrade to Node.js 22.18.0 or later before updating to this
version.
#11075
fa49a37
Thanks @eddeee888! - generate() now returns
Promise<FileOutput[] | void> instead of Promise<FileOutput[] | any>. The result is no longer
any, so consumers using the result as an array must narrow it first.
Refs #11071
#11075
fa49a37
Thanks @eddeee888! - BREAKING CHANGE: Remove the deprecated
emitLegacyCommonJSImports config option and the --emit-legacy-common-js-imports CLI flag
Use importExtension (or --import-extension) to set the extension appended to relative imports.
When importExtension is not set, no extension is appended.
@graphql-codegen/plugin-helpers no longer exports normalizeImportExtension. Use
importExtension ?? '' instead.
Migration:
const config: CodegenConfig = {
- emitLegacyCommonJSImports: false,
+ importExtension: '.js',
};
#11075
fa49a37
Thanks @eddeee888! - BREAKING CHANGE: @graphql-tools/*
dependencies are updated to their latest majors, which require Node.js 22.18.0 or later and
GraphQL 16 or 17. If you import @graphql-tools/* packages in your own code, update them to the
same majors to avoid duplicate installs. @graphql-tools/code-file-loader@9 now extracts
#graphql-marked template literals by default, so code files that contain such templates can
produce newly found documents; check your generated output after upgrading. To keep the previous
behavior, set pluckConfig: { gqlHashComment: '' }.
#11075
fa49a37
Thanks @eddeee888! - BREAKING CHANGE - config.generates no
longer takes ConfiguredPlugin[], takes ConfiguredOutput[] instead
config.generates's previous typing allowed a value to be an array e.g.
generates: {
"src/gql/generated.ts": [{ typescript: {} }]
}
However, this never worked because this config is eventually passed into normalizeOutputParam
which previously had this bug in the implementation:
export function normalizeOutputParam(config) {
// 0. When config is an array...
if (isOutputConfigArray(config)) {
// 1. `isOutputConfigArray(config)` was `Array.isArray(config)` -> returns true
return {
documents: [],
schema: [],
plugins: isConfiguredOutput(config) ? config.plugins : config // 2. ‼️ `isConfiguredOutput(config)` was `typeof config === 'object'` -> returns true. This is a bug because we are accessing `plugins` property of an array, which will ALWAYS be `undefined` -> the output is always rejected as "Invalid Codegen Configuration"
}
}
if (isConfiguredOutput(config)) {
return config
}
throw new Error(`Invalid "generates" config!`)
}
Now, an array is still accepted, but as ConfiguredOutput[] instead. For this major version
release, only the first array element is used, and @graphql-codegen/cli logs a warning when
there is more than one element.
normalizeOutputParam now returns ConfiguredOutput[] instead of a single ConfiguredOutput.
@graphql-codegen/cli also throws its "Invalid Codegen Configuration" error when a generates
array is empty or its first element is not a config object. This error is now a single generic
message, no longer naming the output file, and it shows a TypeScript CodegenConfig example with
the ConfiguredOutput shape instead of the old YAML plugin-list example.
#11075
fa49a37
Thanks @eddeee888! - dependencies updates:
@graphql-tools/apollo-engine-loader@^9.0.2 ↗︎
(from ^8.0.38, in dependencies)@graphql-tools/code-file-loader@^9.0.3 ↗︎
(from ^8.1.41, in dependencies)@graphql-tools/git-loader@^9.0.3 ↗︎
(from ^8.0.44, in dependencies)@graphql-tools/github-loader@^10.0.3 ↗︎
(from ^9.1.11, in dependencies)@graphql-tools/graphql-file-loader@^9.0.2 ↗︎
(from ^8.1.22, in dependencies)@graphql-tools/json-file-loader@^9.0.2 ↗︎
(from ^8.0.36, in dependencies)@graphql-tools/load@^9.0.2 ↗︎
(from ^8.1.19, in dependencies)@graphql-tools/merge@^10.0.2 ↗︎
(from ^9.2.6, in dependencies)@graphql-tools/url-loader@^10.0.2 ↗︎
(from ^9.1.12, in dependencies)@graphql-tools/utils@^13.0.2 ↗︎
(from ^12.0.3, in dependencies)graphql-config@^6.0.0 ↗︎ (from
^5.1.8, in dependencies)graphql@^16.0.0 || ^17.0.0 ↗︎ (from
^0.8.0 || ^0.9.0 || ^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0 || ^15.0.0 || ^16.0.0 || ^17.0.0,
in peerDependencies)#11075
fa49a37
Thanks @eddeee888! - dependencies updates:
@graphql-tools/apollo-engine-loader@^9.0.2 ↗︎
(from ^8.0.38, in dependencies)@graphql-tools/code-file-loader@^9.0.3 ↗︎
(from ^8.1.41, in dependencies)@graphql-tools/git-loader@^9.0.3 ↗︎
(from ^8.0.44, in dependencies)@graphql-tools/github-loader@^10.0.3 ↗︎
(from ^9.1.11, in dependencies)@graphql-tools/graphql-file-loader@^9.0.2 ↗︎
(from ^8.1.22, in dependencies)@graphql-tools/json-file-loader@^9.0.2 ↗︎
(from ^8.0.36, in dependencies)@graphql-tools/load@^9.0.2 ↗︎
(from ^8.1.19, in dependencies)@graphql-tools/merge@^10.0.2 ↗︎
(from ^9.2.6, in dependencies)@graphql-tools/url-loader@^10.0.2 ↗︎
(from ^9.1.12, in dependencies)@graphql-tools/utils@^13.0.2 ↗︎
(from ^12.0.3, in dependencies)graphql-config@^6.0.0 ↗︎ (from
^5.1.8, in dependencies)graphql@^16.0.0 || ^17.0.0 ↗︎ (from
^0.8.0 || ^0.9.0 || ^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0 || ^15.0.0 || ^16.0.0 || ^17.0.0,
in peerDependencies)#11075
fa49a37
Thanks @eddeee888! - dependencies updates:
graphql-config@^6.0.0 ↗︎ (from
^5.1.8, in dependencies)Updated dependencies
[fa49a37,
fa49a37,
fa49a37,
fa49a37,
fa49a37,
fa49a37,
fa49a37,
fa49a37,
fa49a37,
fa49a37,
fa49a37,
409ffbf,
fa49a37,
fa49a37,
7366c63,
fa49a37,
fa49a37]:
Your coding agent can read these notes before it upgrades. Set up the MCP server →
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
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
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
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
@graphql-codegen/cli@7.4.6
@graphql-codegen/cli@7.4.6
#10985
d8aa07f
Thanks @eddeee888! - Build with strict: true, which changes
these emitted type declarations:
@graphql-codegen/cli: mkdirp returns Promise<string | undefined>, and the require (-r)
CLI option's default is typed never[] instead of any[].@graphql-codegen/visitor-plugin-common: BaseResolversVisitor and BaseTypesVisitor
SchemaDefinition()/SchemaExtension() return null instead of any.@graphql-codegen/visitor-plugin-common: BaseSelectionSetProcessor.typeCache is keyed by
Location | undefined.@graphql-codegen/visitor-plugin-common: SelectionSetToObject.buildSelectionSet returns
typeInfo as { name: string; type: string } | null.@graphql-codegen/visitor-plugin-common: getPossibleTypes accepts null as the type, which
graphql 15's schema.getType() can return.@graphql-codegen/visitor-plugin-common: removeDescription returns nodes with
description: undefined instead of any.@graphql-codegen/typescript: TsIntrospectionVisitor's constructor takes pluginConfig as
TypeScriptPluginConfig | undefined, DirectiveDefinition() returns null and
ObjectTypeDefinition() returns string | null.@graphql-codegen/client-preset: the babel preset accepts options as
ClientBabelPresetOptions | null | undefined.@graphql-codegen/testing: mockGraphQLServer returns nock.Scope | null.@graphql-codegen/graphql-modules-preset: a schema without extensions (graphql 15) throws the
"requires to use GraphQL SDL" error instead of a TypeError.Generated output is unchanged.
Updated dependencies
[d8aa07f]:
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
@graphql-codegen/cli@7.4.5
@graphql-codegen/cli@7.4.5
#11043
31761f9
Thanks @eddeee888! - dependencies updates:
@graphql-tools/apollo-engine-loader@^8.0.38 ↗︎
(from ^8.0.28, in dependencies)@graphql-tools/code-file-loader@^8.1.41 ↗︎
(from ^8.1.39, in dependencies)@graphql-tools/git-loader@^8.0.44 ↗︎
(from ^8.0.32, in dependencies)@graphql-tools/github-loader@^9.1.11 ↗︎
(from ^9.0.6, in dependencies)@graphql-tools/graphql-file-loader@^8.1.22 ↗︎
(from ^8.1.11, in dependencies)@graphql-tools/json-file-loader@^8.0.36 ↗︎
(from ^8.0.26, in dependencies)@graphql-tools/load@^8.1.19 ↗︎
(from ^8.1.8, in dependencies)@graphql-tools/merge@^9.2.6 ↗︎
(from ^9.2.4, in dependencies)@graphql-tools/url-loader@^9.1.12 ↗︎
(from ^9.0.6, in dependencies)@graphql-tools/utils@^12.0.3 ↗︎
(from ^11.2.0, in dependencies)graphql-config@^5.1.8 ↗︎ (from
^5.1.6, in dependencies)#11043
31761f9
Thanks @eddeee888! - Update @graphql-tools/utils to v12, and
other @graphql-tools/* dependencies and graphql-config to releases that use it, to pick up the
fix for GHSA-7mx3-vvmw-hjmv (prototype
pollution in mergeDeep, @graphql-tools/utils <= 12.0.0).
@graphql-codegen/cli now unwraps the AggregateError that newer @graphql-tools/load versions
throw, so schema and document syntax errors still print the native GraphQLError with its file
location.
Updated dependencies
[31761f9,
31761f9,
31761f9,
31761f9]:
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
@graphql-codegen/cli@7.4.4
@graphql-codegen/cli@7.4.4
#11025
43d0f65
Thanks @BuddhaBing! - Widen
Types.SchemaWithLoaderOptions['loader'] to accept a custom loader function
(CustomSchemaLoaderFn) in addition to a path string.
A per-entry schema custom loader ({ '<pointer>': { loader, ...options } }) is resolved by
@graphql-tools/load's useCustomLoader, which already accepts either a path string (resolved
via require()) or a function value at runtime (typeof loaderPointer === 'function'). Only the
TypeScript type restricted loader to string, forcing consumers who pass an imported loader
function (or a class instance exposing a bound loader property) to cast the schema array to
bypass the type error, even though it worked correctly at runtime.
This is additive and backward compatible — loader: string continues to type-check exactly as
before.
Also fixes a schema-cache collision for function loaders in @graphql-codegen/cli: the cache key
is JSON.stringify(schemaPointerMap), and JSON.stringify drops functions, so two generates
targets using different loader functions for the same pointer
({ 'schema.graphql': { loader: fnA } } vs { loader: fnB }) both keyed as
{"schema.graphql":{}} and the second silently reused the first's schema. Function values are now
keyed by object identity (via the existing getJsObjectId), so distinct loaders load separately
while one function reused across targets still loads once.
#11020
82ebbb5
Thanks @eddeee888! - Fix type errors in cli under
strict: true:
@graphql-codegen/cli: loadCodegenConfig returns Promise<LoadCodegenConfigResult | null>,
matching the null it resolves to when no config file is found. YamlCliFlags includes the
kebab-case ignore-no-documents, emit-legacy-common-js-imports and import-extension flags
that the CLI reads. CodegenContext.filepath is optional, and watch mode only watches the
config file when the context has a filepath. CodegenContext.getConfig() without an argument
returns Types.Config, and getConfig(extraConfig) returns T & Types.Config.
CodegenContext.checkModeStaleFiles is typed as string[]. Adds @types/yargs,
@types/babel__generator and @types/babel__template as dev dependencies.@graphql-codegen/plugin-helpers: normalizeInstanceOrArray and normalizeConfig accept
null and undefined, returning [].Generated output is unchanged.
Updated dependencies
[43d0f65,
82ebbb5,
e972b6d,
eae0e62,
1f7566f]:
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
One column per quarter.