-
Notifications
You must be signed in to change notification settings - Fork 19
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
ENOENT on windows with nypm 0.1.x #59
Comments
Does it make a difference if you run |
I did try that but no difference and the corepack is enabled |
(@danielroe only FYI, nypm internally uses global |
Indeed. I thought it might be a helpful debugging step, however. |
The cross-platform issue with windows is fully fixed in nypm@0.2.x (checked on local windows). However, Nuxt is using 0.1.x. Trying to make a hot patch only on 1.x for windows support. |
Also fixed on nypm@0.1.1 new |
Environment
Windows : 11
Nuxt : 3.4.0
Nodejs : 18.15.0
Pnpm : 8.2.0
Reproduction
No reproduction for this i think
Describe the bug
After enabling the devtools in the nuxt.config.ts via ( devtools: true ) the nuxi upgrade --force detected it correctly and asked if i want to install the missing dep ( @nuxt/devtols ) but when i select yes i get the error showen in the screenshot
Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered: