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.

npm start fail on creat-react-app

See original GitHub issue

$ cd /c/Users/Engr_Sodiq/first-app

Engr_Sodiq@Harmatan MINGW64 ~/first-app (master) $ npm start

first-app@0.1.0 start C:\Users\Engr_Sodiq\first-app react-scripts start

Starting the development server…

events.js:287 throw er; // Unhandled ‘error’ event ^

Error: spawn cmd ENOENT ←[90m at Process.ChildProcess._handle.onexit (internal/child_process.js:267:19)←[39m ←[90m at onErrorNT (internal/child_process.js:469:16)←[39m ←[90m at processTicksAndRejections (internal/process/task_queues.js:84:21)←[39m Emitted ‘error’ event on ChildProcess instance at: ←[90m at Process.ChildProcess._handle.onexit (internal/child_process.js:273:12)←[39m ←[90m at onErrorNT (internal/child_process.js:469:16)←[39m ←[90m at processTicksAndRejections (internal/process/task_queues.js:84: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! first-app@0.1.0 start: react-scripts start npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the first-app@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\Engr_Sodiq\AppData\Roaming\npm-cache_logs\2020-04-26T16_14_32_307Z-debug.log

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:10 (2 by maintainers)

github_iconTop GitHub Comments

7reactions
Mahmoudhadidicommented, May 10, 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 react-scripts@2.1.8 npm start

2reactions
Dev-Harmattancommented, Apr 29, 2020

Reinstall your node version and go to appData/roaming file inside your root and delete the npm and npm-cache, after that perform these actions.

Install node. On the terminal: do these npm uninstall -g create-react-app

npx create-react-app my-app cd my-app npm start.

Read more comments on GitHub >

github_iconTop Results From Across the Web

javascript - npm start error with create-react-app - Stack Overflow
Go to your C:\Users\<USER>\AppData\Roaming · Delete npm and npm-cache directories... · Go back to your application directory and remove ...
Read more >
'Npm start' fails on react-scripts-start · Issue #9594 - GitHub
I have 4 projects bootstrapped using create-react-app. One of the projects is working completely fine. However, with the other three, ...
Read more >
React npm start not working? - The freeCodeCamp Forum
Not sure what's going on here as Ive just started using React. But when I use create-react-app and then npm start I get...
Read more >
Create a New React App
When you're ready to deploy to production, running npm run build will create an optimized build of your app in the build folder....
Read more >
Troubleshooting - Create React App
npm start fail due to watch error​ ... If you are using a Linux operating system and see an error similar to: ENOSPC:...
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