You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Error: spawn cmd ENOENT
?[90m at Process.ChildProcess._handle.onexit (internal/child_process.js:266:19)?[39m
?[90m at onErrorNT (internal/child_process.js:468: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:272:12)?[39m
?[90m at onErrorNT (internal/child_process.js:468:16)?[39m
?[90m at processTicksAndRejections (internal/process/task_queues.js:84:21)?[39m {
errno: ?[33m-4058?[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:\Users\rupen\AppData\Roaming\npm-cache_logs\2019-12-08T20_27_22_195Z-debug.log
PS F:\ReactJS\practical-reach>
The text was updated successfully, but these errors were encountered:
INFO: Gracefully shutting down. Please wait...
PS F:\ReactJS\practical-reach> npm run start
Starting the development server...
events.js:196
throw er; // Unhandled 'error' event
^
Error: spawn cmd ENOENT
?[90m at Process.ChildProcess._handle.onexit (internal/child_process.js:266:19)?[39m
?[90m at onErrorNT (internal/child_process.js:468: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:272:12)?[39m
?[90m at onErrorNT (internal/child_process.js:468:16)?[39m
?[90m at processTicksAndRejections (internal/process/task_queues.js:84:21)?[39m {
errno: ?[33m-4058?[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:\Users\rupen\AppData\Roaming\npm-cache_logs\2019-12-08T20_27_22_195Z-debug.log
PS F:\ReactJS\practical-reach>
The text was updated successfully, but these errors were encountered: