NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm
npm, #3061 most downloaded on npm
A set of utils for faster development of GraphQL tools
Latest stable
3.6.1
Last release 12 days ago
10 Nov 2026
Ships fairly regularly
a new release about every 4 weeks
Rarely documented
notes for 13 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
4 years old
2327 releases · first in 2022
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
Nothing published for this version
@graphql-tools/executor-http@3.6.1
@graphql-tools/executor-http@3.6.1
e288224 Thanks @enisdenjo! - dependencies updates:
@graphql-tools/utils@^12.1.0 ↗︎ (from ^12.0.1, in dependencies)Updated dependencies [e288224]:
Nothing published for this version
@graphql-tools/executor-http@3.6.0
@graphql-tools/executor-http@3.6.0
#2717 cc5870d Thanks @enisdenjo! - Add deduplicateInflightRequestsPerContext option to the HTTP executor
When true (default), inflight requests are deduplicated only within the same context object. When false, identical requests are deduplicated across different contexts within the same executor.
Hive Gateway's HTTP transport sets it to false so that identical subgraph requests coming from different clients are deduplicated.
Nothing published for this version
Nothing published for this version
Nothing published for this version
@graphql-tools/executor-http@3.5.1
@graphql-tools/executor-http@3.5.1
4a2d3b6 Thanks @enisdenjo! - Deduplicate inflight requests only within the same executor and the same context
The fetch implementation receives the request context and may handle each request differently, so identical requests with different contexts or from different executors are no longer deduplicated together.
Nothing published for this version
Nothing published for this version
Nothing published for this version
@graphql-tools/executor-http@3.5.0
@graphql-tools/executor-http@3.5.0
#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.
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
Nothing published for this version
Nothing published for this version
@graphql-tools/executor-http@3.4.1
@graphql-tools/executor-http@3.4.1
#2485 47fe3d6 Thanks @adam-drag! - Release the connection when an SSE subscription is torn down
handleEventStreamResponse called reader.releaseLock() on normal teardown,
which detaches the reader but leaves the response body un-cancelled, so the
underlying HTTP connection was never released and the socket stayed open until
the process exited. Long-running consumers accumulated one leaked connection per
disposed subscription.
It now calls reader.cancel(), which propagates cancellation and closes the
connection. The error path already used cancel(); only the normal path did not.
Closes https://github.com/graphql-hive/gateway/issues/2486
Nothing published for this version
Nothing published for this version
Nothing published for this version
@graphql-tools/executor-http@3.4.0
@graphql-tools/executor-http@3.4.0
#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)Updated dependencies [ee4cc07, ee4cc07]:
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Add the useContentTypeForGETRequests opt-in for GET requests that need content-type: application/json compatibility.
#2334 0f8706c Thanks @copilot-swe-agent! - Add useGETForHashedQueries support for downstream APQ requests so hash-only
query probes can use GET while full-query fallbacks continue to use POST.
Add the useContentTypeForGETRequests opt-in for GET requests that need
content-type: application/json compatibility.
One column per quarter.