Create-react-app: React npm start con't run and open the localhost:3000

Created on 16 May 2019 · 36Comments · Source: facebook/create-react-app

[email protected] start C:Usersmohammad ahmadDesktopReact Projectsapp
react-scripts start

Starting the development server...

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

Error: spawn cmd ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:240:19)
at onErrorNT (internal/child_process.js:415:16)
at process._tickCallback (internal/process/next_tick.js:63:19)
Emitted 'error' event at:
at Process.ChildProcess._handle.onexit (internal/child_process.js:246:12)
at onErrorNT (internal/child_process.js:415:16)
at process._tickCallback (internal/process/next_tick.js:63:19)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: react-scripts start
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] 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:Usersmohammad ahmadAppDataRoamingnpm-cache_logs2019-05-15T20_48_25_193Z-debug.log

needs investigation

Source

mohammad-dc

👍8

Most helpful comment

Was helping someone with this problem on their Windows box and came across the following SO article and it did the trick.

I checked system variables one more time and found the cause of the problem: missing C:\Windows\System32\ variable. I added it and that solved my problem

More detailed instructions that didn't get labeled as the answer:

Goto > Control PanelSystem and SecuritySystemAdvance system settingEnviroment variable and set system variables path C:\Windows\System32\ variable and restart your System.

Took a fair amount of Googling to arrive there. Hopefully this helps people out so they aren't forced to try a particular, now outdated, version of react-scripts just to get their React app running.

creativetim on 23 May 2019

👍21 🎉8 👀4 🚀3 😄3 ❤2

All 36 comments

Hi, i confirm that i have the same problem , since yesterday

alexreu on 16 May 2019

Finally i downgrade my react-scripts in package.json to this version : "react-scripts": "^2.1.8" and it works for me

alexreu on 16 May 2019

👍15 ❤7 🚀2 🎉1

Hi, I have the same problem , since morning

When I am trying to create new app using create-react-app and trying to start it thorwing below error. Though old apps are still running. Please help me in this as I have already tried all solutions available on stackoverflow and issue list.

OS: WIN 8,
NODE : v10.15.3
NPM: 6.4.1

create-react-app

[email protected]
[email protected]
[email protected]

React npm start throwing the error and not opening the localhost:3000

Error On Cmd:

[email protected] start C:UI DevReact-Demomy-app
react-scripts start

Starting the development server...

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

Error: spawn cmd ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:240:19)
at onErrorNT (internal/child_process.js:415:16)
at process._tickCallback (internal/process/next_tick.js:63:19)
Emitted 'error' event at:
at Process.ChildProcess._handle.onexit (internal/child_process.js:246:12)
at onErrorNT (internal/child_process.js:415:16)
at process._tickCallback (internal/process/next_tick.js:63:19)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: react-scripts start
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional log
ging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! C:UsersMyPCAppDataRoamingnpm-cache_logs2019-05-16T08_07_
48_884Z-debug.log

SId02 on 16 May 2019

to work around the problem i use this old version of react-scripts :
[email protected]

alexreu on 16 May 2019

Here is the message I get in my terminal, it seems to be something to do with the version of babel-jest in the react-scripts 3.0.1 package:
The react-scripts package provided by Create React App requires a dependency: "babel-jest": "^24.8.0" However, a different version of babel-jest was detected higher up in the tree: npm ls babel-jest [email protected] └─┬ [email protected] ├── [email protected] └─┬ [email protected] └─┬ [email protected] └─┬ [email protected] └── [email protected] deduped

Once I rolled back to react-scripts 3.0.0 npm start works fine.

alteredco on 17 May 2019

Was helping someone with this problem on their Windows box and came across the following SO article and it did the trick.

I checked system variables one more time and found the cause of the problem: missing C:\Windows\System32\ variable. I added it and that solved my problem

More detailed instructions that didn't get labeled as the answer:

Goto > Control PanelSystem and SecuritySystemAdvance system settingEnviroment variable and set system variables path C:\Windows\System32\ variable and restart your System.

creativetim on 23 May 2019

👍21 🎉8 👀4 🚀3 😄3 ❤2

i have some problem too, check yours environtment variable first, this is mine and its work
Capture
Capture2
Capture3

rafafauzi on 31 May 2019

👍2

Finally i downgrade my react-scripts in package.json to this version : "react-scripts": "^2.1.8" and it works for me

This worked for me also. Pretty weird, though.

Smytt on 19 Jul 2019

👍4

Finally i downgrade my react-scripts in package.json to this version : "react-scripts": "^2.1.8" and it works for me

This worked for me also. Pretty weird, though.

So, does that mean the latest version of React (v3.2) is not usable ??

m-vignesh on 30 Aug 2019

Finally i downgrade my react-scripts in package.json to this version : "react-scripts": "^2.1.8" and it works for me

This worked for me also. Pretty weird, though.

works for me thanks

waqaryounis7564 on 26 Sep 2019

Yup, downgrading works~!

CanaanGM on 7 Oct 2019

instead of npx, use npm i create-react-app.

waqaryounis7564 on 8 Oct 2019

Downgrading works (y)

prathapgunasekara on 4 Nov 2019

Yep!! Downgrading works for me

chamath-naveen on 14 Nov 2019

How did you downgrade it, do you have any links or any video available ? Please send me. Thanks in advance for the solutions.

RajAakash on 24 Nov 2019

How did you downgrade it, do you have any links or any video available ? Please send me. Thanks in advance for the solutions.

First, go to the package.json file then find out the "react-scripts" tag and make it like this "react-scripts": "^2.1.8" after that remove the node modules folder and again install node modules using npm install. I think these steps will help you.

chamath-naveen on 24 Nov 2019

👍1

what hapen?/
please help me

Starting the development server...

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

