graphql-js
graphql-js copied to clipboard
graphql
A reference implementation of GraphQL for JavaScript
:sparkles: _**This is an old work account. Please reference @brandonchinn178 for all future communication**_ :sparkles: --- It seems like `variableDefinitions` will always be a non-null array. https://github.com/graphql/graphql-js/blob/f07ec241d51d7c3fb0263bb3ade1975dc87babc3/src/language/parser.js#L258-L285 https://github.com/graphql/graphql-js/blob/f07ec241d51d7c3fb0263bb3ade1975dc87babc3/src/language/parser.js#L307
Running a project with Vue3 / Quasar2 / Vite in development mode fails after update. ``` // node_modules/graphql/jsutils/instanceOf.mjs globalThis.process && globalThis.process.env.NODE_ENV === 'production' ``` is compiled to ``` var instanceOf...
As surfaced in [Discord](https://discord.com/channels/625400653321076807/862957336082645006/1206980831915282532) this currently is a breaking change in the 16.x.x release line which is preventing folks from upgrading towards a security fix. This PR should result in...
This PR introduces optional chaining when accessing `globalThis.process.env.NODE_ENV` in the graphql-js codebase. The current implementation assumes that `globalThis.process.env` is always defined, which may not be the case in all environments....
This is a rebase of https://github.com/graphql/graphql-js/pull/3847 This implements execution of Fragment Arguments, and more specifically visiting, parsing and printing of fragment-spreads with arguments and fragment definitions with variables, as described...
I am reviving #1262 as I have an use case that is related to that discussion: > Right now directives are purely a feature of the GraphQL language and IDL,...
## Context We use [contentful/live-preview](https://github.com/contentful/live-preview). The library has `graphql-js` as a dependency. ## Problem If the DOM has an element with `id="process"` eg. `` than the current implementation of `utils/instanceOf`...
Many of the type configuration objects in GraphQL-js have properties that accept thunks: - GraphQLObjectTypeConfig.fields - GraphQLObjectTypeConfig.interfaces - GraphQLInterfaceTypeConfig.fields - GraphQLInterfaceTypeConfig.interfaces - GraphQLInputObjectTypeConfig.fields - GraphQLUnionTypeConfig.types These are because their definitions...
I noticed an issue where creating a `GraphQLSchema` from an SDL and then printing it again results in dropping a `@deprecated` directive if the reason is explicitly set to `null`....
