Actually remove preset-env's useBuiltIns#18079
Merged
Merged
Conversation
preset-env's useBuiltIns
Collaborator
|
Build successful! You can test your changes in the REPL here: https://babeljs.io/repl/build/61790 |
|
commit: |
This was referenced Jul 1, 2026
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
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.
Fixes #1, Fixes #2We marked this as removed both in the migration guide's Getting ready section and in the release post, but... did not actually remove it from the code 😓
Given that it's less than 24 hours since Babel 8, I'm quickly adding an error when using the option and releasing it. It's technically a breaking change in a patch release, but the timing should make it still possible.
This patch doesn't actually remove the code yet, so that we can easily add it back if needed.
Note that even if we keep this option we would only support core-js3, even after that core-js 4 is released, as people really should use the separate packages rather than putting all of the versions under preset-env again, with the option defaulting to what the old version would be.