[core] Drop support for node 10 #25306
Merged
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
eps1lon
added
the
breaking change
oliviertassinari
approved these changes
Mar 11, 2021
1 task
1 task
42 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
BREAKING CHANGE
Upgrade your node version to 12.x. Installing with node 10 will not yet error. Though installing with node 10 happens at your own risk. Once v5 is released as stable it will error during install.
Node 10 will reach end-of-life end of this month. We might as well use this opportunity to drop support for it to be able to use native modules (and the
exportsfield)Update to the
enginesfield is blocked by codesandbox/codesandbox-ci-ui#22