npm / @graphql-tools/merge
@graphql-tools/merge
What changed in @graphql-tools/merge 7 to 10, from its official release notes, upgrade guides and advisories. Sources checked 2026-11-13.
8 breaking1 deprecations1 new APIs and options3 fixes and other
See which of these apply to your code, ranked, in your agent:
npx @unstale/cli init@graphql-tools/merge 102 changes
Breaking changes 2
GraphQL v14/v15 support is dropped; the graphql peer range is now ^16.0.0 || ^17.0.0.
Node.js >=22.18.0 is required.
@graphql-tools/merge 94 changes
Breaking changes 1
Node 14 support is dropped; Node.js >= 16 is required.
Deprecations 1
mergeDeep accepts an options object; the old positional boolean arguments still work but are deprecated.
Fixes and other changes 2
Resolver map types use ExtensionsObject, allowing symbol-keyed resolver extensions to type-check under GraphQL.js v17+.
Schema extension merge/extract and resolver merging preserve symbol-keyed extensions, including non-enumerable symbols.
@graphql-tools/merge 86 changes
Breaking changes 4
NamedDefinitionNode, resetComments, collectComment, pushComment, and printComment moved from @graphql-tools/merge to @graphql-tools/utils.
Moved mergeSchemas from @graphql-tools/merge to @graphql-tools/schema to prevent a circular dependency.
Removed mergeSchemasAsync.
Moved MergeSchemasConfig from @graphql-tools/merge to @graphql-tools/schema to prevent a circular dependency.
New APIs and options 1
Added the schemaExtensions option to mergeSchemas, makeExecutableSchema, and stitchSchemas configurations.
Fixes and other changes 1
Comments are ignored while merging directives.
@graphql-tools/merge 71 changes
Breaking changes 1
The type signature and generic parameters of mergeResolvers changed, which may require updates to existing usage.