NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm, #1448 most downloaded on npm
Common package containing utils and types for GraphQL tools
Latest stable
13.2.2
Last release 12 days ago
10 Nov 2026
Ships fairly regularly
a new release about every 9 days
Nearly every release is documented
notes for 60 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
7 years old
2013 releases · first in 2020
Drag across the ruler to compare, or tap a release to open it.
Nothing published for this version
@graphql-tools/utils@13.1.2
@graphql-tools/utils@13.1.2
#8558 501109b Thanks @ardatan! - printSchemaWithDirectives no longer turns unquoted directive argument literals into strings.
In GraphQL SDL, an unquoted identifier in value position is an EnumValue AST node. A quoted value is a StringValue. Those are different kinds even when the argument type is a custom scalar rather than an enum type. parseLiteral on that scalar receives the original kind, so a custom scalar can treat argument_value and "argument_value" as different inputs.
The printer was reconstructing directive arguments from JS values. valueFromASTUntyped maps both kinds to the same string, and astFromValue then emits a StringValue. The printed SDL became @directive(arg: "argument_value") even though the schema AST still had @directive(arg: argument_value).
That is a round-trip / fidelity bug: loaders, schema diffs, snapshots, and subgraph publishes see different SDL, and a scalar that distinguishes the two kinds changes meaning. Default scalars coerce both to the same JS string, so many runtime paths do not notice.
When the original AST is still the source of truth, printSchemaWithDirectives now keeps those directive argument nodes, including nested list and input-object values. If directive values are supplied only through extensions (code-first), JS strings are still printed as strings because the original kind is not available.
Fixes #8557
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
@graphql-tools/utils@13.1.1
@graphql-tools/utils@13.1.1
#8552 f87bdf4 Thanks @ardatan! - INCREMENTAL_DELIVERY_SPECS is the shared HTTP contract for incrementalSpec. Each row maps an Accept / Content-Type parameter (deferSpec=20220824, incrementalSpec=v0.2, ...) to the executor payload id ('v0.1' | 'v0.2').
GraphQL Yoga, Hive Gateway, HTTP executors, and other servers should look up this table instead of hardcoding spec strings. When a later incremental spec ships, the work stays in graphql-tools: add a row here and an executor publisher. Consumers bump @graphql-tools/utils / @graphql-tools/executor. Accept negotiation, Content-Type echo, and 406 for unknown spec params keep working without a Yoga / Gateway / executor-http patch for the new identifier.
Unknown values for a registered parameter name stay unsupported (HTTP 406). Helpers: lookupIncrementalDeliverySpec, getMultipartContentType, getDefaultIncrementalDeliverySpec, getIncrementalSpecParameterNames.
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
Field execution, @defer / @stream scheduling, and AbortSignal cancellation are shared. Spec-specific JSON is built by a publisher: v0.1 still yields {
#8550 4db5750 Thanks @ardatan! - @graphql-tools/executor can publish both incremental delivery payload formats from one execution kernel. Pass incrementalSpec: 'v0.1' | 'v0.2' on execute / subscribe / normalizedExecutor (also on ExecutionRequest for executorFromSchema). 'v0.1' remains the default and keeps the existing path / label patches used with multipart/mixed;deferSpec=20220824. 'v0.2' emits Apollo incremental v0.2 payloads (pending with id and path, incremental with id and optional subPath, completed) used with multipart/mixed;incrementalSpec=v0.2.
Field execution, @defer / @stream scheduling, and AbortSignal cancellation are shared. Spec-specific JSON is built by a publisher: v0.1 still yields { incremental, hasNext }; v0.2 assigns ids when a pending group is first announced, groups streamed items under one pending path, and reports completion separately. Nested @defer patches are collected as children of the parent patch so v0.2 can announce the inner fragment only after the parent is pending, without making the nested fragment wait on the parent's promise (v0.1 sibling completion is unchanged aside from incremental array order).
Publisher state (Map / Set of ids) is allocated only for 'v0.2'. StreamGroup is created only for v0.2 and only when items are actually streamed. v0.2 stream completion uses an open-count on the group instead of scanning subsequentPayloads.
mergeIncrementalResult still merges v0.1 path / items patches. For v0.2 it records pending ids on the execution result, writes deferred data at pending.path + subPath, appends streamed items onto the list at pending.path, and folds completed.errors into errors. visitResult flattens nested deferred patches so result visiting still sees fields that live under a child @defer.
Nothing published for this version
Nothing published for this version
Nothing published for this version
@graphql-tools/utils@13.0.2
@graphql-tools/utils@13.0.1
@graphql-tools/utils@13.0.1
#8540 15efe55 Thanks @ardatan! - Align memoize4 third-level cache initialization with the let + reassignment pattern used by memoize3 / memoize5.
Previously a nested const cache4 inside if (!cache4) shadowed the outer binding. Runtime behavior was already safe (that branch stores the map and returns), but the declaration was easy to misread and fragile if the early return were removed. The helper now assigns to the outer let cache4 instead, with regression tests for the third-level cache path.
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/utils@13.0.0
@graphql-tools/utils@13.0.0
#8515 1d70c62 Thanks @ardatan! - Drop GraphQL v14/v15 support and require Node.js >= 22.18.
graphql peer range is now ^16.0.0 || ^17.0.0.engines.node is now >=22.18.0 (Node fs.glob + Babel 8).@graphql-tools/graphql-tag-pluck move to Babel 8 (@babel/core / parser / traverse / types).cross-inspect package is discontinued. Use inspect from @graphql-tools/utils instead (Node util.inspect via process.getBuiltinModule, with a small JSON.stringify / String fallback).@graphql-tools/utils exports| Removed | Use instead |
|---|---|
getArgumentValues |
import { getArgumentValues } from 'graphql' |
coerceInputs / graphqlJSCompat |
graphql@16+ APIs (getArgumentValues, etc.) |
createDeferred / createDeferredPromise |
const { promise, resolve, reject } = Promise.withResolvers() |
createGraphQLError |
new GraphQLError(message, options) from graphql |
mapMaybePromise |
handleMaybePromise from @whatwg-node/promise-helpers |
isPromise / fakePromise / mapAsyncIterator / MaybePromise |
@whatwg-node/promise-helpers |
registerAbortSignalListener / getAbortPromise |
AbortSignal APIs (throwIfAborted, addEventListener('abort', …, { once: true }), AbortSignal.any, …) |
withCancel / getAsyncIterableWithCancel / getAsyncIteratorWithCancel |
Handle cancellation on the async iterator’s return() (or your transport abort path) |
debugTimerStart / debugTimerEnd |
Your own timing / console.time if needed |
PromiseWithResolvers (type) |
Built-in PromiseWithResolvers<T> / return type of Promise.withResolvers() |
inspect and the WeakMap memoize1…memoize2of5 helpers remain on @graphql-tools/utils (inspect is no longer re-exported from cross-inspect).
globby → fs.glob)Loaders and @graphql-tools/load-files now use Node’s fs.glob through:
import { matchFiles, matchFilesSync } from '@graphql-tools/load-files';
Directory symlinks are followed for recursive (**) patterns:
fs.glob followSymlinks is used.cwd) and patterns are re-rooted.@graphql-tools/executor hot-path caches (collectSubfields, argument coercion, @stream detection) use memoize2 / memoize3 from utils. collectSubFields in utils stays unmemoized so the executor can own a single memoize3 layer.
new GraphQLError(message, options) from graphql. Experimental schema coordinate support remains on locatedError / relocatedError / getSchemaCoordinate.URL.canParse fallback).@whatwg-node/promise-helpers (handleMaybePromise, isPromise, fakePromise, mapAsyncIterator, MaybePromise) rather than re-exported from utils.1d70c62 Thanks @ardatan! - dependencies updates:
@graphql-typed-document-node/core@^3.2.0 ↗︎ (from ^3.1.1, in dependencies)cross-inspect@1.0.1 ↗︎ (from dependencies)graphql@^16.0.0 || ^17.0.0 ↗︎ (from ^14.0.0 || ^15.0.0 || ^16.0.0 || ^17.0.0, in peerDependencies)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.