How can I change the version of npm using nvm?

Question

I've been using NVM to install the latest versions of Node.js for my Node.js work. It works totally fine for installing separate versions and switching between them. It also installs the latest version of NPM within each local .../bin folder along with the Node.js binary. However, there doesn't seem to be a way to switch the version of NPM that I'm using (or at least I can't figure it out).

The only solution I can think of myself is to delete the binary that it's defaulting to (which is the NPM that was installed when I first installed node with NVM), and in its place to put the latest NPM binary. However, is there a better way to go about doing this?

Why do you wanna change the version of NPM, it's not like you gonna install any package that only works with an old version of NPM. And after node 0.6, node comes with the latest NPM. So changing node version will also change npm version. — Farid Nouri Neshat, Mar 18 '12 at 04:35
except it doesn't through NVM. yes - node comes with NPM, but that just means that it installs a binary alongside it. i can see both binaries in their respective folders, but when i run "nvm use v0.6.13", the npm binary in use remains the one that was installed with the older version of node, instead of the one installed with the newest version. — thisissami, Mar 19 '12 at 15:35
Here's the code for npm: https://github.com/creationix/nvm/blob/master/nvm.sh#L135-148 , which is not needed since, 0.6, so maybe you should try to remove that part. That should help. You can also create an issue on github. — Farid Nouri Neshat, Mar 20 '12 at 02:35
I am working on this problem right now, any help appreciated - https://stackoverflow.com/questions/50976138/tool-to-change-npm-version-for-testing-by-symlinking-different-versions-to-glo — Alexander Mills, Jun 21 '18 at 19:25
Do not confuse it with `nvm-windows` (!!!) which is `nvm` as well in command line!!! Check this instead: https://stackoverflow.com/questions/54652381/updating-npm-when-using-nvm-windows — Ruslan Zhomir, Jul 29 '22 at 16:16

score 556 · Accepted Answer · edited Aug 09 '22 at 19:40

556

As noted in another answer, there is now a command for this:

nvm now has a command to update npm. It's nvm install-latest-npm or nvm install --latest-npm.

nvm install-latest-npm: Attempt to upgrade to the latest working npm on the current Node.js version.

nvm install --latest-npm: After installing, attempt to upgrade to the latest working npm on the given Node.js version.

Below are previous revisions of the correct answer to this question.

For later versions of npm it is much simpler now. Just update the version that nvm installed, which lives in ~/.nvm/versions/node/[your-version]/lib/node_modules/npm.

I installed Node.js 4.2.2, which comes with npm 2.14.7, but I want to use npm 3. So I did:

cd ~/.nvm/versions/node/v4.2.2/lib
npm install npm

Easy!

And yes, this should work for any module, not just npm, that you want to be "global" for a specific version of node.

In a newer version, npm -g is smart and installs modules into the path above instead of the system global path.

edited Aug 09 '22 at 19:40

Peter Mortensen

30,738
21
105
131

answered Nov 06 '15 at 20:46

Lawrence

10,142
5
39
51

21

and for those who don't know where their nvm is, like me, run a `which npm`. – Larry Jan 27 '16 at 15:33
48

And if you want a version of npm other than the latest, run `npm install npm@major.minor.patch` to get that specific version, e.g. `npm@3.10.9` – Michael Nov 21 '16 at 18:15
3

