How do I debug “Error: spawn ENOENT” on node.js?

by

When I get the following error:

events.js:72
        throw er; // Unhandled 'error' event
              ^
Error: spawn ENOENT
    at errnoException (child_process.js:1000:11)
    at Process.ChildProcess._handle.onexit (child_process.js:791:34)

What procedure can I follow to fix it?

Author note: Lots of issues with this error encouraged me to post this question for future references.

Related questions:

  • using spawn function with NODE_ENV=production
  • node.js child_process.spawn ENOENT error – only under supervisord
  • spawn ENOENT node.js error
  • https://stackoverflow.com/questions/27603713/nodejs-spawn-enoent-error-on-travis-calling-global-npm-package
  • Node JS – child_process spawn(‘npm install’) in Grunt task results in ENOENT error
  • Running “foreman” task Fatal error: spawn ENOENT
  • unhandled error event in node js Error: spawn ENOENT at errnoException (child_process.js:975:11)
  • Node.js SpookyJS: error executing hello.js
  • https://stackoverflow.com/questions/26572214/run-grunt-on-a-directory-nodewebkit
  • Run exe file with Child Process NodeJS
  • Node: child_process.spawn not working on Java even though it’s in the path (ENOENT)
  • spawn ENOENT error with NodeJS (PYTHON related)
  • image resizing is not working in node.js (partial.js) (non-installed dependency)
  • npm install error ENOENT (build dependency problem)
  • Cannot install node.js – oracle module on Windows 7 (build dependency problem)
  • Error installing gulp using nodejs on windows (strange case)

29 Answers
29

Leave a Comment