question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Command cross-env not found on Windows

See original GitHub issue

I’ve got this issue when running this command npm run dev.

npm ERR! Windows_NT 6.3.9600
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "dev"
npm ERR! node v6.9.1
npm ERR! npm  v3.10.8
npm ERR! code ELIFECYCLE
npm ERR! project@1.0.0 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 project@1.0.0 dev script 'cross-env NODE_ENV=development webpack --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 project 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 webpack --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 project
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls project
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     d:\Dev\Servers\wamp\www\project.dev\npm-debug.log

Note:

  • I’m using Windows 8.1
  • I’ve installed the node dependencies with yarn.

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Reactions:2
  • Comments:8 (3 by maintainers)

github_iconTop GitHub Comments

78reactions
TeroBlaZecommented, Jan 22, 2017

Install it globally That’s like I did with npm npm i -g cross-env the same for webpack@^2.2.0 and webpack-dev-server@^2.2.0

9reactions
sumitmanoharcommented, Sep 6, 2018

Install it globally That’s like I did with npm npm i -g cross-env the same for webpack@^2.2.0 and webpack-dev-server@^2.2.0

Read more comments on GitHub >

github_iconTop Results From Across the Web

'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 ...
Read more >
Command cross-env not found on Windows #131 - GitHub
I've got this issue when running this command npm run dev. npm ERR! Windows_NT 6.3.9600 npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" ...
Read more >
'cross-env' is not recognized as an internal or external command
To solve the error "cross-env is not recognized as an internal or external command, operable program or batch file", open your terminal in...
Read more >
How to resolve npm command not found: cross-env error
Open the terminal in your project directory, then use npm install command to install the package like this: · If that doesn't work,...
Read more >
'cross-env' is not recognized as an internal or ... - Laracasts
'cross-env' is not recognized as an internal or external command,. I'm building a Laravel 8 project using Vue2. The initial problem was that...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found