feat: use core-js@3 by default
#594
Merged
Conversation
This file contains 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
clarkdo
reviewed
Aug 27, 2020
clarkdo
approved these changes
Aug 27, 2020
Atinux
approved these changes
Aug 28, 2020
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.
It is a long time since
core-js@3released but we are still usingcore-js@2by default to avoid breaking changes. This is going to make more problems for nuxt@2 users as more packages updated.Since 2.14.0 we auto detect core-js version by resolving installed version from root dir (src) so this is a non-breaking change encouraging users to use 3.x for newly created projects.
PS: PR also contains sorting of dependencies by yarn