remove the enhanced error messages regarding using multiple versions of graphql-js. #4238
Closed
yaacovCR wants to merge 1 commit intographql:nextfrom
Closed
remove the enhanced error messages regarding using multiple versions of graphql-js. #4238yaacovCR wants to merge 1 commit intographql:nextfrom
yaacovCR wants to merge 1 commit intographql:nextfrom
Conversation
✅ Deploy Preview for compassionate-pike-271cb3 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
Hi @yaacovCR, I'm @github-actions bot happy to help you with this PR 👋 Supported commandsPlease post this commands in separate comments and only one per comment:
|
Contributor
Author
|
Closing in favor of: on background of: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR removes the enhanced error messages regarding using multiple versions of graphql-js.
Motivation:
globalThischeck and align with what bundlers can accept #4022)Downside:
This PR should be thought of a strawman PR for discussion.
If we do want to re-enter the package management business to some extent, we could combine this with #3915 => although that PR would only protect us going forward with versions that will support
Symbol.for().