Extension of the API #1012
Merged
Extension of the API #1012
+2,804
−1,288
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
zloirock
force-pushed
the
api
branch
3 times, most recently
from
e2737af to
6010565
Compare
zloirock
force-pushed
the
api
branch
4 times, most recently
from
356536e to
05ebe3f
Compare
|
Published. |
This was referenced Jan 16, 2022
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.
(sure, without breaking changes)
core-js/actual/**namespace.We will have 4 main namespaces:
/es/that contains only stable ECMAScript features/stable/that contains stable ECMAScript features and features from web standards/actual/that contains stable ECMAScript features, stage-3 ECMAScript proposals and features from web standards that will be the recommended way ofcore-jsusage/features/that contains only stable ECMAScript featuresIn
core-js@4:import 'core-js'will not contain early stage proposals and will be an equal ofimport 'core-js/actual'/features/will be renamed to something more descriptiveimport 'core-js/proposals/string-padding'for import old string padding proposal.In
core-js@4:core-js/stage/4entry point will be removed since it contains proposals finished only after the latestcore-jsmajor release. For usage of them will be required to import it from/es|stable|actual|features/namespaces or by a proposal name, like in the example above./web/namespace and/virtual/indexentries removed from theREADME.mdsince they will be removed fromcore-js@4(the first is almost useless and confuses users, the second is harmful since they load many unused features and cause problems with theexportspackage.jsonfield).I'm not completely sure in the
/actual/name, does anyone have better ideas?