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
Last release today
23 Sep 2026
Release timing varies
gaps range from 8 days to 3 months
Nearly every release is documented
notes for 60 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
4 years old
905 releases · first in 2022
One column per quarter.
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 [`6f3776c`]:
6f3776c]:
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)
}
}
2118a80]:
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
Updated dependencies [`2fe123a`]:
2fe123a]:
Nothing published for this version
Updated dependencies [`dddc5f6`]:
dddc5f6]:
Nothing published for this version
Nothing published for this version
Updated dependencies [`fbb58b5`]:
fbb58b5]:
Updated dependencies [`fd105f4`, `fded91e`, `3b99a9b`]:
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
Your coding agent can read these notes before it upgrades. Set up the MCP server →