-
Notifications
You must be signed in to change notification settings - Fork 12.1k
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
Add babel plugin to workaround bug in @babel/preset-env #45664
Conversation
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.
Great work! 🎉 babel.config.json is a normal json file and comments shouldn't be used there. I guess this is not actually enforced when reading this file but wonder if we might get errors later at some point.
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new branch
git switch --create backport-45664-to-v8.4.x origin/v8.4.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x 05f68c391c67790cbf8c81c4ac295b12c808d310
# Push it to GitHub
git push --set-upstream origin backport-45664-to-v8.4.x
git switch main
# Remove the local backport branch
git branch -D backport-45664-to-v8.4.x Then, create a pull request where the |
(cherry picked from commit 05f68c3)
It's a JSON5 file (as documented at https://babeljs.io/docs/en/config-files#supported-file-extensions), so it's safe to use comments there. |
What this PR does / why we need it:
@babel/preset-env
to a newer patch version@babel/plugin-proposal-class-properties
to work around the problem until a fix is released in@babel/preset-env
Which issue(s) this PR fixes:
Fixes #45624
Special notes for your reviewer:
one thing that confuses me a little is that you can apparently add comments to the
babel.config.json
? i guess it's not real json then, or it gets stripped out later 😕