NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm
npm, #2780 most downloaded on npm
A set of utils for faster development of GraphQL tools
Latest stable
10.3.2
Last release 13 days ago
09 Nov 2026
Release timing varies
gaps range from 8 days to 3 months
Nearly every release is documented
notes for 59 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
6 years old
1932 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
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
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
`e288224` Thanks @enisdenjo! - dependencies updates:
e288224 Thanks @enisdenjo! - dependencies updates:
@graphql-tools/utils@^12.1.0 ↗︎ (from ^12.0.1, in dependencies)Nothing published for this version
Nothing published for this version
@graphql-tools/batch-execute@10.3.1
@graphql-tools/batch-execute@10.3.1
9877255 Thanks @enisdenjo! - Batch only requests that share the same context in createBatchingExecutorNothing published for this version
Nothing published for this version
Nothing published for this version
@graphql-tools/batch-execute@10.3.0
@graphql-tools/batch-execute@10.3.0
#2680 680eb53 Thanks @ardatan! - # Execution cancellation on batched requests
When using Batched Execution, it is now possible to cancel the entire batched request if all individual requests' AbortSignals are aborted. This enhancement improves resource management and responsiveness in applications that utilize batched GraphQL operations.
Previously, aborting individual requests did not affect the batched request. With this update, if all individual requests signal an abort, the batched request will also be aborted, ensuring that unnecessary processing is avoided.
This feature is implemented using the new utility function abortSignalAll, which combines multiple AbortSignal instances into a single signal. If all of the individual signals are aborted, the combined signal will also be aborted, allowing for more efficient cancellation handling in batched operations.
#2672 befdb8e Thanks @ardatan! - Support @defer / @stream incremental delivery within schema stitching.
Gateway-owned @defer (default): deferred selections are omitted from subgraph requests (only @requires / key dependencies are kept), so nested @defer can flush before slow fields resolve. Missing fields are filled later via type-merging or source resolvers.
Subgraph-forwarded @defer: set defer: true on a SubschemaConfig (or defer: true on getStitchedSchemaFromSupergraphSdl) to forward @defer to that subgraph and merge incremental patches via IncrementalReceiver. With batch: true and batchingOptions.defer (or subschema.defer), multi-request batches wrap each root selection in @defer for subgraph compatibility; results are still collected before DataLoader waiters resolve. Single-request batches pass the AsyncIterable through so the initial payload can flush before deferred patches arrive.
Hive Gateway config: extend deferStream instead of a separate flag:
deferStream: true // client-facing only (gateway-owned omit)
deferStream: { subgraph: true } // also forward @defer to every subgraph
deferStream: { subgraph: { users: true, '*': false } } // per-subgraph
@graphql-tools/executor-http adds mergeIncremental (default true: legacy growing snapshots). Set mergeIncremental: false to yield raw multipart parts like the default schema executor. Hive Gateway's @graphql-mesh/transport-http always uses passthrough (mergeIncremental: false).
IncrementalReceiver prefers raw patches and cheaply tolerates accumulated snapshots (only fills missing keys). The HTTP executor preserves hasNext in accumulate mode.
@stream continues to be forwarded on field directives as before. List streaming in @graphql-tools/delegate uses a plain async generator (no @repeaterjs/repeater dependency).
Hive Router runtime does not plan incremental delivery yet; deferStream.subgraph applies to the stitching federation path.
#2680 680eb53 Thanks @ardatan! - dependencies updates:
@graphql-hive/signal@^2.0.0 ↗︎ (to dependencies)62175b8 Thanks @enisdenjo! - Use semver dependencies matched by minor
Updated dependencies [680eb53]:
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
Preserves GraphQL 16 compatibility while upgrading to @graphql-tools/utils v12, @graphql-tools/executor v2, and the compatible @graphql-tools/schema a
#2604 ee4cc07 Thanks @enisdenjo! - Support GraphQL 16 with @graphql-tools/utils v12
Preserves GraphQL 16 compatibility while upgrading to @graphql-tools/utils v12, @graphql-tools/executor v2, and the compatible @graphql-tools/schema and @graphql-tools/merge releases. Consumers now receive consistent resolver and execution request types without conflicts between different GraphQL Tools versions.
Stitched and delegated operations handle the new executor variable result shape correctly, including variables used by directives. Resolver execution also supports the executor's cancellation and asynchronous work helpers while remaining compatible with the GraphQL 16 GraphQLResolveInfo API.
#2604 ee4cc07 Thanks @enisdenjo! - dependencies updates:
@graphql-tools/utils@^12.0.1 ↗︎ (from ^11.0.0, in dependencies)Nothing published for this version
Nothing published for this version
Nothing published for this version
Per the GraphQL spec a non-nullable field returning null should propagate to the parent, in this case it should propagate to data. Batched sub-request
#2545 8cbdfd0 Thanks @omahili! - Fixes #1288.
Per the GraphQL spec a non-nullable field returning null should propagate to the parent, in this case it should propagate to data. Batched sub-requests share one merged document so null should propagate to every result and not just the one whose fields actually failed.
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
One column per quarter.