NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm, #3076 most downloaded on npm
Fork of GraphQL.js' execute function
Latest stable
4.1.8
Last release 12 days ago
10 Nov 2026
Ships fairly regularly
a new release about every 8 days
Nearly every release is documented
notes for 60 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
4 years old
1184 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
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
Updated dependencies [`501109b`]:
501109b]:
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 - #6790 `d54bc77` Thanks @n1ru4l! - Executor now collects @defer fields the way graphql-js 17 IncrementalExecutor does: overlapping
d54bc77 Thanks @n1ru4l! - Executor now collects @defer fields the way graphql-js 17 IncrementalExecutor does: overlapping fields execute once in the parent group instead of again in the deferred patch. Subsequent payloads only contain fields that were not already delivered. When a field is nulled by error bubbling, deferred and streamed work at or under that path is cancelled (and ancestor patches that would write into the nulled subtree are dropped), matching graphql-js 17 hasNulledPosition. Default / non-incremental execution still uses the previous collect 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
Updated dependencies [`f87bdf4`]:
f87bdf4]:
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.
4db5750]:
Nothing published for this version
Nothing published for this version
Nothing published for this version
Updated dependencies [`34b740b`]:
34b740b]:
Updated dependencies [`15efe55`]:
15efe55]:
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
Execution now calls graphql-js directly for variable coercion (including GraphQL 17 SDL input-field defaults on omitted variables). The maintained for
#8536 875d060 Thanks @ardatan! - BREAKING: stop exporting getVariableValues from @graphql-tools/executor. Use graphql's getVariableValues instead.
Execution now calls graphql-js directly for variable coercion (including GraphQL 17 SDL input-field defaults on omitted variables). The maintained fork and helpers (values.ts, validateInputValue, etc.) were removed.
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 peer range is now ^16.0.0 || ^17.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.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.