-
Notifications
You must be signed in to change notification settings - Fork 1
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
npm init riot failed spawn npm ENOENT error #15
Comments
node:internal/child_process:285 Error: spawn npm ENOENT Node.js v22.11.0 |
I have 2 pcs, both shows same message |
C:\Users\mikes>node -v C:\Users\mikes>npm -v |
in directory C:\Users\Masanobu Shimura\AppData\Local\npm-cache_npx\91a95858ebf364cb\node_modules.bin |
set PATH=%PATH%;C:\Users\Masanobu Shimura\AppData\Local\npm-cache_npx\91a95858ebf364cb\node_modules.bin |
Thank you for reporting this issue. I don't use windows and the error seems to come from node internals. Have you the same error using older node versions for example v20? |
I tried 20.18.0 but same status as below. Error: spawn npm ENOENT Node.js v20.18.0 |
I tried with windows linux wsl2 and it work normal. |
So it worked on windows via wsl2, the problem seems to exist only in windows cmd.exe. |
Help us to manage our issues by answering the following
Describe your issue: npm init riot commnd failed with following message.
Can you reproduce the issue?
Post the link using one of our bug report templates:
On which browser/OS does the issue appear?
Which version of Riot does it affect?
How would you tag this issue?
The text was updated successfully, but these errors were encountered: