$ npminstall
$ npm run build
> vue-devtools@5.3.3 build D:\GitRespiratory\vue-devtools
>cd packages/shell-chrome && cross-env NODE_ENV=production webpack --progress --hide-modules
'webpack' is not recognized as an internal or external command,
operable program or batch file.
events.js:174
throw er; // Unhandled 'error' event
^
Error: spawn webpack ENOENT
at notFoundError (D:\GitRespiratory\vue-devtools\node_modules\cross-spawn\lib\enoent.js:6:26)
at verifyENOENT (D:\GitRespiratory\vue-devtools\node_modules\cross-spawn\lib\enoent.js:40:16)
at ChildProcess.cp.emit (D:\GitRespiratory\vue-devtools\node_modules\cross-spawn\lib\enoent.js:27:25)
at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)
Emitted 'error' event at:
at ChildProcess.cp.emit (D:\GitRespiratory\vue-devtools\node_modules\cross-spawn\lib\enoent.js:30:37)
at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! vue-devtools@5.3.3 build: `cd packages/shell-chrome && cross-env NODE_ENV=production webpack --progress --hide-modules`npm ERR! Exit status 1
npm ERR!npm ERR! Failed at the vue-devtools@5.3.3 build 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\Administrator\AppData\Roaming\npm-cache\_logs\2019-12-12T02_12_20_581Z-debug.log