@graphql-tools/graphql-tag-pluck

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.

Minor Changes

• Recognize #graphql at the start of template literals by default.

  Until now, untagged template literals were only plucked when they had a leading block comment such as /* GraphQL */ (gqlMagicComment). Many setups instead use a #graphql marker inside the string:

  export const typeDefs = `#graphql
    type Query {
      hello: String
    }
  `

  That marker is GraphQL source text, not a JavaScript leading comment, so gqlMagicComment could never see it. Without extraction, loaders fall back to importing the module, which stays cached under GraphQL Codegen --watch and leaves generated types stale.

  This release adds gqlHashComment (default: 'graphql'):

  • #graphql is recognized out of the box

  • set gqlHashComment: 'gql' (or any other value) for markers like #gql

  • set gqlHashComment: '' to disable hash-comment detection

  /* GraphQL */ via gqlMagicComment and the isGqlTemplateLiteral / pluckStringFromFile hooks keep working as before.

Patch Changes

• dependencies updates:

  • Updated dependency @babel/core@^8.0.7 ↗︎ (from ^7.29.7, in dependencies)

  • Updated dependency @babel/parser@^8.0.7 ↗︎ (from ^7.29.3, in dependencies)

  • Updated dependency @babel/traverse@^8.0.7 ↗︎ (from ^7.26.10, in dependencies)

  • Updated dependency @babel/types@^8.0.6 ↗︎ (from ^7.26.10, in dependencies)

  • 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/utils@^12.0.4 ↗︎ (from ^12.0.3, in dependencies)

Patch Changes

• dependencies updates:

  • Removed dependency @babel/plugin-syntax-import-assertions@^7.26.0 ↗︎ (from dependencies)

• Parse with Babel importAttributes (and deprecatedAssertSyntax so existing assert { … } files still work), and drop the unused @babel/plugin-syntax-import-assertions dependency. Fixes #5454.