Skip to content
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

Error: spawn npm run help ENOENT #85

Closed
vaiulian opened this issue Feb 28, 2017 · 5 comments
Closed

Error: spawn npm run help ENOENT #85

vaiulian opened this issue Feb 28, 2017 · 5 comments

Comments

@vaiulian
Copy link

Hei,

I've been having an issue with the new 0.6.x version.

this gshell.task([ "npm run help"]) won't work anymore.

it crashes with

events.js:141
      throw er; // Unhandled 'error' event
      ^

Error: spawn npm run help ENOENT
    at exports._errnoException (util.js:907:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:178:32)
    at onErrorNT (internal/child_process.js:344:16)
    at nextTickCallbackWith2Args (node.js:442:9)
    at process._tickCallback (node.js:356:17)
    at Function.Module.runMain (module.js:443:11)
    at startup (node.js:139:18)
    at node.js:974:3

although some simple shell commands like pwd or whoami, works fine. And in 0.5.2 this one used to work.

i'm using node v4.5.0, npm 2.15.9 on a Windows10 Enterprise Machine

@sun-zheng-an
Copy link
Owner

sun-zheng-an commented Feb 28, 2017

What about npm.cmd run help on Windows?

I found a similar issue in nodejs/node#3675.

@vaiulian
Copy link
Author

Yes, you are right

npm.cmd run help works. Strange. Will have to look into it.

Thanks.

@stevepiron
Copy link

I'm getting pretty much the same problem. This is my task:

plugins.shell.task([
    "ssh -L 3333:localhost:3306 " + options.config.ssh.user + "@xx.xxx.xxx.xxx"
], {
    quiet: true,
});

and the error message:

events.js:141
      throw er; // Unhandled 'error' event
      ^

Error: spawn ssh -L 3333:localhost:3306 steve@xx.xxx.xxx.xxx ENOENT
    at exports._errnoException (util.js:870:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:178:32)
    at onErrorNT (internal/child_process.js:344:16)
    at nextTickCallbackWith2Args (node.js:442:9)
    at process._tickCallback (node.js:356:17)
    at Function.Module.runMain (module.js:443:11)
    at startup (node.js:139:18)
    at node.js:968:3

I'm on Mac OS X, node 4.4.5, npm 3.10.2

@stevepiron
Copy link

^ Had a look at the releases page of gulp-shell and noticed it required a certain version of node to be installed. I followed this guide and it now works: https://davidwalsh.name/upgrade-nodejs

@WebDeveloperMobin
Copy link

Starting project at F:\React Native\amazingOne
Expo DevTools is running at http://localhost:19002
Opening DevTools in the browser... (press shift-d to disable)
Error: spawn powershell ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:267:19)
at onErrorNT (internal/child_process.js:469:16)
at processTicksAndRejections (internal/process/task_queues.js:84:21)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @ start: expo start
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @ start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Dell\AppData\Roaming\npm-cache_logs\2020-09-04T10_37_25_963Z-debug.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants