'nodemon' is not recognized as an internal or external command

avatar

Borislav Hadzhiev

6 min

banner

Photo from Unsplash

Table of Contents #

  1. 'nodemon' is not recognized as an internal or external command
  2. nodemon: command not found error

'nodemon' is not recognized as an internal or external command #

Use npx to solve the error "'nodemon' is not recognized as an internal or external command, operable program or batch file", e.g. npx nodemon server.js or install the package globally by running npm install -g nodemon and make sure your PATH environment variable is set up correctly.

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

shell
npx nodemon@latest server.js npx nodemon@latest --version

Alternatively, you can install nodemon globally or as a development dependency.

shell
# ๐Ÿ‘‡๏ธ installs nodemon globally (can run from any directory) npm install -g nodemon # ๐Ÿ‘‡๏ธ (better) installs nodemon locally to the project (must be run from root directory) npm install --save-dev nodemon
The benefit of installing nodemon as a development dependency is that you can control the version of the package in your package.json file.

You can create a command in the scripts object of your package.json file.

package.json
{ "scripts": { "dev": "nodemon server.js" } }

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

Now you would run the command as npm run dev, and not use nodemon directly.

If you decide to install nodemon globally and the installation fails, you have to open your shell as an administrator and rerun the commands.
shell
npm install -g nodemon nodemon --version

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

shell
npm link nodemon

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

If the "nodemon is not recognized as an internal or external command" error is not resolved, try restarting your terminal.

Update your PATH environment variable on Windows #

If that didn'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.

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:

  1. Open the start search and type in env and then click "Edit the system environment variables"
  2. Then click "Environment Variables"
  3. Edit the 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 add the output from the command to your PATH environment variable, you have to restart any open command prompts before it takes effect.

If you get the error "nodemon 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.

shell
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser
Make sure to open your PowerShell as an administrator before you run the 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 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 nodemon globally by running npm install -g nodemon@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 nodemon globally (can run from any directory) npm install -g nodemon nodemon --version
If the global installation of nodemon fails, you have to open your shell as an administrator and rerun the commands.

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

nodemon: command not found error #

Use npx to solve the error "nodemon: command not found", e.g. npx nodemon server.js or install the package globally by running npm install -g nodemon to be able to use the command without the npx prefix.

command not found nodemon

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

shell
npx nodemon@latest server.js npx nodemon@latest --version

Alternatively, you can install nodemon globally or as a development dependency.

shell
# ๐Ÿ‘‡๏ธ installs nodemon globally (can run from any directory) npm install -g nodemon # ๐Ÿ‘‡๏ธ (better) installs nodemon locally to the project (must be run from root directory) npm install --save-dev nodemon

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

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

package.json
{ "scripts": { "dev": "nodemon server.js" } }

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

Now you would run the command as npm run dev, and not use nodemon directly.

If you decide to install nodemon 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 nodemon nodemon --version

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

shell
npm link nodemon

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

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

Update your PATH on macOS or Linux #

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

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 nodemon globally by running npm install -g nodemon@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 nodemon globally (can run from any directory) npm install -g nodemon
If the global installation of nodemon fails, you might have to run the command prefixed with sudo.
shell
# ๐Ÿ‘‡๏ธ if you get permissions error sudo npm install -g nodemon nodemon --version

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

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.

Copyright ยฉ 2023 Borislav Hadzhiev