cross-env: command not found error [Solved]

avatar

Borislav Hadzhiev

Last updated: Mar 11, 2022

banner

Photo from Unsplash

cross-env: command not found error [Solved] #

Use npx to solve the error "cross-env: command not found", e.g. npx cross-env NODE_ENV=production webpack --config build/webpack.config.js or install the package globally by running npm install -g cross-env to be able to use the command without the npx prefix.

command not found cross env

The fastest way to solve the error is to use the npx command.

shell
# 👇️ prefix with npx npx cross-env NODE_ENV=production webpack --config build/webpack.config.js

Alternatively, you can install cross-env globally or as a development dependency.

shell
# 👇️ installs cross-env globally (can run from any directory) npm install -g cross-env # 👇️ (better) installs cross-env locally to the project (must be ran from root directory) npm install --save-dev cross-env

The benefit of installing cross-env as a development dependency is that you can control the version of the package in your package.json file.

You can also create commands in the scripts object of your package.json file.

package.json
{ "scripts": { "build": "cross-env NODE_ENV=production webpack --config build/webpack.config.js" } }

This works because npm will resolve cross-env from your node_modules directory because you ran npm install --save-dev cross-env.

Now you would run the command as npm run build, and not use cross-env directly.

If you decide to install cross-env globally and the installation fails, you might have to run the command prefixed with sudo.
shell
# 👇️ if you get permissions error sudo npm install -g cross-env

You can link your project to the globally installed cross-env package, by opening your terminal in your project's root directory (where your package.json file is) and running the npm link cross-env command.

shell
npm link cross-env

The npm link command creates a symbolic link from the globally installed package to the node_modules/ directory of the current folder.

If the "cross-env: command not found" error is not resolved, try restarting your terminal.

If that doesn't help, run the following command:

shell
npm config get prefix

The command will show you the path where npm puts your globally installed packages. The global packages will be in the bin directory at the specified path.

Look at the PATH environment variable on your operating system and add the path that the npm config get prefix command outputs if it's not already there.

If you add the output from the command to your PATH environment variable, you have to restart any open command prompts before it takes effect.

If that didn't work, try to add the path to the bin folder (from npm config get prefix) to your PATH environment variable and restart your terminal.

For example, on macOS, you can update your path with the following command:

shell
# make sure path matches with npm config get prefix export PATH=/usr/local/share/npm/bin:$PATH

And on Windows, the output of the npm config get prefix command will look something like: C:\Users\Your_User_Name\AppData\Roaming\npm.

Edit the environment variable on your machine and add the specified path (replacing the placeholder with your username).

If you are on Linux, you can add the output from the npm config get prefix command to your .bashrc file.

~/.bashrc
# 👇️ make sure to update the path with the output # from the command export PATH="/usr/local/share/npm/bin:$PATH"
If you add the output from the command to your PATH environment variable, you have to restart any open command prompts before it takes effect.

If that doesn't help try to reinstall Node.js on your machine and then install cross-env globally by running npm install -g cross-env@latest.

During the installation, you might get a prompt for whether you want to automatically update the PATH environment variable on your system, make sure to tick the option.
shell
# 👇️ installs cross-env globally (can run from any directory) npm install -g cross-env
If the global installation of cross-env fails, you might have to run the command prefixed with sudo.
shell
# 👇️ if you get permissions error sudo npm install -g cross-env

Alternatively, you can see how you can fix the permissions error on this page in the official npm docs.

Conclusion #

Use npx to solve the error "cross-env: command not found", e.g. npx cross-env NODE_ENV=production webpack --config build/webpack.config.js or install the package globally by running npm install -g cross-env to be able to use the command without the npx prefix.

I wrote a book in which I share everything I know about how to become a better, more efficient programmer.
book cover
You can use the search field on my Home Page to filter through all of my articles.