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
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...
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
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...
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
The text was updated successfully, but these errors were encountered:
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 😅
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.
After creating react project using npm , when I am facing the below issue after using npm start .
C:\Users\667855\my-app>npm 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
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
The text was updated successfully, but these errors were encountered: