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

ENOENT on windows with nypm 0.1.x #59

Closed
Celibioux opened this issue Apr 12, 2023 · 6 comments
Closed

ENOENT on windows with nypm 0.1.x #59

Celibioux opened this issue Apr 12, 2023 · 6 comments

Comments

@Celibioux
Copy link

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
Sans titre

Additional context

No response

Logs

No response

Copy link
Member

Does it make a difference if you run corepack enable?

@Celibioux
Copy link
Author

I did try that but no difference and the corepack is enabled

@pi0
Copy link
Member

pi0 commented Apr 12, 2023

Does it make a difference if you run corepack enable?

(@danielroe only FYI, nypm internally uses global corepack <pm> command. it works as long as using recent node version shipping global binary. enabling is not required)

@danielroe
Copy link
Member

Indeed. I thought it might be a helpful debugging step, however.

@pi0 pi0 changed the title Error while Installing the Devtools ENOENT on windows with nypm 0.1.x Apr 12, 2023
@pi0
Copy link
Member

pi0 commented Apr 12, 2023

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.

@pi0
Copy link
Member

pi0 commented Apr 12, 2023

Also fixed on nypm@0.1.1 new pnpm nuxi@latest upgrade --force should be working on windows machines.

@pi0 pi0 closed this as completed Apr 12, 2023
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

3 participants