-
-
Notifications
You must be signed in to change notification settings - Fork 105
error message "command not found: cowsay" (Win 10) #60
Comments
I think this is likely to be the same issue, yeah. Is this also on Powershell? I'll take a look on Windows tomorrow and see what's up. I know I've had some Windows users for a while, now. |
this is cmd.exe how do you approach developing npx? |
I wasn't using npx in last few days so I didn't notice it's not working for several major versions for me :) Tried running different versions today: running not installed packages stopped working since v6.0.0 and running both locally and globally installed packages stopped working since v6.2.0 on my box. Error message is I'm not experienced in processes and spawning etc. so it's probably a naive approach but when I set There is a related note in node docs:
I have Windows 10 and I've tried all of that in cmd.exe, but the results are the same for bash.exe (aka Git Bash) too. I have node 6.9.4 and tried npx 5.4.0 (works fine), 6.0.0 (not installed packages stopped working), 6.1.0, 6.2.0 (globally and locally installed packages stopped working), 7.0.0, 8.1.1, 9.0.3 (bundled), and 9.0.7 (standalone) (still not working). I tried the fix above with 8.1.1 and 9.0.7 (both bundled and standalone). |
works like a charm, thanks everybody! :) |
this may or may be not related to #58 (i encountered the same issue, but only when running a module that has not been installed already).
when i try to reproduce the example from your blog post I get the error message from the title.
in more detail:
Update:
I updated to 9.0.5, the issue is still the same.
The text was updated successfully, but these errors were encountered: