-
-
Notifications
You must be signed in to change notification settings - Fork 32
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
Implicitly added babel plugins #189
Comments
11 tasks
Hey @wessberg, any chance you could have a look at this? |
2 tasks
This was referenced Feb 28, 2023
Hi all 👋 PR #205 has been created 3 month ago to fix this, but no activity on this ticket or the PR since… Is there a chance this could get a review? |
This was referenced Jun 29, 2023
Hi there, As |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
tsc
(if applicable): n/aReproduction
Expected Behavior
I am trying to apply only the explicitly configured babel plugins, and otherwise let the code be "ESLatest".
The docs say:
According to this, I am expecting only the explicitly configured babel plugins to be used. Which means the object spread is not transpiled away.
Actual Behavior
My use of object spread syntax is unnecessarily transpiled away, and this babel helper function is included as a polyfill into the bundle.
Comment
Amongst others,
@babel/plugin-proposal-object-rest-spread
is added implicitly here. I do not understand the rationale behind this logic. Why are these plugins implicitly added? And why specifically these five? Object spread is AFAIK an approved ES2018 feature, supported in all modern browsers and node. So no need for transpilation by default, and without a way to disable this behavior.The text was updated successfully, but these errors were encountered: