nuxi upgrade 3.7.0 throws ERROR spawnSync /bin/sh ENOENT
Closed this issue · 2 comments
mklueh commented
Environment
- Operating System: Linux //WSL 2
- Node Version: v20.6.0
- Nuxt Version: 3.7.1
- CLI Version: 3.7.3
- Nitro Version: 2.5.2
- Package Manager: yarn@3.6.3
- Builder: -
- User Config: -
- Runtime Modules: -
- Build Modules: -
Reproduction
Downgrade from nuxt 3.7.1 to 3.7.0
Describe the bug
I'm trying to downgrade nuxt, but it is throwing an error
Additional context
No response
Logs
nuxi upgrade 3.7.0
ℹ Package Manager: yarn 3.6.3 8:10:57 AM
ℹ Current nuxt version: 3.7.1 8:10:57 AM
✔ Would you like to recreate node_modules and 3.7.0/yarn.lock to fix problems with hoisted dependency versions and ensure you have the most up-to-date dependencies?
Yes
ℹ Recreating node_modules and 3.7.0/yarn.lock. If you encounter any issues, revert the changes and try with --no-force 8:11:06 AM
ℹ Installing latest Nuxt 3 release... 8:11:06 AM
ERROR spawnSync /bin/sh ENOENT 8:11:06 AM
at Object.spawnSync (node:internal/child_process:1124:20)
at spawnSync (node:child_process:876:24)
at execSync (node:child_process:957:15)
at Object.run (node_modules/nuxi/dist/chunks/upgrade.mjs:76:5)
at async runCommand$1 (node_modules/nuxi/dist/shared/nuxi.57fa43de.mjs:1644:5)
at async runCommand$1 (node_modules/nuxi/dist/shared/nuxi.57fa43de.mjs:1638:7)
at async runMain$1 (node_modules/nuxi/dist/shared/nuxi.57fa43de.mjs:1756:7)
ERROR spawnSync /bin/sh ENOENT
mklueh commented
I've tried to manually delete yarn.lock. Now I'm getting
ERROR Cannot detect Package Manager in /home/user/workspace/myproject/3.7.0 8:15:16 AM
pi0 commented
Hi. The issue with /bin/sh ENOENT
should be resolved in latest nuxi version (you might need a manual upgrade). With latest version of nypm, we automatically fallback from corepack when is not found in env.
@mklueh Feel free to open a new issue. But it is on track to support a fallback when no package manager is not detected (which itself seems a bug but need reproduction)