Laravel 5 4 cross-env Is Not Recognized as an Internal or External Command

Question

I m trying to run npm run dev for Laravel Mix and I get this error    gt    dev D  projects ptcs  gt  cross-env NODE ENV development webpack --progress --hide-modules -- config node modules laravel-mix setup webpack config js   cross-env  is not recognized as an internal or external command  operable program or batch file  npm ERR  code ELIFECYCLE npm ERR  errno 1 npm ERR    dev   cross-env NODE ENV development webpack --progress --hide- modules --config node modules laravel-mix setup webpack config js  npm ERR  Exit status 1 npm ERR  npm ERR  Failed at the   dev script    I updated node js to 6 11 0 and npm to 5 2 0  but it didn t help  I m running Homestead on Windows 7

User · Answer

Your error states that cross-env is not installed      cross-env  is not recognized as an internal or external command  operable program or batch file    You just need to run  npm install cross-env

User · Answer

First run   rm -rf node modules rm package-lock json yarn lock npm cache clear --force   Then run the command  npm install cross-env  npm install    and then you can also run   npm run dev

User · Answer

I think this log entry Local package json exists  but node modules missing  did you mean to install  has gave me the solution    npm install  amp  amp  npm run dev

User · Answer

For me simply run   npm install cross-env   was enough

User · Answer

You are getting the error because you might not have run the command npm install first   i e  First  run npm install and then npm run dev

User · Answer

Before try running npm run dev please run npm install --no-bin-links in the project directory  this will install all required packages  Also check this link for compiling instruction  https   laravel com docs 5 4 mix  Also double check in your conf file  wherever you find something like this   something  cross-env bin  something   change it to    something  cross-env dist bin  something   If you are using homestead  in package json paste this       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 3        jquery     3 1 1        laravel-mix     0 8 1        lodash     4 17 4        vue     2 1 10          Also check this link  https   github com JeffreyWay laravel-mix issues 478

User · Answer

Delete the node modules folder  Then you should run the commands   npm install --no-bin-links  npm run dev   It s worked on my Laravel 5 5 and Windows

User · Answer

Try to run npm run dev in powershell  This worked for me

User · Answer

You need to make cross-env working globally instead of having it in the project   1  remove node modules folder  2  run      npm install --global cross-env   3  remove  cross-env     5 0 1   from package json file devDependencies section  Actually  you can skip this step and keep package json intact  If you prefer   4  run      npm install --no-bin-links   5  run     npm run dev   and see it working  P S Tested on Windows 10 with Laravel-5 4  P P S Windows 10 with Laravel-5 6 does not have this problem  thus updating is an alternative solution

User · Answer

According to this issue comment  editing cross-env path will fix the problem  Change cross-env to node node modules cross-env dist bin cross-env js in package json like this        dev    npm run development        development    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    npm run watch -- --watch-poll        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        prod    npm run production        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

User · Answer

The following worked for Laravel 7 x  and should probably work for any other version as well given the nature of the issue    npm uninstall --save-dev cross-env npm install -g cross-env   Just moving cross-env from being a local devDependency to a globally available package

User · Answer

Just npm install --save-dev cross-env in the root directory of your project

User · Answer

I real all the solution but there is not a standard solution    JUST REMOVE NODEJS AND INSTALL THE LATEST VERSION OF NODEJS instead of many bad shortcut solutions

User · Answer

Following these steps solved my problem    Delete node modules directory Delete package-lock json file Start command prompt as Administrator  lt - important  Run npm install Run npm run dev

User · Answer

There is the same problem in Linux OS  The issue is related on Windows OS  but Homestead is a Ubuntu VM  and the solution posted works strongly good in others SO  I applied the commands sugested by flik  and the problems was solved  I only used the following commands   I only used the following commands  rm -rf node modules npm cache clear --force   After  npm install cross-env npm install  npm run watch   It s working fine on linux Fedora 25

User · Answer

Simply try running npm install   yarn etc first before running npm start   yarn start as  only4 mentioned  if you see this problem  as it means your  env is not in sync with your package json  i e  you installed a package but not quite configured it or other way around

User · Answer

This worked for me  on Windows 10     Add the following lines into your scripts in the package json file    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    watch    npm run development -- --watch    watch-poll    npm run watch -- --watch-poll    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    prod    npm run production    production    cross-env NODE ENV production node modules webpack bin webpack js --no-progress --hide-modules --config node modules laravel-mix setup webpack config js   Make your devDependencies looks something like this    devDependencies          axios     0 18        bootstrap     4 0 0        popper js     1 12        cross-env     5 1        jquery     3 2        laravel-mix     2 0        lodash     4 17 4        vue     2 5 7     Remove node modules folder Run npm install Run npm run dev

[node.js] Laravel 5.4 ‘cross-env’ Is Not Recognized as an Internal or External Command

Examples related to node.js

Examples related to laravel

Examples related to npm

Examples related to laravel-mix