A
A
Alexey Yakovlev2020-08-13 15:22:11
JavaScript
Alexey Yakovlev, 2020-08-13 15:22:11

Error when starting the server on react js, what should I do?

Created an application - create-react-app app. Run - npm start.
Mistake:

events.js:291
          throw er; // Unhandled 'error' event
          ^
    
    Error: spawn cmd ENOENT
        at Process.ChildProcess._handle.onexit (internal/child_process.js:268:19)
        at onErrorNT (internal/child_process.js:468:16)
        at processTicksAndRejections (internal/process/task_queues.js:80:21)     
    Emitted 'error' event on ChildProcess instance at:
        at Process.ChildProcess._handle.onexit (internal/child_process.js:274:12)
        at onErrorNT (internal/child_process.js:468:16)
        at processTicksAndRejections (internal/process/task_queues.js:80:21) {
      errno: -4058,
      code: 'ENOENT',
      syscall: 'spawn cmd',
      path: 'cmd',
      spawnargs: [ '/s', '/c', 'start', '""', '/b', '"http://localhost:3000/"' ]
    }
    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\Алекс\AppData\Roaming\npm-cache\_logs\2020-08-13T12_14_12_199Z-debug.log

Answer the question

In order to leave comments, you need to log in

2 answer(s)
A
Alexey Yakovlev, 2020-08-13
@aleshaykovlev

added a variable to the user's PATH environment - C:\Windows\System32

I
ilyashvts, 2020-08-13
@ilyashvts

Perhaps there was a problem with the modules during installation, try deleting node_modules and re-run npm install

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question