NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm, #3292 most downloaded on npm
A set of utils for faster development of GraphQL tools
Latest stable
12.3.3
Last release 10 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.
Previously, when a subgraph declared @provides(fields: "...") on a field, the gateway would still:
#2351 0bbdbbc Thanks @ardatan! - Fix @provides so the gateway only requests the provided fields the client actually selected, and stops delegating to the owner subgraph when @provides already covers the request.
Previously, when a subgraph declared @provides(fields: "...") on a field, the gateway would still:
@provides to that subgraph, even when the client never asked for them.@provides-covered fields whenever the providing subgraph declared them as @external, even though the data was already returned.For example with:
# subgraph B (provider)
type Query {
entity: Entity @provides(fields: "name description")
}
type Entity @key(fields: "id") {
id: ID!
name: String! @external
description: String! @external
}
a client query of { entity { id name } } would still cause the gateway to ask subgraph B for description and fetch name again from subgraph A (the owner of Entity).
After this fix:
@provides fields the client actually selected are forwarded to the providing subgraph (request side).@provides declarations at every nested level (e.g. @provides(fields: "nested { nestedNested { name description } }")) and @provides declarations made via inline fragments on union/interface members (e.g. @provides(fields: "... on Book { title }")), so the gateway no longer round-trips to the owner subgraph for fields that the providing subgraph has already returned.@provides-covered fields. Previously, using a fragment spread (e.g. ...MyFrag) for nested @external fields could cause an unnecessary delegation to the owner because selection subtraction compared only the spread name with the explicit @provides fields. The planner now resolves fragment spreads before subtracting provided selections, while preserving the fragment type condition and directives when only part of a fragment remains.Aliases, direct field selections, fragments, fragment spreads, @include/@skip directives wrapping a @provides field, and nested @provides selections are preserved without unnecessary owner delegations.
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
Updated dependencies [`4311d79`]:
4311d79]:
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
The fix in extractUnavailableFieldsFromSelectionSet within extractUnavailableFields.ts now preserves the fragment wrapper and type condition, so concr
#2382 3e774e0 Thanks @gonzo-32! - Fix cross-subgraph delegation for unavailable fields selected through inline fragments or fragment spreads on interface fields.
The fix in extractUnavailableFieldsFromSelectionSet within extractUnavailableFields.ts now preserves the fragment wrapper and type condition, so concrete-type fields do not lose their type context and get treated as missing.
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
Two bugs were addressed in delegateRequest:
#2320 deafdc0 Thanks @copilot-swe-agent! - Fix @stream directive not working for federated subgraphs with non-null scalar list return types.
Two bugs were addressed in delegateRequest:
isListType was called without first unwrapping NonNull, so a field typed [String!]! (a NonNull(List(...))) was not recognised as a list. The fix wraps the check with getNullableType().
Deduplication of already-pushed stream items used a WeakSet, which throws a TypeError for primitive values (strings, numbers, etc.). This was replaced with an integer index counter that works for both object and primitive list items.
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
One column per quarter.