-
Notifications
You must be signed in to change notification settings - Fork 161
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
fix: Disabling dev tool make the project crash #667
Comments
nuxt.config.ts
|
@Arcelone I just did your reproduction steps and I got no error, worked as expected |
This behavior is fix withe 3.12 version release. 👍🏻 EDIT : obviously present again in subsequent versions. |
I'm getting this as well, 3.12.4 |
Can confirm, I'm getting the same error in 3.12.4. |
Can confirm, I'm getting the same error in 3.13.0 also.
|
Get this in latest Chrome but not when using inkognito or in Firefox on a mac. |
Still getting this issue with |
Same. 3.13.2 |
Fix with this version :
If any one can confirme ? That I can close the issue. |
same! 3.13.2 |
Same problem |
So, on 3.13.2, i managed to get it going again by adding this explicitly on nuxt.config.ts:
also, i read somewhere that nuxt-security might be causing the issue, but I can't confirm. I've got nuxt-security set up, with the headers settings to make devtools work, but if i explicitly disable them with the code above, it doesn't crash. |
Problem went away on its own.. not really sure what happened. |
🐛 The bug
When you create a new project with :
then run :
the run the project with :
npm run dev
you get this error :
🛠️ To reproduce
https://github.com/Arcelone/devtoolsbug
🌈 Expected behavior
That the project works properly without the devtools.
ℹ️ Additional context
.nuxtrc
contain just thistelemetry.enabled=false
version :
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.7/install.sh | bash
)No "system" version of node installed. I have tried with but doesn't solve anything.
If you create the project with :
and the disable with :
everything is working well.
The text was updated successfully, but these errors were encountered: