-
Notifications
You must be signed in to change notification settings - Fork 2
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
Windows and Linux(Debian) Support - Error trying to run npm init ic #11
Comments
Are you on Windows? If yes, this CLI does not support this OS (yes, PR welcome). If Mac or Linux, what version of NodeJS are you using? |
i also got same error , i am using WSL2 and my node version is v18.16.0 |
Thanks for the addition feedback. That's the issue then. This CLI does not support Windows (yet) so I guess it does not work with WSL2 as well. PR welcome! |
I am also facing the same issue on Linux(Debian). I am running node v18.15.0 and npm v9.6.7 |
@sam-the-tutor thanks for the ping. Did you use the last version of the CLI?
And what version of NodeJS are you using? |
I used that command but it failed. I am running node v18.15.0 |
@sam-the-tutor well then, it look like it does not work on Linux (Debian) as well 😢. I don't plan to solve this my self but, if you or anyone is keen to provide a PR, for sure happy to review and merge it! |
when I try to run the " npm init ic@latest " command I get this error:
create-ic version 0.5.0
Unexpected error Error: spawn command ENOENT
at ChildProcess._handle.onexit (node:internal/child_process:285:19)
at onErrorNT (node:internal/child_process:483:16)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
errno: -2,
code: 'ENOENT',
syscall: 'spawn command',
path: 'command',
spawnargs: [ '-v', 'dfx' ]
The text was updated successfully, but these errors were encountered: