NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm, #1448 most downloaded on npm
Common package containing utils and types for GraphQL tools
Latest stable
13.2.2
Last release 12 days ago
10 Nov 2026
Ships fairly regularly
a new release about every 9 days
Nearly every release is documented
notes for 60 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
7 years old
2013 releases · first in 2020
Drag across the ruler to compare, or tap a release to open it.
Nothing published for this version
Nothing published for this version
Nothing published for this version
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
@graphql-tools/utils@12.1.0
@graphql-tools/utils@12.1.0
#8445 82457d1 Thanks @ardatan! - Fix: Preserve symbol-keyed GraphQL extensions when building, merging, or extracting schemas.
GraphQL.js v17 allows string | symbol keys on schema/type/field extensions (via toObjMapWithSymbols). @graphql-tools was dropping those symbol keys in two places:
mergeDeep only walked enumerable string keys (for...in), so symbol extensions were lost when applying schemaExtensions.extractExtensionsFromSchema did not copy non-enumerable own symbol keys (enumerable symbols already survive object rest/spread; the explicit loop covers the non-enumerable case).import { makeExecutableSchema } from '@graphql-tools/schema'
const META = Symbol('META')
const schema = makeExecutableSchema({
typeDefs: /* GraphQL */ `
type Query {
hello: String
}
`,
schemaExtensions: {
schemaExtensions: {
[META]: { source: 'app' },
tagged: true,
},
types: {},
},
})
// Before: only string keys survived
// schema.extensions === { tagged: true }
// After: symbol keys are preserved
// schema.extensions[META] === { source: 'app' }
// schema.extensions.tagged === true
Schema extension merge/extract and resolver merging always enable { enumerable: true, nonEnumerable: true } so symbol keys survive in tools' own merge/extract paths on every supported GraphQL.js major. (GraphQL.js itself may still drop symbol keys from field configs below v17 when rebuilding types.)
mergeDeep APImergeDeep now accepts an options object. The old positional boolean arguments still work but are deprecated.
import { mergeDeep } from '@graphql-tools/utils'
// Deprecated (still supported)
mergeDeep([a, b], false, true, false, true)
// ^proto ^arrays ^len ^non-enumerable symbols only
// Preferred
mergeDeep([a, b], {
respectPrototype: false,
respectArrays: true,
respectArrayLength: false,
respectSymbols: {
enumerable: true, // merge `obj[sym] = value` keys
nonEnumerable: true, // copy defineProperty(..., { enumerable: false }) symbols
},
})
respectSymbols defaults to { enumerable: false, nonEnumerable: false } (symbols dropped), matching the historical default. The legacy 5th positional flag still maps to { nonEnumerable: true } only.
Resolver map types (IResolvers / field resolver extensions and type __extensions) now use ExtensionsObject (Record<string | symbol, any>), so symbol-keyed resolver extensions type-check under GraphQL.js v17+.
#8513 98673c3 Thanks @ardatan! - fix(utils): coerce GraphQL 17 argument defaults in getArgumentValues via local input coercion (defaults, missing variables, nested sources)
#8493 a75d725 Thanks @cpruijsen! - Keep argument types of defined directives when pruning so that unused directives such as @key(fields: _FieldSet!) retain their full definitions instead of losing the argument together with its type.
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
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-tools/utils@12.0.4
Nothing published for this version
Nothing published for this version
@graphql-tools/utils@12.0.3
Nothing published for this version
Nothing published for this version
@graphql-tools/utils@12.0.2
@graphql-tools/utils@12.0.2
#8456 b1fbba2 Thanks @renovate! - dependencies updates:
@whatwg-node/promise-helpers@^2.0.0 ↗︎ (from ^1.0.0, in dependencies)#8467 20d36a5 Thanks @ardatan! - Fix prototype pollution in mergeIncrementalResult
Path segments are now rejected unless they are primitive strings or numbers, and keys named __proto__, constructor or prototype are still blocked. Previously a non-primitive segment such as ["__proto__"] bypassed the string equality guard and was coerced into a write on Object.prototype.
Also exports shared isSafeObjectKey / isDangerousObjectKey helpers used by this path walker and other package call sites. @graphql-tools/merge and @graphql-tools/mock are patched so they ship with the new imports; updateInternalDependencies raises their utils floor when 12.0.2 is versioned.
Nothing published for this version
One column per quarter.