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

"Though the loose option was set to false" error on fresh nuxt install. Reopen! #9653

Closed
Intevel opened this issue Aug 10, 2021 · 1 comment

Comments

@Intevel
Copy link
Contributor

Intevel commented Aug 10, 2021

I just set up a new NuxtJS project and a problem what came in another version again. Issue#9651.

I copied the text from the old issue. The Merge/Fix was deleted!

Reproduction
Create a new nuxt app.

Steps to reproduce
Project name: my-brand-new-project
? Programming language: JavaScript
? Package manager: Npm
? UI framework: None
? Nuxt.js modules: (Press to select, to toggle all, to invert selection) (Axios)
? Linting tools: (Press to select, to toggle all, to invert selection) (Prettier)
? Testing framework: None
? Rendering mode: Universal (SSR / SSG)
? Deployment target: Server (Node.js hosting)

What is Expected?
Start normally after npm run dev

What is actually happening?
Having this error.

Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-property-in-object since the "loose" mode option was set to "true" for @babel/plugin-proposal-private-methods. The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding ["@babel/plugin-proposal-private-property-in-object", { "loose": true }] to the "plugins" section of your Babel config.

@danielroe
Copy link
Member

@Intevel The fix you linked has been merged but not yet released.

You can substitute nuxt-edge for nuxt in your package.json to confirm that the fix works.

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

No branches or pull requests

2 participants