Closed martinszeltins closed 4 months ago
@martinszeltins as you can see in the console log you are using a very old version of Nuxt DevTools: 0.3.1
(probably cached). check this comment
@martinszeltins as you can see in the console log you are using a very old version of Nuxt DevTools:
0.3.1
(probably cached). check this comment
@arashsheyda Thank you! There was indeed a ~/.nuxtrc
file in my home directory and it included something about @nuxt/devtools
I have no clue how it got there or why it locked the devtools version causing it to install an old version. This is very strange and totally unexpected. This feels like a bug in pnpm or Nuxt. When I ran nuxi@latest init
I wanted it to install the latest version of everything not a very old cached version of Devtools. And I didn't even ask it to cache it.
I think the DX could be much improved if the developer was given a choice about this. Because right now I was pulling out my hair trying to figure out why Devtools was not working or why it installed a very old version when I specifically said I wanted to install the latest version of Nuxt. What do you think?
This was my ~/.nuxtrc file (I did not know it even existed) Very frustrating... đŖ
telemetry.consent=1
telemetry.enabled=true
telemetry.seed=75ccc17ff3c6d221
modules.0=/home/martins/.nvm/versions/node/v18.12.1/lib/node_modules/@nuxt/devtools/module.cjs
devtoolsGlobal.projects.0=/home/martins/Programming/test/nuxt/my-nuxt-1
After deleting the ~/.nuxtrc file, everything worked again!
@martinszeltins as you can see in the console log you are using a very old version of Nuxt DevTools:
0.3.1
(probably cached). check this comment@arashsheyda Thank you! There was indeed a
~/.nuxtrc
file in my home directory and it included something about@nuxt/devtools
I have no clue how it got there or why it locked the devtools version causing it to install an old version. This is very strange and totally unexpected. This feels like a bug in pnpm or Nuxt. When I ran
nuxi@latest init
I wanted it to install the latest version of everything not a very old cached version of Devtools. And I didn't even ask it to cache it.I think the DX could be much improved if the developer was given a choice about this. Because right now I was pulling out my hair trying to figure out why Devtools was not working or why it installed a very old version when I specifically said I wanted to install the latest version of Nuxt. What do you think?
This was my ~/.nuxtrc file (I did not know it even existed) Very frustrating... đŖ
telemetry.consent=1 telemetry.enabled=true telemetry.seed=75ccc17ff3c6d221 modules.0=/home/martins/.nvm/versions/node/v18.12.1/lib/node_modules/@nuxt/devtools/module.cjs devtoolsGlobal.projects.0=/home/martins/Programming/test/nuxt/my-nuxt-1
After deleting the ~/.nuxtrc file, everything worked again!
This solved it for me as well, thank you!
đ The bug
I just installed the latest version of Nuxt
3.11.1
and also latest version of Nuxt Devtools1.1.3
. When I start the dev server and try to open the DevTools it shows an error in the console. I thought this might be fixed with #630 but it still shows me this error. I would be happy to provide any extra info to help debug this issue. This seems to be happening only on my computer as others have said that it works fine on their computers. I tried restarting my computer, tried running dev server on a different port and still does not work.This is a completely fresh Nuxt 3.11.1 installation with
npx nuxi@latest init nuxt-app
My environment:
DevTools screenshot: https://i.imgur.com/tZcjZSK.png Console output screenshot: https://i.imgur.com/BRA3daV.png
Error:
Here are my ENV variables if perhaps it has anything to do with this (Ubuntu 20.04 LTS, GNOME):
đ ī¸ To reproduce
npx nuxi@latest init nuxt-app
đ Expected behavior
Expecting DevTools to work.
âšī¸ Additional context
No response