-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Babel preset warnings in v12.6.6 #6683
Comments
Actual IssueAs the error suggests, whenever
Since depending on the config that line is added to the preset here: https://github.com/nrwl/nx/blob/master/packages/web/babel.ts#L81, we run into this issue. How to solve itIn @nrwl/web/babelIf you are using the web preset you cann add the
In @nrwl/react/babelUnfortunately the react babel preset, does not have an option to configure it, but it can be overwritten with this:
Testing the issue is hard due to cachingWhen running builds or something, the babel-loader caches the configuration of .babelrc which makes testing different configurations hard. The warnings are only logged when the babel config file is evaluated, which does not happen in the case it was cached. Disable Caching for .babelrc to test different babel configurationsIn order to disable the caching I had to overwrite the webpack config, so at least it is easy to test different babel configurations.
|
…lugin-proposal-class-properties If `loose` is set to `true` for `@babel/plugin-proposal-class-properties`, the same must be true for `@babel/preset-env`. ISSUES CLOSED: nrwl#6683
Unfortunately that didn't do the job for me. I did override all of the .babel config files of my project to set loose: false for plugin-proposal-class-properties, but I was still seeing all of those warnings. What seems to have done the job was the following instead:
on every single .babel file that I have. |
Hi, since updating to NX@12.9, we are seeing lots of babel warnings in our app. The main reason is because we are using Looks like the default for loose is false. Is there a reason for it to be Ideally, we don't want to add overrides in all of our |
This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context. |
Current Behavior
Babel warns for:
Expected Behavior
No warnings should be shown
Steps to Reproduce
The text was updated successfully, but these errors were encountered: