-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: class-static-block
works different on node 12 and 14+ after 7.14.0
#13293
Comments
Hey @JounQin! We really appreciate you taking the time to report an issue. The collaborators on this project attempt to help as many people as possible, but we're a limited number of volunteers, so it's possible this won't be addressed swiftly. If you need any help, or just have general Babel or JavaScript questions, we have a vibrant Slack community that typically always has someone willing to help. You can sign-up here for an invite." |
Besides, the Maybe it is related. |
The error is expected. Note that unlike plugins, the presets are applied in an order of last to first (https://babeljs.io/docs/en/presets/#preset-ordering), in your cases, In Babel 7.14,
So error is thrown because Since TypeScript already supported private methods and properties, I would suggest do a major release for |
@JLHwung #12691 blocks me removing some related plugins. And
They are already removed, but I forgot to remove them in package.json, thanks for point out. |
@JounQin Until that other issue is fixed, could you try checking if moving |
@nicolo-ribaudo Thanks for your advice, but it seems not working.
Not end. |
馃捇
How are you using Babel?
Other (Next.js, Gatsby, vue-cli, ...)
Input code
Configuration file name
babel.config.js
Configuration
Current and expected behavior
Works on Node 14+, build failed on Node 12
un-ts/babel-preset-proposal-typescript#115
Environment
Possible solution
No idea for now.
Additional context
It was just working previously for
babel@7.12.0
.https://github.com/rx-ts/babel-preset-proposal-typescript/runs/2472758787#step:8:38
The text was updated successfully, but these errors were encountered: