npm run dev

 

> @ dev /var/www/html

> npm run development

 

 

> @ development /var/www/html

> cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js

 

events.js:183

      throw er; // Unhandled 'error' event

      ^

 

Error: spawn node_modules/webpack/bin/webpack.js ENOENT

    at _errnoException (util.js:1022:11)

    at Process.ChildProcess._handle.onexit (internal/child_process.js:190:19)

    at onErrorNT (internal/child_process.js:372:16)

    at _combinedTickCallback (internal/process/next_tick.js:138:11)

    at process._tickCallback (internal/process/next_tick.js:180:9)

    at Function.Module.runMain (module.js:695:11)

    at startup (bootstrap_node.js:188:16)

    at bootstrap_node.js:609:3

 

npm ERR! Linux 5.0.0-29-generic

npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "run" "development"

npm ERR! node v8.10.0

npm ERR! npm  v3.5.2

npm ERR! code ELIFECYCLE

npm ERR! @ development: `cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js`

npm ERR! Exit status 1

npm ERR!

npm ERR! Failed at the @ development script 'cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js'.

npm ERR! Make sure you have the latest version of node.js and npm installed.

npm ERR! If you do, this is most likely a problem with the  package,

npm ERR! not with npm itself.

npm ERR! Tell the author that this fails on your system:

npm ERR!     cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js

npm ERR! You can get information on how to open an issue for this project with:

npm ERR!     npm bugs

npm ERR! Or if that isn't available, you can get their info via:

 

 

npm ERR! Failed at the @ dev script 'npm run development'.

npm ERR! Or if that isn't available, you can get their info via:

npm ERR!     npm owner ls

npm ERR! There is likely additional logging output above.

 

npm ERR! Please include the following file with any support request:

npm ERR!     /var/www/html/npm-debug.log