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-env/lib/utils has been removed #12856
Comments
Hey @markhoney! 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." |
We can check if we can add a stub back to restore the original functionality, but that file has never been part of the public API. |
Adding it back in, for now, would be great, as I'm sure there will be a few Nuxt users who are going to have issues with this. In the long term, hopefully Nuxt will work around this. |
Ok it looks like it's easier to make a PR to remove that usage in Nuxt.js, I think I'll do that instead. |
Closing this issue as nuxt/nuxt#8883 is merged. Importing internal Babel files will throw on Babel 8, as we mentioned in Babel 8 release plan
|
Bug Report
Current behavior
Nuxt JS relies on @babel/preset-env/lib/utils, which appears to have been removed in version 7.13
Input Code
Expected behavior
Babel Configuration (babel.config.js, .babelrc, package.json#babel, cli command, .eslintrc)
babel.config.js
Environment
Possible Solution
Re-add the file utils.js to @babel/preset-env
Additional context
The text was updated successfully, but these errors were encountered: