-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
[babel 8] Update default @babel/runtime version
#17512
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
nicolo-ribaudo
commented
Sep 12, 2025
| Q | A |
|---|---|
| Fixed Issues? | Fixes #17510 |
| Patch: Bug Fix? | |
| Major: Breaking Change? | |
| Minor: New Feature? | |
| Tests Added + Pass? | Yes |
| Documentation PR Link | |
| Any Dependency Changes? | |
| License | MIT |
@babel/runtime version
|
Build successful! You can test your changes in the REPL here: https://babeljs.io/repl/build/59947 |
|
commit: |
| const { | ||
| version: runtimeVersion = "7.0.0-beta.0", | ||
| version: runtimeVersion = process.env.BABEL_8_BREAKING | ||
| ? "8.0.0-beta.0" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we bump the default in every beta version and stable it to 8.0.0 in the official release? So we can still add new runtime in the beta stage.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The problem is that for local development api.version is 7.28.4 even with BABEL_8_BREAKING=true, which makes it a bit complex.
I'm thinking of keeping it like this and bump it to 8.0.0 for the Babel 8.0.0 release?