graphql-js
graphql-js copied to clipboard
graphql
A reference implementation of GraphQL for JavaScript
Context: I wanted to try more automatic alternative to #3687 that allows us to continue using ES6 features without perfomance lost.
This PR aims to explain what's going on for #3648 the main issues seem to be: - using `for..of` in hot paths - using array destructuring If we find this...
## Description Currently while validating graphql, the parent type is not specified in the error message when validation fails due to a missing type. Without the parent name this can...
This is really a continuation of @daniel-nagy's work in https://github.com/graphql/graphql-js/pull/2871 and, more distantly, @sam-swarr's initial AST implementations in https://github.com/graphql/graphql-js/pull/1141, as well as @josephsavona and the entire Relay team's work from...
As it seems right now graphql-js 17 will ship without a commonjs solution. Since ESM modules can only be loaded with a dynamic import within a commonjs context that will...
adds tests for `expectPromise` and `expectEqualPromisesOrValues` #3620 introduced `expectEqualPromisesOrValues` with a TODO of moving to testUtils and testing. This PR accomplishes that, and also moves the related `expectPromise` function, adding...
I investigated the performance drop between v15 and v16 and it was caused by switching transpilation target from es5 to es6. It's easy to reproduce with the following diff: ```diff...
Validation implementation for the [Client Controlled Nullability RFC](https://github.com/graphql/graphql-spec/pull/895) Follow up to https://github.com/graphql/graphql-js/pull/3418
Implements the suggestion by @benjie (https://github.com/graphql/graphql-js/issues/3356#issuecomment-958969934)
Continued from https://github.com/graphql/graphql-js/pull/2839 This is the reference impementation of the defer/stream spec proposal. The corresponding PR for spec changes are here: https://github.com/graphql/graphql-spec/pull/742 Please limit comments on this PR to code...