Something similar works for [nvm-windows](https://github.com/coreybutler/nvm-windows/) too, e.g. `cd ~/AppData/Roaming/nvm/v5.10.1`. – absynce Feb 24 '17 at 20:17
For those wanting a use case, I was tasked with getting a legacy project running which needed Node 5 and NPM 2, the latter being required because of the change in how [peerDependencies](https://docs.npmjs.com/files/package.json#peerdependencies) are handled. NPM versions 1 and 2 will automatically install peerDependencies if they are not explicitly depended upon higher in the dependency tree, whereas this is no longer the case. The legacy app build process relied on this older behavior. – spex Mar 17 '17 at 19:13
4

For anyone using nvm for Windows, the same can be done as above (running npm install npm), but in the node install locations for Windows. In Windows 10, this is ~/AppData/Roaming/nvm/[your-version]. i.e Users\myusername\AppData\Roaming\nvm\v9.7.1 – Sean Holmesby Mar 28 '18 at 16:31
!! Is there a way to switch npm versions with nvm without installing a new/different npm version each time you want to switch? – Alexander Mills Jun 21 '18 at 02:50
I am working on this problem right now, any help appreciated - https://stackoverflow.com/questions/50976138/tool-to-change-npm-version-for-testing-by-symlinking-different-versions-to-glo – Alexander Mills Jun 21 '18 at 19:25
3

Even easier: `nvm install-latest-npm` as answered below by samlandfried -https://stackoverflow.com/a/47519162/5991278 – philraj Aug 17 '18 at 19:07
2

This isn't a comprehensive answer to the question even though there are good comments. The question asks about changing npm while the answer only deals with upgrading npm. I have a legacy project that needs an old version of node which I can get using nvm but the associated version of npm is too new. Unfortunately Michael's upvoted comment doesn't work for me and it looks like work is needed on the existing files/symlinks. However, I had success with Ryan Shillington's answer by replacing latest with 5.6.0. – Astrophe Oct 16 '20 at 08:50
Make sure to update nvm to the latest version before running `nvm install-latest-npm`. I had an old version of nvm and the option install-latest-npm did not exist. After updating, the option was available. – mrbinky3000 Jan 03 '22 at 21:57
2

This doesn't work for `nvm-windows`, check this - https://stackoverflow.com/questions/54652381/updating-npm-when-using-nvm-windows – kaushalpranav Jan 07 '22 at 12:16
This didn't change due to the passage of time alone. Can you add version information to the answer? What version did it change in? (But ***without*** "Edit:", "Update:", or similar - the answer should appear as if it was written today.) – Peter Mortensen Aug 07 '22 at 03:05
1

"Newest" and "now" get dated very quickly. This answer shouldn't read as a revision history. It should be written ***as if it was written today***. Either provide the exact version ranges (along with release dates) for which certain parts are valid. For example, with sub sections headings *"Version 4.35.2 (2020-09-18) or later"*, *"Version 2.10.9 - 4.35.1 (2015-01-29 - 2020-09-18)"*, and *"Version 2.10.8 (2015-07-02) or earlier"* . Or only provide it for some new version if older versions are not that interesting. – Peter Mortensen Aug 09 '22 at 19:44
Does this work for anybody now with nvm 1.1.10 on windows? When I run `nvm install-latest-npm` it just gives me the same as `nvm help`. When I run `nvm install --latest-npm` it errors. – Rory Nov 12 '22 at 21:17
I cannot get this to work with nvm 1.1.10 or 1.1.11 – Axel Kennedal Jun 26 '23 at 09:39

score 172 · Answer 2 · edited Aug 09 '22 at 19:56

172

Use

npm install npm@x.x.x -g
npm install npm@5.4.0 -g

edited Aug 09 '22 at 19:56

Peter Mortensen

30,738
21
105
131

answered Sep 05 '17 at 20:53

Ocko

1,851
1
9
4

27

Though the question is about nvm, I actually came here for that, thanks. Upvoting. – Mouloud85 May 16 '18 at 12:06
3

This command will work regardless of which version of Node you've installed with nvm, because of the `-g` flag. When you switch versions in nvm, the npm version will change as well, so it's easy to undo this action. – A.Wan Nov 24 '21 at 00:26
4

An explanation would be in order. E.g., what is the idea/gist? What is it supposed to do? Is "x.x.x" literal or not? Is it installing two versions side by side (at the same time)? From [the Help Center](https://stackoverflow.com/help/promotion): *"...always explain why the solution you're presenting is appropriate and how it works"*. Please respond by [editing (changing) your answer](https://stackoverflow.com/posts/46063210/edit), not here in comments (***without*** "Edit:", "Update:", or similar - the answer should appear as if it was written today). – Peter Mortensen Aug 09 '22 at 19:57

score 56 · Answer 3 · edited Aug 09 '22 at 20:05

56

nvm doesn't handle npm.

So if you want to install Node.js 0.4.x (which many packages still depend on) and use NPM, you can still use npm 1.0.x.

Install Node.js 0.6.x (which comes with npm 1.1.x) and install nvm with npm:

npm install nvm
. ~/nvm/nvm.sh

Install Node.js 0.4.x with nvm:

nvm install v0.4.12
nvm use v0.4.12

Install npm using install.sh (note the -L parameter to follow any redirects):

curl -L https://npmjs.org/install.sh | sh

This will detect Node.js 0.4.12 and install npm 1.0.106 in your ~/nvm/v0.4.12/lib/node_modules folder and create a symbolic link for nvm:

~/nvm/v0.4.12/bin/npm -> ../lib/node_modules/npm/bin/npm-cli.js

If you try to run npm, it will still give an error, but if you do nvm use v0.4.12 again, it should now work.

edited Aug 09 '22 at 20:05

Peter Mortensen

30,738
21
105
131

answered Apr 10 '12 at 18:40

fijiaaron

5,015
3
35
28

3

Thanks! A note that the url has changed to: `curl https://npmjs.org/install.sh | sh` – tristen Sep 24 '12 at 14:50
16

Is this a really old answer now? My npm is downloaded by nvm automatically as a dependency of the node version I'm using. – Damon Smith Jan 27 '15 at 00:49
3

Yeah. It's old. If you're still using node 0.4 and an old nvm you might see this issue. – fijiaaron Jan 28 '15 at 22:51
1

The URL has been changed again to force www. Use `curl -L` to follow the redirect. – Neal Ehardt Oct 07 '15 at 20:27

samlandfried · Answer 4 · 2018-03-09T16:55:51.563

48

nvm now has a command to update npm. It's nvm install-latest-npm or npm install --latest-npm.

edited Mar 09 '18 at 16:55

answered Nov 27 '17 at 20:19

samlandfried

801
9
11

6

Do you have a link to the documentation for this? – allicarn Jan 30 '18 at 16:38
2

From `nvm help` console output: `--latest-npm After installing, attempt to upgrade to the latest working npm on the given node version` I didn't find a reference to this in the `nvm` docs, though. Please share if you find it. – samlandfried Mar 09 '18 at 16:47
Thank you! This really should be marked as the correct answer. – philraj Aug 17 '18 at 19:05
2

its only available on 32 bits – Negin Basiri Aug 12 '19 at 01:17
1

when i ran this, it updated node as well – Kip Oct 07 '21 at 14:13
2

Is it possible to save the npm version into an .nvmrc-like file? – derpedy-doo Oct 13 '21 at 21:12
1

Maybe obvious, but this works until the latest includes a breaking change, e.g., upgrading npm v6 (from node 14) to v8.1.0 when you really wanted v7 – Ed Norris Oct 18 '21 at 19:08

score 48 · Answer 5 · edited Aug 09 '22 at 20:08

48

I'm on Windows and I couldn't get any of this stuff to work. I kept getting errors about files being in the way. This worked though:

cd %APPDATA%\nvm\v8.10.0           # or whatever version you're using
mv npm npm-old
mv npm.cmd npm-old.cmd
cd node_modules\
mv npm npm-old
cd npm-old\bin
node npm-cli.js i -g npm@latest

cd %APPDATA%\nvm\v8.10.0 # or whatever version you're using
rm npm-old
rm npm-old.cmd
cd node_modules\
rm -rf npm-old

And boom, I'm back in business.

edited Aug 09 '22 at 20:08

Peter Mortensen

30,738
21
105
131

answered Jun 20 '18 at 19:00

Ryan Shillington

23,006
14
93
108

3

Thanks, this worked for me as well, on Windows. (had same issue of file conflicts) – Venryx Jul 20 '18 at 04:53
1

Worked for me thx. Am using nvm on Windows to manage node and wanted to uplift nvm after switching to node version. Had to run console with elevated permissions. My path nodejs folder is "C:\Program Files\nodejs" which is an alias for a.n.other location on my machine nvm uses to cache downloads (not APPDATA), guess I elected a different location when installing nvm. – Moika Turns Mar 12 '19 at 13:11
2

Thank you, they probably need to fix the way npm update on every old nodejs version on nvm windows. – rbinsztock May 02 '19 at 08:36
1

That helped me to update npm which came with Node 10.x. Thank you! – andypotato Sep 10 '19 at 12:01
2

Worked on windows with nodejs v10.15.3, had to change `mv` to `ren` and `rm` to `del` and `rmdir` for me. – deerchao Sep 19 '19 at 04:35
2

I found that when upgrading from npm@6, I also had to rename `npx` and `npx.cmd`. Not sure what version introduced npx. – Ken Lyon Feb 19 '21 at 23:17
With v5.11.0 I get this error: module.js:341 throw err; ^ ''' Error: Cannot find module 'process-nextick-args' at Function.Module._resolveFilename (module.js:339:15) at Function.Module._load (module.js:290:25) at Module.require (module.js:367:17) ... at Module.load (module.js:357:32) at Function.Module._load (module.js:314:12) at Module.require (module.js:367:17) ''' – Fantantonio Oct 09 '21 at 09:12
1

Doesn't work for me with node 14.18.0: I get errors like `npm ERR! Error: EPERM: operation not permitted, rename 'C:\Users\roryk\AppData\Roaming\nvm\v14.18.0\node_modules\npm\node_modules\.node-gyp.DELETE\node_modules\@npmcli' -> 'C:\Users\roryk\AppData\Roaming\nvm\v14.18.0\node_modules\npm\node_modules\node-gyp\node_modules\@npmcli'` – Rory Nov 12 '22 at 21:25

score 37 · Answer 6 · edited Aug 09 '22 at 20:28

37

In Windows, run your terminal as system administrator (in case there are permission issues as I had). Then use a specific Node.js version (say 7.8.0) by

nvm use 7.8.0

Then update your npm to desired the specific version by:

npm install -g npm@5.0.3

edited Aug 09 '22 at 20:28

Peter Mortensen

30,738
21
105
131

answered Jan 12 '18 at 06:01

adnan2nd

2,083
20
16

Yes, I ended up just doing this on Windows. nvm-windows doesn't seem to have install-latest-npm command, and this seemed to do the trick just fine. – Hemaolle Aug 01 '23 at 10:53

score 20 · Answer 7 · edited Aug 09 '22 at 19:52

20

Changing npm versions on Linux-based OSes isn't a straightforward one-command process yet. I have done the following to switch back to older versions of npm. This should work to get any version of npm working.

First install the version of npm you want to use:

sudo npm install -g npm@X.X.X

Remove the symbolic link in /usr/local/bin/:

sudo rm /usr/local/bin/npm

Recreate the symbolic link using the desired version of npm you have installed:

sudo ln -s /usr/bin/npm@X.X.X /usr/local/bin/npm

edited Aug 09 '22 at 19:52

Peter Mortensen

30,738
21
105
131

answered Nov 13 '15 at 01:58

Arun Reddy

3,443
1
21
16

1

followed these instructions trying to go from 2.14.7 to 2.15.9, and now when I type npm -v, I get 3.8.6. Dammit. – Kyle Baker Nov 18 '16 at 16:52
3

After trying several things, for me, just using `sudo npm install -g npm@x.x.x` gets me that version responding from `npm -v`. This at least worked going from 4.x to 2.15.9, anyways. – Kyle Baker Nov 18 '16 at 17:43
1

In my case `sudo npm install -g npm@4.6.1` only installed 4.6.1 but npm 5.1.0 was still used. Your tip help me switch to 4.6.1. – Hung Tran Jul 11 '17 at 04:11

score 13 · Answer 8 · edited Aug 09 '22 at 20:52

You can install two versions of Node.js using nvm, and install different version of npm on each Node.js environment.

For example, nvm install 14.18.0 and nvm install 14.18.1 will install two separate Node.js environments.

In 14.18.0, you can use npm v6 (installed by default).
In 14.18.1, you can use npm v7 (install with npm install -g npm@7).

This way, you can switch to different npm versions without pain.

nvm use 14.18.0

    Now using node v14.18.0 (npm v6.14.15)

nvm use 14.18.1

    Now using node v14.18.1 (npm v7.24.2)

score 11 · Answer 9 · edited Aug 09 '22 at 20:21

11

Find the Node.js and npm version you want to use from here Previous Releases
nvm use 8.11.4
You already got the npm 5.6 with Node.js 8.11.4

Just go with nvm use node_version.

edited Aug 09 '22 at 20:21

Peter Mortensen

30,738
21
105
131

answered Aug 07 '19 at 04:47

Alvin Smith

547
5
9

1

That works fine for the first time. If you upgrade run `npm i -g npm` from an older node version and it updates to latest, your npm version will be the latest. – BonisTech Jan 13 '22 at 14:16

score 8 · Answer 10 · edited Aug 09 '22 at 19:54

8

By looking at www.npmjs.com/install.sh I found there is a way to install a specific version by setting an environment variable.

export npm_install="2.14.14"

Then run the download-script as described at npmjs.com:

curl -L https://www.npmjs.com/install.sh | sh

If you omit setting the npm_install variable, then it will install the version they have marked as latest.

edited Aug 09 '22 at 19:54

Peter Mortensen

30,738
21
105
131

answered Dec 07 '15 at 10:54

jim

101
1
5

2

I had to use `curl -L https://www.npmjs.com/install.sh | sudo sh`, aaaaand this method did not work, getting me the latest version even though I had exported said environment variable. God dammit. I wanted version 2.15.9 from 2.14.7, answer below put me at 3.8.6, and now this answer puts me at 4.0.2. WTF. – Kyle Baker Nov 18 '16 at 17:11

score 8 · Answer 11 · edited Aug 09 '22 at 20:46

8

We can easily solve this using n.

To install n:

npm install -g n

To switch versions:

n latest

To switch to a particular version:

n 10.16.0

edited Aug 09 '22 at 20:46

Peter Mortensen

30,738
21
105
131

answered Aug 11 '21 at 15:39

Deepak Chandh

257
3
9

`npm` and `n` both manages `nodejs` versions not `npm` versions. – ishandutta2007 Aug 26 '23 at 07:16

score 3 · Answer 12 · edited Aug 09 '22 at 19:58

3

Use npm i -g npm. Try to run this as well.

edited Aug 09 '22 at 19:58

Peter Mortensen

30,738
21
105
131

answered Oct 30 '17 at 16:32

Dimitri Reifschneider

457
4
5

This is always the quickest and easiest I normally use. – CTS_AE Jan 17 '19 at 00:25

score 3 · Answer 13 · edited Aug 09 '22 at 20:11

3

I had the same issue after installing nvm-windows on top of an existing Node.js installation. The solution was just to follow the instructions:

You should also delete the existing npm install location (e.g. "C:\Users\AppData\Roaming\npm") so that the nvm install location will be correctly used instead.

Installation & Upgrades

edited Aug 09 '22 at 20:11

Peter Mortensen

30,738
21
105
131

answered Dec 18 '18 at 19:58

WelcomeTo

19,843
53
170
286

score 3 · Answer 14 · edited Aug 09 '22 at 20:23

3

The easy way to change version is first to check your available version using

nvm ls

Then select a version from the list

nvm use version

edited Aug 09 '22 at 20:23

Peter Mortensen

30,738
21
105
131

answered Nov 11 '20 at 08:20

Syed Haseeb

212
2
9

score 2 · Answer 15 · edited Aug 09 '22 at 20:37

2

A slight variation on the previous instructions. It worked for me (macOS v10.12.6 (Sierra)).

npm install -g npm@3.10.10
rm /usr/local/bin/npm
ln -s ~/.npm-packages/bin/npm /usr/local/bin/npm
npm --version

edited Aug 09 '22 at 20:37

Peter Mortensen

30,738
21
105
131

answered Dec 28 '17 at 05:16

Nick Grealy

24,216
9
104
119

score 2 · Answer 16 · edited Aug 09 '22 at 20:50

In my case I updated npm from version 6 to 8 in a Node.js environment set to version 10 by nvm. This resulted in npm not working any more, rendering the answers I found here useless.

I finally resorted to clearing the nvm folder:

rm -rf ~/.nvm/versions/node/*

Afterwards I could work with nvm and npm again. My lesson: Never install a fresh npm version with npm. nvm install-latest-npm seems to let you safely update within legacy environments.

score 1 · Answer 17 · answered Dec 23 '22 at 23:26

To resolve:

I installed the latest version of node using nvm for Windows, which also installed the latest version of npm.
I deleted the npm directory from the node_modules folder and replaced it with the new version from the latest node install.

This allowed me to use the latest version of npm with a previous version of node, and resolved the issue I was having.

score 0 · Answer 18 · edited Aug 09 '22 at 20:28

0

For some reason, npm install -g npm@X.X.X didn't work, so I've changed the version of npm in file package.json in the npm folder:

which npm

/opt/homebrew/bin/npm

And then run

npm install npm

Platform: macOS v11.2.2 (Big Sur) with M1 (arm64).

edited Aug 09 '22 at 20:28

Peter Mortensen

30,738
21
105
131

answered Mar 19 '21 at 19:48

Andrey Gritsay

979
1
10
18

score 0 · Answer 19 · edited Oct 09 '22 at 01:57

0

In order to change your npm version when using nvm, you must install your npm version only inside the folder of the desired Node.js version. For instance, if you want to install npm version 8.12.1, you must do it inside the node version folder.

If you do it globally, it will not work.

edited Oct 09 '22 at 01:57

Peter Mortensen

30,738
21
105
131

answered Aug 23 '22 at 11:07

João Saraiva

1

2

Your answer could be improved with additional supporting information. Please [edit] to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers [in the help center](/help/how-to-answer). – Prathamesh More Aug 27 '22 at 10:41

score 0 · Answer 20 · answered Feb 16 '23 at 22:04

If you need it temporarily, you can use npm bundled with nvm-downloaded node version directly.

For example, this shows where is the current node executable and then runs npm install:

$ whereis node
node: ~/.nvm/versions/node/v18.12.1/bin/node
$ ~/.nvm/versions/node/v18.12.1/bin/npm -v
8.19.2
$ ~/.nvm/versions/node/v18.12.1/bin/npm install
...

score -1 · Answer 21 · edited Aug 09 '22 at 20:15

NVM installation and usage on Windows

Below are the steps for NVM installation on Windows:

NVM stands for Node Version Manager, which will help to switch your Node.js versions for specific use. It also allows the user to work with multiple npm and Node.js versions.

Install nvm setup.
Use command "nvm list" to check the list of installed Node.js versions.
Type "nvm use version number[6.9.3]" to switch versions.
For more information.

How can I change the version of npm using nvm?

21 Answers21

Linked