-
Notifications
You must be signed in to change notification settings - Fork 29.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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Errors from conditional exports after upgraded to Node 13.13 #32852
Comments
/cc @guybedford |
@JLHwung I created babel/babel#11283 specifically to avoid Babel having this error. Was the above fix not patched and released already? |
@guybedford Ahh thanks. It was release in 7.9.0. For those babel users who are affected by this issue after upgrading to node.js 13.13/12.17, please upgrade |
Great, I'm glad the early fix here could help! |
After the update to `@babel/preset-env` `^7.8.6"` I faced the exception during the build on a plain machine: ``` ERROR in ./core/service-worker/index.js Module build failed (from ./node_modules/babel-loader/lib/index.js): Error: Cannot find module '@babel/compat-data/corejs3-shipped-proposals' ``` I've found this issue mentioned in the latest commits of the `babel` plugin and upgraded to `7.9.0` as recommended: babel/babel#11283 and nodejs/node#32852
Node v13.13.0 introduced a change that is incompatible with `@babel/preset-env` versions `< 7.9.0`. See: nodejs/node#32351 nodejs/node#32852 babel/babel#11283 Bump our direct dependencies to `7.9.5` and manually cause additional bumps in `yarn.lock` that result in all versions of `@babel/preset-env` installed in the monorepo's `node_modules` trees being `>= 7.9.0`.
Node v13.13.0 introduced a change that is incompatible with `@babel/preset-env` versions `< 7.9.0`. See: * nodejs/node#32351 * nodejs/node#32852 * babel/babel#11283 Bump our direct dependencies to `7.9.5` and manually cause additional bumps in `yarn.lock` that result in all versions of `@babel/preset-env` installed in the monorepo's `node_modules` trees being `>= 7.9.0`.
Node v13.13.0 introduced a change that is incompatible with `@babel/preset-env` versions `< 7.9.0`. See: * nodejs/node#32351 * nodejs/node#32852 * babel/babel#11283 Bump our direct dependencies to `7.9.5` and manually cause additional bumps in `yarn.lock` that result in all versions of `@babel/preset-env` installed in the monorepo's `node_modules` trees being `>= 7.9.0`.
This addresses this error travis-ci builds have been hitting: Error: Cannot find module '@babel/compat-data/corejs3-shipped-proposals' https://travis-ci.org/github/scottlamb/moonfire-nvr/jobs/684922930 nodejs/node#32852 (comment)
I had this problem in building a React Native Bob library. I solved it using This solution only applies if you use |
This should resolve an issue with Node v14 and `@babel/preset-env`. The pipeline was failing on an import. Here's an example: https://github.com/PsychoLlama/filament/runs/707159418?check_suite_focus=true#step:6:9 Babel published a fix. I just needed to upgrade. See: nodejs/node#32852
FYI, I noticed the same issue in |
not to be able to run nodejs/node#32852 This also updates Mirador to the latest RC
This upgrades @babel/preset-env to 7.9.0 from 7.8.7. See: nodejs/node#32852 (comment)
See nodejs/node#32852 (comment) Was getting error like: `Error: Cannot find module '@babel/compat-data/corejs3-shipped-proposals'`
Bump to current `ember-cli-babel`, which transitively requires a version of `@babel/preset-env` which [fixes the build issue][1]. Then use `yarn-deduplicate` to resolve all transitive dependencies to the minimum number of (maximum) versions of those shared dependencies, which results in *all* 7.x versions of `@babel/preset-env` resolving to a version with the fix. [1]: nodejs/node#32852
On new machine, we have a newer NodeJS, so we're running into this: Error: Cannot find module '$path_to/@babel/compat-data/data/corejs3-shipped-proposals' Which I think is the issue described here: nodejs/node#32852 and fixed here: babel/babel#11283 I just ran `yarn upgrade-interactive` and updated all the packages which looked safe-ish.
Ran into similar problem, though on a later Node version and using
|
This worked for me. Thanks!
|
What steps will reproduce the bug?
What is the expected behavior?
It should load the module as expected in Node.js 13.12
What do you see instead?
Additional information
Caught by the Babel CI: https://travis-ci.com/github/babel/babel/jobs/319348116#L360
The regression was likely introduced in #32351.
The file structure of
@babel/compat-data
can be simplified w.l.o.g asand the
package.json
:The
corejs3-shipped-proposals.js
is a proxy which delegates to "./data/corejs3-shipped-proposals.json" for Node.js < 13.3 support.The text was updated successfully, but these errors were encountered: