Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
Pick a username Email AddressPasswordBy clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
- Home
- Node.js
- Laravel 54 Cross Env Is Not Recognized As An Internal Or External Command
Laravel 5.4 ‘cross-env’ Is Not Recognized as an Internal or External Command
Tags: node.js , laravel , npm , laravel-mix Answers: 1 | Viewed 130,215 times
I'm trying to run npm run dev for Laravel Mix and I get this error:
> @ dev D:\projects\ptcs
> 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.
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.
* The answers/resolutions are collected from stackoverflow, are licensed under CC BY-SA 4.0
Some Code Answers
>
@ dev D:\projects\ptcs >
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.
rm -rf node_modules rm package-lock.json yarn.lock npm cache clear --force
npm install cross-env npm install
rm -rf node_modules npm cache clear --force
npm install cross-env npm install npm run watch
"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"
'cross-env' is not recognized as an internal or external command, operable program or batch file.
npm uninstall --save-dev cross-env npm install -g cross-env
{ "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" } }
"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"
"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" }
npm install &&
npm run dev
npm install --no-bin-links npm run dev
More Answers Related Laravel 54 Cross Env Is Not Recognized As An Internal Or External Command
Laravel 5.4 ‘cross-env’ Is Not Recognized as an Internal or …
2 days ago Jul 10, 2017 · 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.
› Reviews: 3
Show details
Laravel ‘cross-env’ Is Not Recognized as An Internal or External ...
1 week ago Jul 16, 2019 · We need to make cross-env working globally instead of having it in the project. Solution 1. Delete node_modules folder from your project. Run npm install --global cross-env this command. Delete "cross-env": "^5.0.1", from package.json file devDependencies section. Run npm install --no-bin-links; Now run npm run dev to what happens. Solution 2
Show details
› See also: Json File
Laravel 5.4 ‘cross-env’ Is Not Recognized as an Internal or External ...
1 day ago May 06, 2022 · 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. …
Show details
'cross-env' is not recognized as an internal or external command, …
1 week ago May 28, 2022 · ‘cross-env’ is not recognized as an internal or external command, laravel ... The solution for “‘cross-env’ is not recognized as an internal or external command, laravel” can be found here. The following code will assist you in solving the problem. Get the Code! npm install -global cross-env npm install –no-bin-links. Thank you ...
Show details
› See also: Laravel
Laravel 5.4 'cross-env' is not recognized as an internal or external ...
1 week ago Jul 11, 2017 · Home / laravel / laravel-mix / node.js / npm / Laravel 5.4 'cross-env' is not recognized as an internal or external command. Laravel 5.4 'cross-env' is not recognized as an internal or external command by. Rajitha on. July 11, 2017 in …
Show details
› See also: Node.js Laravel
Laravel 5.4 ‘cross-env’ Is Not Recognized as an Internal or External ...
4 days ago The best answers to the question “Laravel 5.4 ‘cross-env’ Is Not Recognized as an Internal or External Command” in the category Dev. QUESTION : I’m trying to run npm run dev for Laravel Mix and I get this error:
Show details
Laravel ‘cross-env’ Is Not Recognized as An Internal or External …
1 day ago Run in your terminal or command prompt the following command npm install –global cross-env. Delete “cross-env”: “^5.0.1”, from package.json file devDependencies section. After deletion run npm install –no-bin-links. In the end run npm run dev to see what happens.
Show details
› See also: Json File
'Laravel 5.4 ‘cross-env’ Is Not Recognized as an Internal or External ...
1 week ago 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
Show details
› See also: Json
'cross-env' is not recognized as an internal or external command, …
1 day ago Sep 15, 2021 · npm install -global cross-env npm install --no-bin-links. Add Own solution. Log in, to leave a comment.
Show details
laravel 5.4 ‘cross-env’ is not recognized as an internal or external ...
2 days ago npm install -global cross-env npm install --no-bin-links laravel 5.4 ‘cross-env’ is not recognized as an internal or external command ask question. Home; Programming Languages . Abap; ... Answers for "laravel 5.4 ‘cross-env’ is not recognized as an …
Show details
› See also: Laravel
cross-env' is not recognized as an internal or external command …
1 week ago Example 2: npm 'cross-env' is not recognized as an internal or external command. 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.
Show details
› See also: Json
"laravel 'cross-env' is not recognized as an internal or external ...
1 day ago 'cross-env' is not recognized as an internal or external command, laravel. ... Source. 1. npm 'cross-env' is not recognized as an internal or external command. 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 ...
Show details
› See also: Json Laravel
"laravel 'cross-env' is not recognized as an internal or external ...
1 week ago 'cross-env' is not recognized as an internal or external command, laravel npm install -global cross-env npm install --no-bin-links Posted by: Guest User on Mar 15 2020
Show details
› See also: Laravel
'cross-env' is not recognized as an internal or external command …
6 days ago Answers for "'cross-env' is not recognized as an internal or external command laravel"
Show details
› See also: Laravel
Cross env is not recognized as an internal or external …
5 days ago Tìm kiếm các công việc liên quan đến Cross env is not recognized as an internal or external command hoặc thuê người trên thị trường việc làm freelance lớn nhất thế giới với hơn 21 triệu công việc. Miễn phí khi đăng ký và chào giá cho công việc.
Show details