{"id":29373,"date":"2021-02-25T20:25:48","date_gmt":"2021-02-26T04:25:48","guid":{"rendered":"https:\/\/careerkarma.com\/blog\/?p=29373"},"modified":"2021-03-29T04:20:42","modified_gmt":"2021-03-29T11:20:42","slug":"npm-command-not-found","status":"publish","type":"post","link":"https:\/\/careerkarma.com\/blog\/npm-command-not-found\/","title":{"rendered":"npm command not found"},"content":{"rendered":"\n

Npm<\/a> (node package manager) helps JavaScript developers focus on the code instead of other \u2014 sometimes tedious and repetitive \u2014 details. Sometimes, however, you may come across npm errors such as npm command not found<\/code>.
<\/p>\n\n\n\n

We will work through how to resolve this error, so you can go back to enjoying all that npm has to offer.<\/p>\n\n\n\n

What is the npm command not found Error?<\/h2>\n\n\n\n

The Npm command not found<\/code> error can appear when you install or upgrade npm.
<\/p>\n\n\n\n

On Windows, the cause of this error could be that a PATH or system variable is not correctly set. The error can also occur if you do not have npm or Node.js installed, have an outdated version, or have permission issues.
<\/p>\n\n\n\n

Mac users seeing the npm command not found error could be due to missing files on your computer or a permissions issue.
<\/p>\n\n\n\n

This article addresses those possible reasons. First we cover general causes related to installation, then go into Mac-specific solutions, before addressing how to fix a potential missing PATH variable on Windows.<\/p>\n\n\n\n

Check if npm is Installed<\/h2>\n\n\n\n

The npm command requires npm to be installed on Windows. Npm uses Node.js, so it comes included in your Node.js installation package. To check if you have NOde.js installed type the following in the terminal:
<\/p>\n\n\n\n

node -v<\/pre><\/div>\n\n\n\n
The -v<\/em> stands for \u201cversion\u201d. Visit the npm site<\/a> to verify if the version of npm you have installed is the latest version.
<\/p>\n\n\n\n
You may have accidentally deleted your npm file or moved its location. This can happen more often than you think, especially if you change your PATH on your system.
<\/p>\n\n\n\n
Check if npm is installed as well as node by typing the following in your terminal:
<\/p>\n\n\n\n
npm -v<\/pre><\/div>\n\n\n\n
If you do have npm installed, it will output the version on your computer. To install npm, run the commands here for Mac<\/a> and here if you are using Windows<\/a>.<\/p>\n\n\n\n
Update npm<\/h2>\n\n\n\n
Even though npm comes with Node.js, they are separate, meaning you can have the latest of one and not of the other, since they may have different update release dates.
<\/p>\n\n\n\n
If you have node (check with $node -v<\/em>) and your node commands work, you may need to simply update npm. Updating npm can be done with one line:
<\/p>\n\n\n\n
npm install npm@latest -g<\/pre><\/div>\n\n\n\n
If you have trouble with this command, you may have to prefix it with sudo<\/code>:
<\/p>\n\n\n\n
sudo npm install -g npm@latest<\/pre><\/div>\n\n\n\n
If you are working on your code in an editor, make sure to restart it after you\u2019re done installing or updating.<\/p>\n\n\n\n
Windows Solution<\/h2>\n\n\n\n
You may still see npm command not found<\/code> because C:\\Program Files\\nodejs could be missing from your PATH environment variable.
<\/p>\n\n\n\n
  1. Open global search \ud83d\udd0e and look up \u201cEnvironment Variables\u201d.<\/li>
  2. Choose \u201cEdit system environment variables\u201d.<\/li>
  3. Click \u201cEnvironment Variables\u201d in the \u201cAdvanced\u201d tab.<\/li>
  4. In the \u201cSystem Variables\u201d box, search for Path and edit it to include the path C:\\Program Files\\nodejs. If you don’t see it there click \u201cNew\u201d then add this path. (Note: Depending on your version you may just need to edit and append this path to what\u2019s there by prefixing it with a semicolon. You\u2019ll see the other paths there are also separated by semicolons).<\/li><\/ol>\n\n\n\n
    Here is some documentation<\/a> on the Windows settings and environment variables relating to npm in case you are curious and want to read more about the settings.<\/p>\n\n\n\n
    Permissions Solution<\/h2>\n\n\n\n
    For permission issues, prefix your terminal commands with sudo<\/code> to bypass issues. Permission issues can be the cause of program files not being able to be properly downloaded. You can also try the following terminal commands as a last option if all others have not worked out for you, though this may not be an option for you if you are on a shared or work computer. For Mac and Linux users:
    <\/p>\n\n\n\n
    sudo chown -R $(whoami):admin \/usr\/local\/lib\/node_modules\/<\/pre><\/div>\n\n\n\n
    This command adjusts the permissions of the npm directory<\/a>. Chown<\/code> means change owner, -R<\/code> means recursively (throughout the files therein), \u201cwhoami\u201d grabs your user account name, and the last line is where your node package files are. After running the above command,  try the npm command you were attempting again.<\/p>\n\n\n\n
    Conclusion<\/h2>\n\n\n\n
    After implementing any changes we went through to troubleshoot the \u201ccommand not found\u201d error, be sure to restart any open code editor or terminal\/command prompt. To recap, the suggested solutions we discussed were:
    <\/p>\n\n\n\n