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
Last release 13 days ago
08 Sep 2026
Ships fairly regularly
a new release about every 2 weeks
Nearly every release is documented
notes for 59 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
6 years old
3654 releases · first in 2020
One column per quarter.
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 fallback name-based matching in resolveExternalValue (introduced in #1557) incorrectly matched unrelated subschemas when neither had an explicit n
#2243 dff525f Thanks @qsona! - Fix redundant type merging calls when subschemas have no explicit name.
The fallback name-based matching in resolveExternalValue (introduced in #1557) incorrectly matched unrelated subschemas when neither had an explicit name set, because undefined === undefined evaluated to true. This caused type merging to trigger even when fetching a type directly from its source subschema, resulting in a redundant second call.
Nothing published for this version
Nothing published for this version
Updated dependencies [`d2bf6af`]:
d2bf6af]:
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
Do not try to resolve types from the subschemas which only have the stub types, for example if a subgraph only has id field as a stub, do not use that
da68d27 Thanks @ardatan! - - Optimizations to select ONLY required fields when fetching the missing fields from other subgraphs
id field as a stub, do not use that subgraph as a target subgraph for resolving the type, because it will not have any other fields than id.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
Updated dependencies [`08c9da2`]:
08c9da2]:
Nothing published for this version
Nothing published for this version
Updated dependencies [`dae3fe4`]:
#2099 dae3fe4 Thanks @copilot-swe-agent! - Fix missing NPM provenance attestation by enabling npmPublishProvenance in Yarn configuration
Updated dependencies [dae3fe4]:
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 - #2022 `43aaa6a` Thanks @ardatan! - Fix redundant extra calls to the same subschema in case of @canonical annotation
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
When you have an argument in a nested field that uses the variable from the gateway request like below;
#1971 4065b7f Thanks @ardatan! - Reuse the existing variables from the gateway request correctly
When you have an argument in a nested field that uses the variable from the gateway request like below;
query GetArticles($date: Datetime!) {
view {
articlesByDate(date: $date) {
id
title
publishedAt
}
}
}
And if Datetime is renamed from DateTime in the original schema, the transform wasn't applied correctly to the variable definitions, and the delegation failed with an error in the subgraph like Datetime is not known.
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 →