-
Notifications
You must be signed in to change notification settings - Fork 810
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
Error: Cannot find module '@babel/compat-data/corejs3-shipped-proposals' #2383
Comments
👍 |
This will fix the `yarn test` problem in the deployment because it's a bug in the node >13.13: laravel-mix/laravel-mix#2383 https://phabricator.endlessm.com/T29832
i add "@babel/compat-data": "^7.9.0", to package.json, delete package-lock.json and node_module files |
I fixed this issue with: |
This will fix the `yarn test` problem in the deployment because it's a bug in the node >13.13: laravel-mix/laravel-mix#2383 https://phabricator.endlessm.com/T29832
This was fixed for me by running |
That bro, it solved my problems |
Seems it's fixed. |
我也遇到了这个问题 , 单单删除 node_modules 没有用, 还得删除 package-lock.json 文件才行 |
This one worked for me. Thanks bro |
❤️ |
Thank you so much... |
Error: Cannot find module '@babel/compat-data/corejs3-shipped-proposals' Update @babel/preset-env and @babel/compat-data More info: laravel-mix/laravel-mix#2383
|
thank you, it works for me. |
works for me |
Thanks this works for me |
'@babel/compat-data/corejs3-shipped-proposals' See: laravel-mix/laravel-mix#2383
this happen as I upgraded node from 12.4 to 12.9 |
In my case, I was using the wrong version of node for the project. Luckily we use NVM so I run |
Node:
|
Thank you bro, the day is saved! |
Ran into similar problem, this seemed to solve for me:
|
This worked for me: yarn upgrade --scope @babel |
solved my problem, Thanks |
I solved this issue by running a command "npm audit fix --force" |
Run this Command "npm audit fix --force" to solve this issue! |
Removing node_modules folder and clearing NPM cache worked for me: |
$> sudo npm update --depth 5 @babel/preset-env thx man... worked for me... |
This fixed my issue in 2022. Wow! kudos bro. |
I think this is related to a breaking change in node version 13.13 which conflicts with babel <= 7.9
The text was updated successfully, but these errors were encountered: