title: I can't solve Error while running npm Start
body: <p>I have an issue please. Each time I set up a react project, either with create react app or using webpack or whatever, I just get stuck at NPM start. It always returns an error. Please I am fed up with this. Can someone tell me what the issue might be?
  But what bugs me the most is, I use Next.js, and each time I run Npm start on Nextjs dev server, it works fine... Please what might be the issue with my react app?</p>
  
  <p>Here's the error:</p>
  
  <pre><code>C:\Users\Kelly\Desktop\My webpack react app&gt;npm start
  
  &gt; webpackreactapp@1.0.0 start C:\Users\Kelly\Desktop\My webpack react app
  &gt; webpack-dev-server --mode development --open --hot
  
  i ｢wds｣: Project is running at http://localhost:8080/
  i ｢wds｣: webpack output is served from /
  i ｢wds｣: Content not from webpack is served from C:\Users\Kelly\Desktop\My webpack react app
  events.js:298
        throw er; // Unhandled 'error' event
        ^
  
  Error: spawn cmd ENOENT
  ←[90m    at Process.ChildProcess._handle.onexit (internal/child_process.js:267:19)←[39m
  ←[90m    at onErrorNT (internal/child_process.js:467: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:273:12)←[39m
  ←[90m    at onErrorNT (internal/child_process.js:467: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'/c'←[39m, ←[32m'start'←[39m, ←[32m'""'←[39m, ←[32m'/b'←[39m, ←[32m'http://localhost:8080/'←[39m ]
  }
  npm ERR! code ELIFECYCLE
  npm ERR! errno 1
  npm ERR! webpackreactapp@1.0.0 start: `webpack-dev-server --mode development --open --hot`
  npm ERR! Exit status 1
  npm ERR!
  npm ERR! Failed at the webpackreactapp@1.0.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\Kelly\AppData\Roaming\npm-cache\_logs\2020-04-07T07_23_56_199Z-debug.log
  </code></pre>