Borislav Hadzhiev
Wed Mar 02 2022·3 min read
Photo by Christoph Peich
To solve the error "'concurrently' is not recognized as an internal or
external command, operable program or batch file", install the package globally
by running npm install -g concurrently
, restart your terminal and make sure
your PATH environment variable is set up correctly.
Open your terminal and install concurrently globally by running the following command.
# 👇️ install concurrently globally npm install -g concurrently # 👇️ or install concurrently locally to your package.json file npm install concurrently
The benefit of installing concurrently
locally to your project is that you can
track the version of the package in your package.json
file.
You could create a start
script in your package.json
file that looks
something like:
{ "scripts": { "start": "concurrently \"command1 arg\" \"command2 arg\"" } }
Notice that we have to escape quotes in the package.json
file.
concurrently
fails, you might have to open your shell as an administrator or run the command prefixed with sudo
.# 👇️ if you got permissions error sudo npm install -g concurrently
If that didn't help, run the following command:
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.
On Windows, the output of the npm config get prefix
command will look
something like: C:\Users\Your_User_Name\AppData\Roaming\npm
.
To update the PATH on a Windows machine, you have to:
env
and then click "Edit the system
environment variables"Path
variable and add the output you got from the
npm config get prefix
command.The path should look like C:\Users\Your_User_Name\AppData\Roaming\npm
(make
sure to replace the Your_User_name
placeholder with your actual username).
If you get the error "concurrently cannot be loaded because running scripts is disabled on this system", open your PowerShell as an administrator and set its execution policy with the Set-ExecutionPolicy command.
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser
Set-ExecutionPolicy
command.This effectively removes the execution policy of Restricted
, which doesn't
allow us to load configuration files or run scripts. The Restricted
execution
policy is the default for Windows client computers.
If you are on macOS
, you can update your path with the following command:
# make sure path matches with npm config get prefix export PATH=/usr/local/share/npm/bin:$PATH
If you are on Linux
, you can add the output from the npm config get prefix
command to your .bashrc
file.
# 👇️ make sure to update the path with the output # from the command export PATH="/usr/local/share/npm/bin:$PATH"
If that doesn't help try to reinstall Node.js on your
machine and then install concurrently
globally by running
npm install -g concurrently
.
# 👇️ install concurrently globally npm install -g concurrently
concurrently
fails, you might have to open your shell as an administrator or run the command prefixed with sudo
.# 👇️ if you got permissions error sudo npm install -g concurrently
Alternatively, you can see how you can fix the permissions error on this page in the official npm docs.