fix: move @codemirror packages to peer deps, upgrade to 0.20.0 #2369
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.
It looks like when CodeMirror 6 support was first added to the
codemirror-graphql
package,@codemirror/stream-parser
was mistakenly added as a regular dependency rather than a peer dependency (unlike the CM5codemirror
package).This may lead to conflicts when upgrading upstream CM6 packages in a project that depends on this package (especially when upgrading major/minor versions) since you end up with multiple versions of core packages like
@codemirror/view
which leads to bugs. This is especially relevant as there is now a new release for each of the core CodeMirror packages (0.20.0
).This PR moves
@codemirror/
packages topeerDependencies
and upgrades the CM6 packages to the latest version in the new release. Note that I remove@codemirror/stream-parser
in favor of@codemirror/language
as per the release notes linked above.