Note that the development build is not optimized.
To create a production build, run npm run build.
events.js:292
throw er; // Unhandled ‘error’ event
^
Error: spawn cmd ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:269:19)
at onErrorNT (internal/child_process.js:465: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:275:12)
at onErrorNT (internal/child_process.js:465:16)
at processTicksAndRejections (internal/process/task_queues.js:80:21) {
errno: -4058,
code: ‘ENOENT’,
syscall: ‘spawn cmd’,
path: ‘cmd’,
spawnargs: [ ‘/c’, ‘start’, ‘“”’, ‘/b’, ‘http://localhost:9528/’ ]
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! flash-vue-admin@4.1.0 dev: vue-cli-service serve --open
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the flash-vue-admin@4.1.0 dev 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:
02T04_57_12_486Z-debug.log
