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.

Problem - npm start

See original GitHub issue

Hello. I have a problem. I have created a project using “npx crate-react-app appname”. This is ok. But, when i enter “npm start”, it shows me this:

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:467: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:467:16) at processTicksAndRejections (internal/process/task_queues.js:84:21) { errno: -4058, code: ‘ENOENT’, syscall: ‘spawn cmd’, path: ‘cmd’, spawnargs: [ ‘/s’, ‘/c’, ‘start’, ‘“”’, ‘/b’, ‘“http://localhost:3000”’ ] } npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! appname@0.1.0 start: react-scripts start npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the appname@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\my name\AppData\Roaming\npm-cache_logs\2020-04-18T14_23_16_209Z-debug.log

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:9

github_iconTop GitHub Comments

1reaction
mateo500commented, Apr 18, 2020

I had a similar issue with unity a couple of months ago, i solved it adding this line at the end of the PATH enviroment varible.

C:\Windows\System32

example Screenshot from 2020-04-18 12 51 10

hope that this works for you.

0reactions
newBieIrfancommented, Apr 19, 2020

@mateo500 Hey, forgot to inform, it started working. I think it was some permission issues, I run my command prompt as administrator and then install create-react-app and then create an app and if I run, it runs. But, i’ll even try as you said, just to make sure that I don’t get into trouble in future!

Thanks 😃

Read more comments on GitHub >

github_iconTop Results From Across the Web

How to fix npm start command not working - Nathan Sebhastian
How to fix npm start command not working · Check if you have a package.json file in your project · Check if you...
Read more >
npm start giving error in node.js - Stack Overflow
The error suggests that the ./bin/www directory is not found. Paths specified with a dot are relative to the current directory, ...
Read more >
npm ERR! Missing script: "start" [Solved] | bobbyhadz
To solve the npm ERR! Missing script: "start" error, make sure to add a start command to the scripts object in your package.json...
Read more >
npm err! missing script: start Solution - Career Karma
If you type npm start and get the npm err! missing script: start error, there must be a missing line in the script...
Read more >
"The NPM script 'start' exited without indicating that the create ...
From the error message, it seems that the react-scripts.js module was not found, try to check the package.json file whether it contains the ......
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