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.

Concurrently started crashing with spawn cmd.exe ENOENT code -4058

See original GitHub issue

Recently concurrently (on multiple projects) stopped working. I’m not aware of any changes to my setup that causes this to occur, as far as I’m aware everything was working fine then one day suddenly broke.

I’m on windows 10, tested using CMD and PowerShell with the same results. Also tried updating node from 12.x.x to latest (14.4.0). Concurrently V5.2.0.

All scripts run individually, but when run using concurrently they crash.

Here’s one script that I’ve tested, taken from the three.js repo:

"dev": "concurrently --names \"ROLLUP,HTTP\" -c \"bgBlue.bold,bgGreen.bold\" \"rollup -c utils/build/rollup.config.js -w -m inline\" \"http-server -c-1 -p 8080\"",

Here’s the error message:

[ROLLUP] Error occurred when executing command: rollup -c utils/build/rollup.config.js -w -m inline
[ROLLUP] Error: spawn cmd.exe ENOENT
[ROLLUP]     at Process.ChildProcess._handle.onexit (internal/child_process.js:268:19)
[ROLLUP]     at onErrorNT (internal/child_process.js:468:16)
[ROLLUP]     at processTicksAndRejections (internal/process/task_queues.js:84:21)
[HTTP] Error occurred when executing command: http-server -c-1 -p 8080
[HTTP] Error: spawn cmd.exe ENOENT
[HTTP]     at Process.ChildProcess._handle.onexit (internal/child_process.js:268:19)
[HTTP]     at onErrorNT (internal/child_process.js:468:16)
[HTTP]     at processTicksAndRejections (internal/process/task_queues.js:84:21)
[HTTP] http-server -c-1 -p 8080 exited with code -4058
[ROLLUP] rollup -c utils/build/rollup.config.js -w -m inline exited with code -4058
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! three@0.116.1 dev: `concurrently --names "ROLLUP,HTTP" -c "bgBlue.bold,bgGreen.bold" "rollup -c utils/build/rollup.config.js -w -m inline" "http-server -c-1 -p 8080"`
npm ERR! Exit status 1

Even if I remove all everything except concurrently \"http-server -c-1 -p 8080\" I get the same error.

Issue Analytics

State:
Created 3 years ago
Comments:7 (3 by maintainers)

Top GitHub Comments

2reactions

looeeecommented, Jun 21, 2020

I was on Node 12 when this first occurred. Upgraded to Node 14, no change. Then uninstalled completely and reinstalled Node 14 and that seemed to fix it.

0reactions

gustavohenkecommented, Jun 20, 2020

No worries! Glad you fixed it. Are you still on Node 14? concurrently on CI is only testing Node 12, maybe there’s some breaking changes I’m not aware of.

Top Results From Across the Web

Problem with npm start (error : spawn cmd ENOENT)

Set your environment variable to C:\Windows\System32 . This works for me. Sets System variable. Solution 2. If the first one doesn't work follow ......

Error: spawn cmd.exe ENOENT using WSL since 9.0.0 #7251

One workaround is to set BROWSER to "none". This will prevent any browser from being launched. BROWSER=none yarn start # or BROWSER=none npm ......

React setup error can u guys help me to solve - Sololearn

Starting the development server... events.js:292 throw er; // Unhandled 'error' event ^ Error: spawn cmd ENOENT at Process.ChildProcess._handle.

ended with error spawn C:\WINDOWS\system32\cmd.exe ...

Hi guys, When i am starting to connect my org and visualforce, i am getting the below error. Starting SFDX: Authorize an Org...