question-mark

Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error: spawn ENOENT

See original GitHub issue

Issue Description

I’m not sure when this started, but after recently updating webpack-shell-plugin to 0.4.6, my config seems to have stopped working. I have the following in my Webpack 2.1.0-beta.27 config:

    plugins: [
        new WebpackShellPlugin({
            onBuildEnd: ['tsc --d --declarationDir dist/typings'],
            dev: false
        })
    ]

Which, when I try to run Webpack gives me:

Executing post-build scripts
events.js:160
      throw er; // Unhandled 'error' event
      ^

Error: spawn tsc ENOENT
    at exports._errnoException (util.js:1007:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:182:32)
    at onErrorNT (internal/child_process.js:348:16)
    at _combinedTickCallback (internal/process/next_tick.js:74:11)
    at process._tickCallback (internal/process/next_tick.js:98:9)

I’m not 100% sure what versions are affected, but I rolled back to version 0.4.3 of this plugin, and that seemed to do the trick.

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:8 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
gvandegriftcommented, Dec 7, 2016

0.4.8 works for me (and throws on failure 😄 ). Thanks!

0reactions
opiepjcommented, Dec 9, 2016

Thanks everyone

Read more comments on GitHub >

github_iconTop Results From Across the Web

How do I debug "Error: spawn ENOENT" on node.js?
Spawn may emit the ENOENT error if the filename command (i.e, 'some-command') does not exist in at least one of the directories defined...
Read more >
spawn node ENOENT" when using child_process in Node.js
Have you ever stumbled upon this error when using spawn from Node.js' child_process module? ~/demo $ node main.js. ~/demo/main.js: ...
Read more >
[Solved-5 Solutions] Error spawn enoent on node.js - Wikitechy
Spawn may emit the ENOENT error if the filename command (i.e, 'some-command') does not exist in at least one of the directories defined...
Read more >
Error spawn ENOENT on node js | Edureka Community
Hii team, When I get the following error: events.js:72 throw er; // Unhandled ' ... at Process.ChildProcess.
Read more >
PM2 error: Error: spawn node ENOENT · Issue #3648 - GitHub
Solved after I changed the path in the process.json from "cwd": "/root/dev/zhaogong-be" to "cwd": "d:/zhaogong-be".
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found