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
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
POTENTIAL BREAKING CHANGE: This can be a breaking change because now the schema above will be printed as the input, previously extend schema was conve…
#7685
6f3776c
Thanks @ardatan! - Support "federation/subgraph style" schemas in
astFromSchema and printSchemaWithDirectives
If a GraphQLSchema doesn't have any defined operation types, we should print the schema
definition as an extension rather than omitting it entirely. They are not a valid schema on their
own, but they are valid subgraph schemas in a federation setup, and it is possible to build such
schemas with assumeValid options.
// A schema without defined root types
buildSchema(
/* GraphQL */ `
extend schema @link(url: "https://specs.apollo.dev/federation/v2.0", import: ["@key"])
type User @key(fields: "id") {
id: ID!
username: String
}
`,
{ assumeValid: true, assumeValidSDL: true }
)
POTENTIAL BREAKING CHANGE: This can be a breaking change because now the schema above will be
printed as the input, previously extend schema was converted to schema {}.
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
This new feature is opt-in, you have to enable it using schemaCoordinateInErrors executor option.
#7588
2118a80
Thanks @EmrysMyrddin! - Add optional schema coordinate in error
extensions. This extension allows to precisely identify the source of the error by automated tools
like tracing or monitoring.
This new feature is opt-in, you have to enable it using schemaCoordinateInErrors executor
option.
Caution: This feature, when enabled, will expose information about your schema. If you need to keep your schema private and secret, you should strip this attribute at serialization time before sending errors to the client.
import { parse } from 'graphql'
import { normalizedExecutor } from '@graphql-tools/executor'
import { getSchemaCoordinate } from '@graphql-tools/utils'
import schema from './schema'
const result = await normalizedExecutor({
schema,
document: parse(`...`),
schemaCoordinateInErrors: true // enable adding schema coordinate to graphql errors
})
if (result.errors) {
for (const error of result.errors) {
console.log('Error in resolver ', error.coordinate, ':', error.message)
// or with `getSchemaCoordinate` util, to workaround types if needed
console.log('Error in resolver', getSchemaCoordinate(error), ':', error.message)
}
}
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
### Patch Changes - #7683 `2fe123a` Thanks @ardatan! - Revert https://github.com/ardatan/graphql-tools/pull/7683 which can cause unexpected breaking c
Nothing published for this version
If a GraphQLSchema doesn't have any defined operation types, we should print the schema definition as an extension rather than omitting it entirely. T
#7679
dddc5f6
Thanks @ardatan! - Support "federation/subgraph style" schemas in
astFromSchema and printSchemaWithDirectives
If a GraphQLSchema doesn't have any defined operation types, we should print the schema
definition as an extension rather than omitting it entirely. They are not a valid schema on their
own, but they are valid subgraph schemas in a federation setup, and it is possible to build such
schemas with assumeValid options.
// A schema without defined root types
buildSchema(
/* GraphQL */ `
extend schema @link(url: "https://specs.apollo.dev/federation/v2.0", import: ["@key"])
type User @key(fields: "id") {
id: ID!
username: String
}
`,
{ assumeValid: true, assumeValidSDL: true }
)
Nothing published for this version
Nothing published for this version
`fbb58b5` Thanks @ardatan! - Remove \dset\ dependency
When the schema is like following;
#5269
fded91e
Thanks @uroslates! - Add default values to the arguments
When the schema is like following;
type Query {
getAllPages(currentPage: Int = 0, pageSize: Int = 10, pageType: getAllPages_pageType = ContentPage, sort: String = "asc"): PagesList
}
enum getAllPages_pageType {
ContentPage
CategoryPage
CatalogPage
}
type PagesList {
...
}
The generated operation will be like following;
query getAllPages_query($currentPage: Int = 0, $pageSize: Int = 10, $pageType: getAllPages_pageType = ContentPage, $sort: String = "asc") {
getAllPages(currentPage: $currentPage, pageSize: $pageSize, pageType: $pageType, sort: $sort) {
...
}
}
#7012
fd105f4
Thanks @ardatan! - Fix the bug in mergeDeep;
The following inputs and outputs are corrected;
mergeDeep([{a:2}, undefined]) - Any nullish values should be ignored so it should return
{a:2}mergeDeep([]) - no sources should return undefinedmergeDeep([undefined]) - no sources should return undefinedNothing 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.