@graphql-tools/mock

Minor Changes

• Query and Mutation mocks now receive the field's resolved arguments. Subscription mocks receive the same map when resolve runs (an event is yielded); the default subscriber does not yield.

  A mock is a type factory, not a resolver. The value that identifies an operation field is its argument map after GraphQL coercion: user(id: ID!) always has id, whether the client sent a literal or a variable. That is what you assert on (jest.fn() / toHaveBeenCalledWith) and what you use to return the right mock.

  context is the same request-wide object for every field (auth, loaders). It does not distinguish user(id: "1") from user(id: "2"). Use the resolvers option of addMocksToSchema when you need context, info, or the mock store; the rest of the fields can still come from mocks.

  mocks.Query = jest.fn(() => ({ ... })) is called with { id: 'user-1' } when user(id:) is resolved. Nested type mocks such as User stay factories with no arguments.

• Lists generated by the mock store can set a length with defaultListLength, and MockList now passes each item's index to its mock function.

  Without an explicit list mock the store always produced two items. addMocksToSchema({ schema, defaultListLength: 0 }) (or createMockStore) now controls that length. Auto-generated list items pass their index to scalar mocks, and new MockList(n, (index) => ...) receives index so items can vary by position.

• MockStore get and set now accept GraphQL input object types.

  Input types were rejected as "not an object or interface", so mutation inputs could not be stored for later CRUD-style mocks. The store now treats input objects like other named object types.

Patch Changes

• Mocks set on list items now apply to fields that take arguments.

  The store keys a field with its arguments (membership:{"param":"test"}). Nested mocks such as { membership: null } were stored under the bare field name, so a query that passed arguments generated a new default instead of using the override. Lookups now fall back to the un-argued field when the exact argument key is missing.

Major Changes

• breaking

  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).

  • Dev tooling and @graphql-tools/graphql-tag-pluck move to Babel 8 (@babel/core / parser / traverse / types).

  • The standalone 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).

Removed @graphql-tools/utils exports

inspect and the WeakMap memoize1…memoize2of5 helpers remain on @graphql-tools/utils (inspect is no longer re-exported from cross-inspect).

File matching (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:

• On Node.js ≥26.1 (and ≥24.16 where backported), fs.glob followSymlinks is used.

• On older engines, symlink directories are discovered only under each pattern’s literal prefix (not the whole cwd) and patterns are re-rooted.

• Non-recursive / literal patterns skip the symlink walk entirely.

@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.

Errors and other cleanup

• Prefer new GraphQLError(message, options) from graphql. Experimental schema coordinate support remains on locatedError / relocatedError / getSchemaCoordinate.

• Removed GraphQL versions older than 16 compatibility branches (error construction, validation rule name suffixes, URL.canParse fallback).

• Promise helpers should be imported from @whatwg-node/promise-helpers (handleMaybePromise, isPromise, fakePromise, mapAsyncIterator, MaybePromise) rather than re-exported from utils.

Patch Changes

• dependencies updates:

  • Updated dependency graphql@^16.0.0 || ^17.0.0 ↗︎ (from ^14.0.0 || ^15.0.0 || ^16.0.0 || ^17.0.0, in peerDependencies)

Patch Changes

• dependencies updates:

  • Updated dependency @graphql-tools/schema@^10.1.4 ↗︎ (from ^10.1.3, in dependencies)

  • Updated dependency @graphql-tools/utils@^12.0.4 ↗︎ (from ^12.0.3, in dependencies)

Patch Changes

• security

  Fix prototype pollution in mergeIncrementalResult

  Path segments are now rejected unless they are primitive strings or numbers, and keys named __proto__, constructor or prototype are still blocked. Previously a non-primitive segment such as ["__proto__"] bypassed the string equality guard and was coerced into a write on Object.prototype.

  Also exports shared isSafeObjectKey / isDangerousObjectKey helpers used by this path walker and other package call sites. @graphql-tools/merge and @graphql-tools/mock are patched so they ship with the new imports; updateInternalDependencies raises their utils floor when 12.0.2 is versioned.

Patch Changes

• Pass resolverValidationOptions through from addMocksToSchema to addResolversToSchema.