
Camilo Alexander Velandia Velandia
Preguntanecesito ayuda para solucionar esto
Starting the development server…
events.js:298
throw er; // Unhandled ‘error’ event
^
Error: spawn cmd.exe ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:267:19)
at onErrorNT (internal/child_process.js:469:16)
at processTicksAndRejections (internal/process/task_queues.js:84:21)
Emitted ‘error’ event on ChildProcess instance at:
at Process.ChildProcess._handle.onexit (internal/child_process.js:273:12)
at onErrorNT (internal/child_process.js:469:16)
at processTicksAndRejections (internal/process/task_queues.js:84:21) {
errno: ‘ENOENT’,
code: ‘ENOENT’,
syscall: ‘spawn cmd.exe’,
path: ‘cmd.exe’,
spawnargs: [ ‘/c’, ‘start’, ‘""’, ‘/b’, ‘http://localhost:3000/’ ]
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! learn-react@0.1.0 start:
react-scripts start
npm ERR! Exit status 1npm ERR!
npm ERR! Failed at the learn-react@0.1.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! /root/.npm/_logs/2020-02-13T16_24_01_712Z-debug.log
ya actualiza node, y tambien use npx create-react-app
Dario Asaro
borra la carpeta node_modules y el package json lock, despues ejecuta desde la consola npm install, eso deberia resolverlo