I've kept it here for historical purposes, but it should no longer be used. It was only ever intended to fix a specific error message which has since been fixed. The reason for updating the path variable is because the npm cli suggests you update npm with npm install -g npm which will install npm at a different location than where Node installs npm originally.This entire guide is based on an old version of Homebrew/Node and no longer applies. Close and reopen the terminal shell and run npm -v to check that npm is correctly on the latest version.Save your changes and close the text editor. ~/.bash_profile) export PATH=$PATH:$HOME/.npm-global/bin If you don't use zsh, open the profile for your corresponding shell (i.e. Open up ~/.zshrc in a text editor and add the following line. If ~/.npm-global/bin does not show up between the colons, then update the path variable. Make sure to set the correct path variable.Sometimes this doesn't work, so I had to go into finder to delete the /npm/ folder. Remove the old version of npm installed by Node.Once installed, close and open a new terminal shell. Npm install -g command uses the old version of npm (installed by Node), to globally install the latest version of npm at ~/.npm-global/. Globally installed the desired version of npm.If npm is not installed, then install it on the Mac with Node.js. Make sure (the old version of) npm is installed.For me, a working solution was a simple, five-step process. In my case, none of the previous answers worked. I followed the directions found on this Q&A, completely removing npm and node from my system and reinstalling them from scratch, and it also fails to update.Ĭlose the terminal, and then re-open the terminal and running: $ npm -v

It displays no error, only 'updated 1 package'. For reasons unknown to me, I haven't been able to update to the latest version of npm on macOS (it works fine on Windows).

Node update mac