Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue in starting react application using "npm start " #8098

Closed
kumaramit06 opened this issue Dec 6, 2019 · 3 comments
Closed

Issue in starting react application using "npm start " #8098

kumaramit06 opened this issue Dec 6, 2019 · 3 comments

Comments

@kumaramit06
Copy link

After creating react project using npm , when I am facing the below issue after using npm start .

C:\Users\667855\my-app>npm start

[email protected] start C:\Users\667855\my-app
react-scripts start

i 「wds」: Project is running at http://10.227.11.119/
i 「wds」: webpack output is served from /
i 「wds」: Content not from webpack is served from C:\Users\667855\my-app\public
i 「wds」: 404s will fallback to /index.html
Starting the development server...

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

Error: spawn cmd ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:201:19)
at onErrorNT (internal/child_process.js:379:16)
at process._tickCallback (internal/process/next_tick.js:114: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:\Users\667855\AppData\Roaming\npm-cache_logs\2019-12-06T09_32_44_032Z-debug.log

C:\Users\667855\my-app>

C:\Users\667855\my-app>npm cache clean --force
npm WARN using --force I sure hope you know what you are doing.
Terminate batch job (Y/N)? y

C:\Users\667855\my-app>npm start

[email protected] start C:\Users\667855\my-app
react-scripts start

i 「wds」: Project is running at http://10.227.11.119/
i 「wds」: webpack output is served from /
i 「wds」: Content not from webpack is served from C:\Users\667855\my-app\public
i 「wds」: 404s will fallback to /index.html
Starting the development server...

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

Error: spawn cmd ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:201:19)
at onErrorNT (internal/child_process.js:379:16)
at process._tickCallback (internal/process/next_tick.js:114: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:\Users\667855\AppData\Roaming\npm-cache_logs\2019-12-06T09_45_49_204Z-debug.log

@gilbertoayala12
Copy link

Have you tried deleting the node_modules folder and then reinstall the dependencies?
I'm not sure if it solves your issue but it's something I do often when everything else fails 😅

@creativesuraj
Copy link

creativesuraj commented Dec 6, 2019

I think the problem is with your node's version, downgrade the version and try.
I use v11.10.1

@heyimalex
Copy link
Contributor

Duplicate of #7251. The error is triggered because cmd isn't in your system path. The short term solution is to put cmd in your path by adding C:\Windows\System32\ to it.

@lock lock bot locked and limited conversation to collaborators Dec 11, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants