Problem with npm start (error : spawn cmd ENOENT)

Question

I have a problem with my application. Because before when I created an application it worked, but now, it shows me this error and I do not know why and the things I have to do to fix it.

Do you have any idea to help me ? (This is a reactJS app).

I checked some stackoverflow topics but everywhere I checked, it was not really an answer that worked.

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

Error: spawn cmd ENOENT
    at Process.ChildProcess._handle.onexit (internal/child_process.js:264:19)
    at onErrorNT (internal/child_process.js:456:16)
    at processTicksAndRejections (internal/process/task_queues.js:77:11)
Emitted 'error' event at:
    at Process.ChildProcess._handle.onexit (internal/child_process.js:270:12)
    at onErrorNT (internal/child_process.js:456:16)
    at processTicksAndRejections (internal/process/task_queues.js:77:11) {
  errno: 'ENOENT',
  code: 'ENOENT',
  syscall: 'spawn cmd',
  path: 'cmd',
  spawnargs: [ '/c', 'start', '""', '/b', 'http://localhost:3000/' ]
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! fix-react-module@0.1.0 start: `react-scripts start`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the fix-react-module@0.1.0 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\Lucas\AppData\Roaming\npm-cache\_logs\2019-07-16T09_33_39_111Z-debug.log

I tried to change environment variables but I'm not sure what to add in PATH — LucasLaurens, Jul 16 '19 at 09:52
1. `npm cache clean --force`, 2. Delete `node_modules` folder, 3. `npm install` 4. `npm start`. Should fix the errors, works for me. Just to be safe delete `package-lock.json` too before doing `npm install` — Vaibhav Vishal, Jul 16 '19 at 09:54
I will try, but every time I create a new application, this error comes up again — LucasLaurens, Jul 16 '19 at 09:59
with : npx create-react-app app-example -> cd app-example -> npm start (it worked before) — LucasLaurens, Jul 16 '19 at 10:00
something is running on the same port probably, try changing, in MAC try, netstat -vanp tcp | grep 3000 — Surya, Jul 16 '19 at 10:01
clean the npm cache, should fix the errors. Not related to ports. — Vaibhav Vishal, Jul 16 '19 at 10:01
I will try to clean but I do not want the error to happen again with each new application — LucasLaurens, Jul 16 '19 at 10:04
https://stackoverflow.com/questions/48198/how-can-you-find-out-which-process-is-listening-on-a-port-on-windows this will happen anytime u try to use same port, which was not released earlier — Surya, Jul 16 '19 at 10:06
I tried to delete the cache and remove the modules and the installation of npm but it doesn't work And this is not the host ... Another idea? — LucasLaurens, Jul 16 '19 at 11:01

score 16 · Answer 1 · answered Jan 10 '20 at 16:32

16

Add C:\Windows\System32 to the global PATH environment variable.

answered Jan 10 '20 at 16:32

f.ardelian

5,632
7
33
49

1

This saved my day after running npx create-react-app 6 times reading other answers. – Akshay kn Jul 30 '20 at 12:10

score 9 · Answer 2 · edited Mar 11 '20 at 00:00

9

Solution 1

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 the 2nd steps. Navigate to your project folder and type this command >>>

rm -rf node_modules

rm package-lock.json

rm  yarn.lock

npm cache clear --force

npm install

Solution 3

Downgrade react-scripts in package.json file

edited Mar 11 '20 at 00:00

Dharman

21,838
18
57
107

answered Feb 05 '20 at 08:15

min456

91
1
2

New: npm cache clean --force – Timo Mar 09 '21 at 19:08

score 4 · Answer 3 · answered Aug 20 '19 at 18:53

I had the same problem after I tried to install Mongo DB. I found out that this problem only exists with react-scripts@3.0.0. Try to reinstall your npm with a different react script version. Simply go to your folder in command and reinstall like this:

npm install react-scripts@2.1.8
npm start

After that the app worked for me again.

score 1 · Answer 4 · answered Feb 07 '20 at 12:28

1

If someone hits this coming from Angular 2+, remove the --open from ng serve or run without this option.

answered Feb 07 '20 at 12:28

Shamitha Silva

1,801
1
16
28

score 1 · Answer 5 · answered Nov 20 '20 at 17:13

For all those Who've come to this problem from react scripts not starting. The solution is

Go to search bar and write environment variables. You should see an option to called edit system environment variables or something similar.
Under the Advanced section there is a enivronment variable button. click it.
After that you will see an option named path click on it.
click add button and add following directory C:\Windows\System32.
close down your editor and restart your command terminal. Problem should be resolved now

Problem with npm start (error : spawn cmd ENOENT)

5 Answers5

Linked