The latest articles on DEV Community by rpraneeth (@rpraneeth). https://dev.to/rpraneeth https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F381987%2F56ab85aa-11a9-46a5-bf6a-e5ba42245b44.png https://dev.to/rpraneeth en rpraneeth Sat, 09 May 2020 10:27:16 +0000 https://dev.to/rpraneeth/react-js-issue-26f8 https://dev.to/rpraneeth/react-js-issue-26f8 <p>events.js:287<br> throw er; // Unhandled 'error' event<br> ^</p> <p>Error: spawn cmd ENOENT<br> ←[90m at Process.ChildProcess._handle.onexit (internal/child_process.js:267:19)←[39m<br> ←[90m at onErrorNT (internal/child_process.js:469:16)←[39m<br> ←[90m at processTicksAndRejections (internal/process/task_queues.js:84:21)←[39m<br> Emitted 'error' event on ChildProcess instance at:<br> ←[90m at Process.ChildProcess._handle.onexit (internal/child_process.js:273:12)←[39m<br> ←[90m at onErrorNT (internal/child_process.js:469:16)←[39m<br> ←[90m at processTicksAndRejections (internal/process/task_queues.js:84:21)←[39m {<br> errno: ←[32m'ENOENT'←[39m,<br> code: ←[32m'ENOENT'←[39m,<br> syscall: ←[32m'spawn cmd'←[39m,<br> path: ←[32m'cmd'←[39m,<br> spawnargs: [ ←[32m'/s'←[39m, ←[32m'/c'←[39m, ←[32m'start'←[39m, ←[32m'""'←[39m, ←[32m'/b'←[39m, ←[32m'"<a href="http://localhost:3000%22'%E2%86%90%5B39m">http://localhost:3000"'←[39m</a> ]<br> }<br> npm ERR! code ELIFECYCLE<br> npm ERR! errno 1<br> npm ERR! <a href="mailto:hello-world@0.1.0">hello-world@0.1.0</a> start: <code>react-scripts start</code><br> npm ERR! Exit status 1<br> npm ERR!<br> npm ERR! Failed at the <a href="mailto:hello-world@0.1.0">hello-world@0.1.0</a> start script.<br> npm ERR! This is probably not a problem with npm. There is likely additional logging output above.</p> <p>npm ERR! A complete log of this run can be found in:<br> npm ERR! C:\Users\win7\AppData\Roaming\npm-cache_logs\2020-05-09T10_07_04_308Z-debug.log</p> <p>help me</p>