NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm
npm, #3292 most downloaded on npm
A set of utils for faster development of GraphQL tools
Latest stable
12.3.3
Last release 12 days ago
10 Nov 2026
Ships fairly regularly
a new release about every 2 weeks
Nearly every release is documented
notes for 60 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
7 years old
3721 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
Nothing published for this version
@graphql-tools/delegate@12.3.3
@graphql-tools/delegate@12.3.3
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/delegate@12.3.2
@graphql-tools/delegate@12.3.2
9877255]:
Nothing published for this version
Nothing published for this version
@graphql-tools/delegate@12.3.1
@graphql-tools/delegate@12.3.1
#2687 aabe28a Thanks @ardatan! - Deliver forwarded @defer patches for nested list items and avoid recursion through wrapSchema over a stitched schema
When a subschema has defer: true, deferred fields inside list items were resolved as null: IncrementalReceiver did not merge patches into existing list items (including nested lists), and when the subgraph sent several patches in one chunk, every re-emitted patch carried the chunk's hasNext: false, so only the first one was applied.
Without defer: true, a deferred field owned by another inner subschema under wrapSchema over a stitched schema called defaultMergedResolver on the nested schema with the same parent and recursed. Re-fetch via the nested merged-type resolver for the field owner instead.
#2701 a558eea Thanks @ardatan! - Settle unsatisfiable stitched leftover fields instead of hanging
When a merged field could only be fetched with a merge key that never
arrived, leftover resolution returned a deferred promise that never
settled and the request hung idle. Track leftover work and, once the
queue is empty, reject unsettled deferreds with SATISFIABILITY_ERROR
(Apollo composition-style message, including selection snippet and
subschema names when set).
Closes #2695
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/delegate@12.3.0
@graphql-tools/delegate@12.3.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.
#2666 127576a Thanks @enisdenjo! - dependencies updates:
@repeaterjs/repeater@^3.0.6 ↗︎ (from dependencies)#2671 cd30482 Thanks @ardatan! - Fix type merging for unions queried with inline fragments (graphql-tools#4965 / #4966).
Typical setup: one subschema returns a stub member (StubMajor { id }) while another resolves the real union members via @merge:
# students
union Major = StubMajor
type StubMajor { id: String! }
# majors
type Query {
major(id: String!): Major @merge(keyField: "id")
}
union Major = MajorSuccess | MajorError
Client query:
major {
... on MajorSuccess { id name }
... on MajorError { id code }
}
Three problems stacked:
@merge on a union only registered concrete members (MajorSuccess / MajorError), not Major itself, so a StubMajor result never triggered merge.MergedTypeInfo was not built for union types, and planners assumed object/interface getFields().id) on a union into ... on StubMajor { id } returned an array from the FIELD visitor; graphql-js visit nests that array as one selection instead of splicing it, so execution ignored the fragment and the merge key was never queried (major(id: $id) ran with empty variables).Fixes:
@merge as well as concrete members.This goes beyond the schema-extension workaround discussed on the issue.
Updated dependencies [680eb53, 62175b8, 680eb53, befdb8e]:
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/delegate@12.2.1
@graphql-tools/delegate@12.2.1
#2644 abf4091 Thanks @enisdenjo! - Fix compatibility with GraphQL 14 and 15 by avoiding runtime access to the OperationTypeNode enum, which is only available in GraphQL 16 and later
Closes #2643
Nothing published for this version
One column per quarter.