graphql-js
graphql-js copied to clipboard
graphql
A reference implementation of GraphQL for JavaScript
With the current code that doesn't define export mapping modern tooling such as vitest v1.6.0 tries to access the CJS version of GraphQL in my project (https://github.com/favware/graphql-pokemon) because it doesn't...
One of the issues we uncovered in https://github.com/graphql/graphql-js/issues/3648 is that upgrading to ES6 output maintained the `for..of` and array destructuring in our bundles which leads to a pretty considerable performance...
This is a writeup to discuss this problem in the GraphQL-WG and the GraphQL-JS-WG. Please give feedback in either of those meetings, or here in the issue, until the next...
Related to the issue in https://github.com/graphql/graphql-js/issues/3968, it doesn't appear that the introspection query is selecting the `isOneOf` field from the server, as defined by the [RFC](https://github.com/graphql/graphql-spec/pull/825/files#diff-30a69c5a5eded8e1aea52e53dad1181e6ec8f549ca2c50570b035153e2de1c43). This has downstream effects...
Submitting here as an issue to reference it in the [next WG agenda](https://github.com/graphql/graphql-js-wg/blob/main/agendas/2024/04-Apr/24-graphql-js-wg-april-2024.md). ### Some historical context puzzle pieces: * [deploy full ESM with "type": "module" in "latest-esm" npm tag...
now that filtering has been removed from #4026, this draft PR could be checked out to see what it would look like to reintroduce it.
by hoisting streamUsage checks out of the loop, requires introducing two versions of the looping functions depends on #4052