cross-env not found on npm run dev

Are you required to use a virtual machine?

Since you are using windows I would recommend using Laragon unless you are otherwise required to use a virtual machine.

You avoid all the hassle of setting up machines

I have read about "the ease of using Homestead" so often, and I heard it in a lot of Jeff's video's, that i wanted to try it out. So it's not required, but i'd like to try it out.

Plus, I don't mind being a tester, to help find issues, so me installing it is me helping out.

I will take a look at Laragon later. Thanks

yes follow @WebKenth if u using window I recommended use laragon.org here is videos https://www.youtube.com/watch?v=pHQOdXY2AZU&list=PL0Nx259JjLcGqXg5kpTifqQ9GFoQ2qGPy

What does your package.json look like?

Original:

{
  "private": true,
  "scripts": {
    "dev": "cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js",
    "watch": "cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --watch --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js",
    "watch-poll": "cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --watch --watch-poll --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js",
    "hot": "cross-env NODE_ENV=development node_modules/webpack-dev-server/bin/webpack-dev-server.js --inline --hot --config=node_modules/laravel-mix/setup/webpack.config.js",
    "production": "cross-env NODE_ENV=production node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js"
  },
  "devDependencies": {
    "axios": "^0.15.3",
    "bootstrap-sass": "^3.3.7",
    "cross-env": "^3.2.4",
    "jquery": "^3.1.1",
    "laravel-mix": "^0.8.3",
    "lodash": "^4.17.4",
    "vue": "^2.1.10"
  }
}

Edited:

{
  "private": true,
  "scripts": {
    "dev": "node node_modules/cross-env/dist/bin/cross-env.js NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js",
    "watch": "node node_modules/cross-env/dist/bin/cross-env.js NODE_ENV=development node_modules/webpack/bin/webpack.js --watch --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js",
    "watch-poll": "cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --watch --watch-poll --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js",
    "hot": "node node_modules/cross-env/dist/bin/cross-env.js NODE_ENV=development node_modules/webpack-dev-server/bin/webpack-dev-server.js --inline --hot --config=node_modules/laravel-mix/setup/webpack.config.js",
    "production": "node node_modules/cross-env/dist/bin/cross-env.js NODE_ENV=production node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js"
  },
  "devDependencies": {
    "axios": "^0.15.3",
    "bootstrap-sass": "^3.3.7",
    "cross-env": "^3.2.4",
    "jquery": "^3.1.1",
    "laravel-mix": "^0.8.3",
    "lodash": "^4.17.4",
    "vue": "^2.1.10"
  }
}

You need to check if that path exists in your node_modules folder (path of the cross-env library). At times it's located within the dist folder, other times it's located outside it.

Thanks @Stretsh! I finally got it to work changing my package.json scripts to yours.

Stretsh your solution fixed my npm run dev problem but for watch it runs but doesn't sense file changes. Any ideas?

I think it could be linked to the same reason why the full path should be used instead of just cross-env. Maybe a permission problem? I still have no clue...

I haven't tried it since posting this, so I have no idea if it was fixed or not. I wonder if i should report a bug...

Try npm install cross-env -g.

After npm update try npm install --save. I tried too many solutions and only saving them worked!

I have tried lots of solutions and finally got windows 10 to create symbolic links, which is the root of most of window users issues heartache.

First turn on Windows 10 Developer. http://www.wikihow.com/Enable-Developer-Mode-in-Windows-10 Search for Developer Features in Settings change it to Developer Mode.

Secondly make sure you have permission to make symbolic links. https://superuser.com/questions/104845/permission-to-make-symbolic-links-in-windows-7 Search for local security policy and click through local security policy \ local polices \ user right assignment\ create symbolic link Give yourself permission. Note: put your user name in all lowercase and check names. Oddly this worked for me. But spelling it with mixed case did not.

Lastly When you open git bash, run it as administrator. Now this is a point of frustration because I often forget. So make it default to open as admin. Make a shortcut on the desktop for git bash. right click on the shortcut \ properties\ advance and check run as administrator.

Reboot the machine and you should be much better off.

If somebody know how to paste screen shots please let me know. I cant get them in here.

I am doing Laracast's "laravel-from-scratch-2017/episodes/14" and "npm run development" is dying with fatal errors on me, too. Win10/Vagrant/Homestead/Laravel 5.6 environment. Error:

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\n throw er; // Unhandled 'error' event\n ^\n

Error: spawn node_modules/webpack/bin/webpack.js ENOENT\n 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:686:11) at startup (bootstrap_node.js:187:16) at bootstrap_node.js:608:3 npm ERR! code ELIFECYCLE npm ERR! errno 1 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. 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! /home/vagrant/.npm/logs/2018-04-09T1801_23_306Z-debug.log

A HUGE part of getting past my cross-env grief involved running the following command:

npm rebuild

Me installing normal without laragon or Virtual host. after the hours of research i found the solution. here is how i did

1. npm install cross-env -g
2. npm install --save

after that npm run dev or npm run build Boom! Laravel Mix Build Successful it is working.....

@VAGGELIS2018 - This solved my cross-env problem. npm install --save

when i run yarn watch then this error massage shows:

dev npm run development

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

[webpack-cli] Error: Unknown option '--hide-modules' [webpack-cli] Run 'webpack --help' to see available commands and options