Answers for "cross-env' is not recognized as the name of a cmdlet"

2

'cross-env' is not recognized as an internal or external command,

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
Posted by: Guest on August-13-2020
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
Posted by: Guest on June-24-2020

Code answers related to "cross-env' is not recognized as the name of a cmdlet"

Browse Popular Code Answers by Language