Error: spawn cmd ENOENT
←[90m at Process.ChildProcess._handle.onexit (internal/child_process.js:264:19)←[39m
←[90m at onErrorNT (internal/child_process.js:456:16)←[39m
←[90m at processTicksAndRejections (internal/process/task_queues.js:80:21)←[39m
Emitted 'error' event on ChildProcess instance at:
←[90m at Process.ChildProcess._handle.onexit (internal/child_process.js:270:12)←[39m
←[90m at onErrorNT (internal/child_process.js:456:16)←[39m
←[90m at processTicksAndRejections (internal/process/task_queues.js:80:21)←[39m {
errno: ←[32m'ENOENT'←[39m,
code: ←[32m'ENOENT'←[39m,
syscall: ←[32m'spawn cmd'←[39m,
path: ←[32m'cmd'←[39m,
spawnargs: [ ←[32m'/s'←[39m, ←[32m'/c'←[39m, ←[32m'start'←[39m, ←[32m'""'←[39m, ←[32m'/b'←[39m, ←[32m'"http://localhost:3000/"'←[39m ]
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: react-scripts start
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] 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:UsersAmir MousaviAppDataRoamingnpm-cache_logs2019-12-18T08_49_45_731Z-debug.log

TheMousavi on 18 Dec 2019

Finally i downgrade my react-scripts in package.json to this version : "react-scripts": "^2.1.8" and it works for me

thank my project is worked good job

TheMousavi on 21 Dec 2019

You could downgrade with help of this scrip and writing that on your terminal then everything should be work:

create-react-app my-app
cd my-app
npm install [email protected]
npm start

Pa22 on 3 Mar 2020

👍7 ❤3 👀1 🚀1 😕1 🎉1 😄1

You could downgrade with help of this scrip and writing that on your terminal then everything should be work:

create-react-app my-app
cd my-app
npm install [email protected]
npm start

Thanks, this worked. I legit got tired of trying all the different methods mentioned across github issues and stack overflow through npm and yarn multiple times, in the end this worked.

ShivS01 on 21 Apr 2020

[email protected] start C:Usersmohammad ahmadDesktopReact Projectsapp
react-scripts start

Starting the development server...

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

Error: spawn cmd ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:240:19)
at onErrorNT (internal/child_process.js:415:16)
at process._tickCallback (internal/process/next_tick.js:63:19)
Emitted 'error' event at:
at Process.ChildProcess._handle.onexit (internal/child_process.js:246:12)
at onErrorNT (internal/child_process.js:415:16)
at process._tickCallback (internal/process/next_tick.js:63:19)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: react-scripts start
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] 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:Usersmohammad ahmadAppDataRoamingnpm-cache_logs2019-05-15T20_48_25_193Z-debug.log

its working fine for me when i changed the react-scripts version: "3.4.1" to "react-scripts": "2.1.8" in package.json .

Vivekch05 on 24 Apr 2020

I checked system variables one more time and found the cause of the problem: missing C:WindowsSystem32 variable. I added it and that solved my problem

This is working and seems a better solution than the workaround of downgrading react-scripts version. Thanks @creativetim

rambabusaravanan on 25 Apr 2020

👍1

Was helping someone with this problem on their Windows box and came across the following SO article and it did the trick.

I checked system variables one more time and found the cause of the problem: missing C:\Windows\System32\ variable. I added it and that solved my problem

More detailed instructions that didn't get labeled as the answer:

Goto > Control PanelSystem and SecuritySystemAdvance system settingEnviroment variable and set system variables path C:\Windows\System32\ variable and restart your System.

Took a fair amount of Googling to arrive there. Hopefully this helps people out so they aren't forced to try a particular, now outdated, version of react-scripts just to get their React app running.

Tried this, this also works. better than downgrading. Thanks a lot!

ShivS01 on 28 Apr 2020

Firstly type rm node_modules, once the node modules is been deleted, type npm install and then yarn --build, restart the IDE. the run the npm start command it will work.

jr17vbc on 20 May 2020

👍1

Firstly type rm node_modules, once the node modules is been deleted, type npm install and then yarn --build, restart the IDE. the run the npm start command it will work.

this works for me

Denzi0 on 15 Jun 2020

I had the same problem. Adding CWindows System32 to the system path variable worked for me.

jadocoder on 2 Jul 2020

I had the same problem. Adding CWindows System32 to the system path variable worked for me.

it works thanks bro

ManishPanwar556 on 2 Jul 2020

non of the above doesn't work for me, any other way to solve this problem ???

FarrukhNuridinov on 25 Jul 2020

E:Web developmentintern-gatereact-test>yarn start
yarn run v1.22.4
$ react-scripts start
Starting the development server...

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

Error: spawn cmd 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)
Emitted 'error' event on ChildProcess instance at:
at Process.ChildProcess._handle.onexit (internal/child_process.js:273:12)
at onErrorNT (internal/child_process.js:469:16)
at processTicksAndRejections (internal/process/task_queues.js:84:21) {
errno: 'ENOENT',
code: 'ENOENT',
syscall: 'spawn cmd',
path: 'cmd',
spawnargs: [ '/s', '/c', 'start', '""', '/b', '"http://localhost:3000"' ]
Screenshot (1081)

}
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

E:Web developmentintern-gatereact-test>cd ..events.js:292
The system cannot find the path specified.

E:Web developmentintern-gatereact-test> throw er; // Unhandled 'error' event

Satyam62 on 8 Aug 2020

i tried all above steps but still no answer solved my problem

Mylifewithmyexperiment on 20 Aug 2020

You could downgrade with help of this scrip and writing that on your terminal then everything should be work:

create-react-app my-app
cd my-app
npm install [email protected]
npm start

thanks alot kind stranger... i literally fcuked myself on figuring out the problem

adiruv on 24 Aug 2020

Did anyone figure out what's the issue. Was facing the same issue and only fixed it by downgrading react. Question is why

muteshi on 30 Aug 2020

You could downgrade with help of this scrip and writing that on your terminal then everything should be work:

create-react-app my-app
cd my-app
npm install [email protected]
npm start

thanks bro it works.

gaurav0000000 on 6 Sep 2020

To solve this issue , insert the following path in your system and user variables.

C:WindowsSystem32WindowsPowerShellv1.0

Set this path in both User and system variables.
Next, open Nodejs command prompt or terminal and type npm start

I hope this solution will work !

Debdyuti-01 on 22 Sep 2020

Help me the error is

[email protected] start D:My WorkLearningthree
webpack-dev-server --mode development --open

i ｢wds｣: Project is running at http://localhost:8080/
i ｢wds｣: webpack output is served from /
i ｢wds｣: Content not from webpack is served from ./dist
events.js:292
throw er; // Unhandled 'error' event
^

Error: spawn cmd ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:269:19)
at onErrorNT (internal/child_process.js:465:16)
at processTicksAndRejections (internal/process/task_queues.js:80:21)
Emitted 'error' event on ChildProcess instance at:
at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12)
at onErrorNT (internal/child_process.js:465:16)
at processTicksAndRejections (internal/process/task_queues.js:80:21) {
errno: -4058,
code: 'ENOENT',
syscall: 'spawn cmd',
path: 'cmd',
spawnargs: [ '/c', 'start', '""', '/b', 'http://localhost:8080/' ]
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: webpack-dev-server --mode development --open
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] 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:UsersAdit KarkiAppDataRoamingnpm-cache_logs2020-10-28T06_57_13_281Z-debug.log
The terminal process "C:Windowssystem32cmd.exe /d /c npm run start" terminated with exit code: 1.