Avoid unnecessarily importing isType
from graphql
package
#8891
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To import
graphql
(and its internalinstanceOf
function) for the first time withprocess.env.NODE_ENV
safely polyfilled, PR #8347 selected a somewhat arbitrary export of thegraphql
package that usesinstanceOf
, specifically theisType
function exported bygraphql/type/definition
.As revealed by issue #8705, importing
isType
was a bad choice, since it depends on a bunch of other code within thegraphql
package, unnecessarily increasing minified+gzip bundle size by approximately 3.4kB.A better choice is the
Source
constructor, which is already imported thanks to other necessary imports, and also imports/usesinstanceOf
.