update to GraphQL 17 #2439
Draft
update to GraphQL 17 #2439
Conversation
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
|
|
@n1ru4l can you update the regression matrix in github actions? |
acao
force-pushed
the
feat-consistent-typescript-version
branch
from
f45dcfa to
fdb74f9
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Currently, the GraphQL.js 17 alpha only ships ESM and no CommonJS.
At my current understanding, this implies that all packages within the mono-repository must be completely converted to ESM-only as you cannot sync-require a ESM module from within a CommonJS context.
Related: graphql/graphql-js#3603