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
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.0
@graphql-tools/utils@12.0.0
#8346
2273c21
Thanks @ardatan! - This release adds GraphQL v17 support and aligns
the existing executor implementation with the latest GraphQL v17 API changes. The following
changes are included:
getAsyncHelpers is now available on GraphQLResolveInfo. Its track method is used whenever
waitUntil is available, as in Yoga's
Explicit Resource ManagementgetAbortSignal is now available on GraphQLResolveInfo, matching behavior that was already
available in this executor implementation, as in Yoga's
Execution CancellationGraphQLResolveInfo automatically aligns variableValues according to the GraphQL version for
better compatibility. In GraphQL v17 and above, variableValues follows the wrapped shape
({ coerced, sources }) expected by GraphQL APIs. In GraphQL v16 and below, variableValues
remains a flat map as in previous versions.__serialize and __parseValue, they are automatically
mapped to coerceOutputValue and coerceInputValue in GraphQL v17.@graphql-tools/executor's getVariableValues now returns { variableValues }
on success, where variableValues is a VariableValues object ({ coerced, sources }). On
failure, it returns { errors }.collectFields, shouldIncludeNode, getDeferValues, and collectSubFields now
need a VariableValues object instead of Record<string, any> for the variableValues
argument.visitResult now internally normalizes ExecutionRequest.variables into a
VariableValues-compatible shape ({ coerced, sources }) before traversing selections.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
### Patch Changes - #8302 `e90719b` Thanks @pbomb! - fix mergeDeep to treat explicit undefined property values as overrides rather than skipping them,
Nothing published for this version
### Patch Changes - #8204 `615c1a2` Thanks @pbomb! - fix mergeDeep to treat null property values as explicit overrides rather than skipping them
Nothing published for this version
Nothing published for this version
### Minor Changes - #8226 `2609c94` Thanks @eddeee888! - getDocumentNodeFromSchema: Add arg defaultValue support for graphql@17
2609c94
Thanks @eddeee888! - getDocumentNodeFromSchema: Add arg
defaultValue support for graphql@17Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Previously the output accumulator was only initialized inside the per-key loop, so merging sources with no own keys (e.g. mergeDeep([{}, {}])) left it
#8256
981d461
Thanks @twavv! - Fix mergeDeep returning undefined instead of {}
when merging two or more empty objects.
Previously the output accumulator was only initialized inside the per-key loop, so merging sources
with no own keys (e.g. mergeDeep([{}, {}])) left it undefined. This silently dropped
empty-object values during nested merges ({ data: {} } became { data: undefined }), which
could surface as "Cannot return null for non-nullable field" errors when stitching schemas. The
accumulator is now initialized as soon as an object source is encountered.
### Minor Changes - #8144 `a4b7dce` Thanks @enisdenjo! - Deep merge and preserve non-enumerable symbols
a4b7dce
Thanks @enisdenjo! - Deep merge and preserve non-enumerable
symbolsNothing published for this version
`ae36a0e` Thanks @mattkrick! - Handle enum values correctly if they are arguments of directives defined in the extensions
ae36a0e
Thanks @mattkrick! - Handle enum values correctly if they are
arguments of directives defined in the extensionsOne column per quarter.