search

unjs / nypm

🌈 Unified Package Manager for Node.js and Bun
MIT License
474 stars 17 forks source link

ENOENT on windows with nypm 0.1.x #59

Closed Celibioux closed 1 year ago

Celibioux commented 1 year ago

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

danielroe commented 1 year ago

Does it make a difference if you run corepack enable?

Celibioux commented 1 year ago

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

pi0 commented 1 year ago

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 commented 1 year ago

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

pi0 commented 1 year ago

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 commented 1 year ago

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