Skip to content
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 "loose" option error spamming in console on fresh project #782

Closed
utshomax-zz opened this issue Apr 30, 2021 · 2 comments
Closed

Babel "loose" option error spamming in console on fresh project #782

utshomax-zz opened this issue Apr 30, 2021 · 2 comments

Comments

@utshomax-zz
Copy link

utshomax-zz commented Apr 30, 2021

The Issue:
nuxt/nuxt#9224 (comment)

Solution (Temp):

With yarn, please pin your babel deps manually in your package.json, then use yarn install again:

"resolutions": {
  "@babel/core": "7.13.15",
  "@babel/preset-env": "7.13.15"
}

With npm, add these as dev deps (with the same versions).

Originally posted by @manniL in nuxt/nuxt#9224 (comment)

The Question:

Shouldn't the create-nuxt-app add those devDependencies by default while creating the project?

@aldy505
Copy link

aldy505 commented May 1, 2021

Shouldn't the create-nuxt-app add those devDependencies by default while creating the project?

Yes, it is. But nuxt is using ^ (caret) on their @babel/core and @babel/preset-env version. See here for more info about that. Then, two days ago a minor version was released on @babel/core and @babel/preset-env which causes the bug.

@utshomax-zz
Copy link
Author

Closing this issue since this PR of nuxt seems solves the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants