'npm start' fails after create-react-app
See original GitHub issuereact-scripts start
Starting the development server…
events.js:200 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:81: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:81: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! ppmtool-react-client@0.1.0 start: react-scripts start
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the ppmtool-react-client@0.1.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (1 by maintainers)
@Saheli95 , @emskaplann I did this and it worked for me-> Add the default variables in your machines PATH: C:\Windows\system32 C:\Windows C:\Windows\System32\Wbem
any other paths can be added to the end. Remember to have the npm paths as well: C:\Program Files\nodejs C:\Users{yourName}\AppData\Roaming\npm
Hope it helps!
Thank you @krishan93985. It worked. I don’t understand how, but works