How can I update npm on Windows?

Question

I tried this:

sudo npm cache clean -f
sudo npm install -g n
sudo n stable

...but it didn't work.

How do I do this on Windows?

Dicrotic

The usual procedure for updating software that doesn't have built-in autoupdaters is to download and install the latest version. Have you tried that? – Tear

@Juhana I was thinking maybe there was some way to do it via npm as mentioned in that link. – Dicrotic

You can do it with Chocolatey. See my answer here for more info: https://mcmap.net/q/45702/-how-do-i-update-node-js – Chirurgeon

So how are you using sudo on windows? superuser.com/questions/42537/… – Avernus

sudo does not work on Windows... – Evergreen

@rcdmk How can you mark this as a possible duplicate of a question that was asked a month later? – Ballplayer

@Barry The other question had better answers at that time. – Seddon

Tagging off topic. I don't see any programming related issue on this question – Nucleoplasm

@Nucleoplasm Please refer to the help topics before flagging things as off-topic. Note that questions about software tools commonly used by programmers are on-topic. – Metempirics

I uninstalled, dowloaded the latest msi and reinstalled. I couldn't get other suggestions to work. Hope this helps someone. – Ceporah

Answer 1

Note: The question is specifically asking how to upgrade npm, not Node.js. If you want to update Node.js over a CLI on windows, I recommend running winget upgrade -q NodeJS or use chocolatey for that.

What method should I choose to update NPM?

• Node.js v16 or higher?
  • npm install -g npm
• Node.js v14 or below?
  • Consider updating to latest LTS release of Node.js
  • npm-windows-upgrade

Upgrade with npm-windows-upgrade

Run PowerShell as Administrator

Set-ExecutionPolicy Unrestricted -Scope CurrentUser -Force
npm install -g npm-windows-upgrade
npm-windows-upgrade

Note: if you run the Node.js installer, it will replace the Node.js version.

• Upgrades npm in-place, where Node.js installed it.
• Does not modify the default path.
• Does not change the default global package location.
• Allows easy upgrades and downgrades and to install a specific version.
• A list of versions matched between NPM and Node.js (https://nodejs.org/en/download/releases/) - but you will need to download the Node.js installer and run that to update Node.js (https://nodejs.org/en/)

Upgrade with npm

npm install -g npm

Note: some users still report issues updating npm with npm, but I haven't had that experience with v16+.

Foreknowledge

Was having issues getting mine to upgrade, this script worked perfectly. Thanks. – Abarca

Microsoft recommends using this in their nodejs-guidlines repo on github. It also suggests tools for managing node versions. – Radioactive

This worked great for npm. thought I would mention, as the question itself is for updating node and npm, that to get both updated I had to uninstall / reinstall node, and run this upgrader as well (not sure if the node installer would have done it by itself as I did the upgrader first) – Heinrik

@Heinrik The node installer does not run this tool. Node picks a version of NPM to package in their installer. It's generally a few minor versions back than the latest. Node 5.6 bundles NPM 3.6, the latest is 3.8 right now. You most likely had to uninstall due to either a bug that was present (now fixed) or you manually updated npm at some point and most likely missed a critical step. You should not need to uninstall node/npm going forward. If you do, then I would wipe out the entire programfiles/node directory and %appdata%\npm after you uninstall. That should fix the problem permanently. – Foreknowledge

Should this be expected to work through a corporate proxy? After your second line in Powershell, I get a little spinning baton on the command line and it runs for a long time (several minutes now) with no indication of what's happening. If that's normal, what's a rough timeline for this process, assuming a good internet connection and computer? Seconds? Minutes? Hours? Thanks! – Outbound

... npm just answered that question for me. Need to set up a proxy. – Outbound

I wanted to try this solution, but there is something that makes me uneasy: there is label that says that the windows build status failed. What does that even mean?, and more importantly, should I care? – Melodist

I am curious as to why the Powershell execution policy needs to be set to unrestricted for the current user for all time. If you're a little more paranoid you can just set it for the current process. Set-ExecutionPolicy Unrestricted -Scope Process -Force – Cloudscape

This would be better asked on the github repo. If you do it your way, you would need to do that everytime you want to run npm-windows-upgrade. By changing the execution policy, you don't need to do that every time. – Foreknowledge

Do this after installing node.js msi, otherwise node.js msi will downgrade npm if not unselected during installation. – Blackout

I've just run the three commands above. npm has been udpated but node not. Is this expected? What can I do to update node to the latest version? – Anorexia

@PiotrBerebecki yes, that is expected. This just updates NPM. To get the latest node, go to nodejs.org, download and run the installer. Node comes with a version of NPM, usually a few minor versions back from the latest. You will need to run npm-windows-upgrade, as the node installer will overwrite npm. – Foreknowledge

npm install -g npm-windows-upgrade -> is working for windows7 – Umberto

@Outbound Yes, you need to setup a proxy for the PwerShell session, and sometimes even disable the dns check for this script with -d directive. After this worked for me. – Frontlet

It would be great if you could change "Officially recommended by the NPM team" to a link to the recommendation. – Robi

and what about node itself? – Chestnut

#4038439 You will need to change permissions on powershell to get this script to run. Set-ExecutionPolicy RemoteSigned – Triplicate

I tried on win 8.1 as admin. Got this error "scripts cannot be executed on this system" – Sizeable

But then again, one needs PowerShell. I'm not really into installing PowerShell just for upgrading Node. So I'd say this is the new best way for PowerShell users. – Lear

When using Powershell I cannot use the arrow keys to select a version, but it works in cmd – Above

Successfully updated upto v5.4.0, but I need v6 minimum. Any help? – Yowl

On Windows (10) PowerShell as Admin, npm install -g npm-windows-upgrade is fine, but npm-windows-upgrade gives Scripts cannot be executed on this system. – Margaretemargaretha

Did not work, because the first statemen is spelled wrong or could not be found – Triumvir

This works up to Win 10 Fall creators update and most recent NPM, dont understand what other people are saying about it. – Harhay

This upgrades NPM version. I want to upgrade Node version. Everyone is lying here – Exactitude

This upgrades the NPM version like mentioned on the question @ShahidKarimi – Levania

(Feb 2018; it must be easier now!) This isn't necessary now. The best answer in today's world is from @josh3736. I commented there, too. – Revkah

Successfully upgraded to 5.7.1 – Instauration

I followed the instruction, but when running "npm-windows-upgrade" I get the following error: npm-windows-upgrade : The term 'npm-windows-upgrade' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. – Scriptwriter

As of Nov 2nd 2018, I ran the commands but did not upgrade my node. I ended up uninstalling node and installing it from the website. – Snow

how do you upgrade node itself? – Jehovah

might want to run with --no-dns-check option if being behind a corporate proxy – Dravidian

@Jehovah First download the NodeJS version you need from nodejs.org/en/download/releases. This installs its own packaged version of NPM. If you need to change the version of NPM then, from a Run-as-Administrator PowerShell prompt, you can run npm install -g npm-windows-upgrade followed by npm-windows-upgrade -v WantedNpmVersion. – Interpolation

Worked for me after updating node version with latest LTE i.e. 10.15.3. Before that npm-windows-upgrade is not working for me. – Syllabub

In my case, Powershell was getting stuck while running npm-windows-upgrade and selecting the version to upgrade. I used cmd prompt in administrator and it did the job. However it only upgraded npm, not the node. – Cluster

@BenCarp try restarting your powershell as the environment variables are not up to date during that session. – Sideline

Actually this does not work if your versions of node/npm are sufficiently outdated. The npm-windows-upgrader scripts rely on language features (specifically, async functions) that are not supported until node 7.5+. The upgrader won't be working for you if your current versions are any older than that. – Belisle

In the Windows 10 there are somes steps to do : 1. Run PowerShell like an Administrator 2. Execute Set-ExecutionPolicy Unrestricted -Scope CurrentUser -Force for rules 3. Run npm install -g npm-windows-upgrade 4. And after this npm-windows-upgrade – Diminution

Followed the instructions. I am getting this error-C:\Users\leena\AppData\Roaming\npm\node_modules\npm-windows-upgrade\src\upgrader.js:26 async ensureInternet () { ^^^^^^^^^^^^^^ SyntaxError: Unexpected identifier at Object.exports.runInThisContext (vm.js:76:16) at Module._compile (module.js:542:28) at Object.Module._extensions..js (module.js:579:10) at Module.load (module.js:487:32) .. at Object.<anonymous> (C:\Users\leena\AppData\Roaming\npm\node_modules\npm-windows-upgrade\bin\npm-windows-upgrade.js:8:16) at Module._compile (module.js:570:32) – Tallula

I used npm i -g npm and it seemed to work. Why are you saying not to use it? – Ossuary

I had to run PowerShell as an Administrator – Tadeas

@jenson-button-event go to node website and download it from there – Gujral

Why should we use this if official doc say to use npm install npm@latest -g as far I can see the git of npm-windows-upgrade is more than a year old :/, in which way is better than the official install? – Armalla

I had to go to C:\Users\{user_name}\AppData\Roaming\npm and then run .\npm-windows-upgrade – Brodeur

Doesn't work. I get cb() never called!. Not because this command is wrong, but because npm is wrong and needs to be updated. But using npm to update npm doesn't work here. – Holster

@Armalla I believe npm install npm@latest -g is for Linux-based operating systems – Rhodium

npm-windows-upgrade may still work for some people but there haven't been releases for two years now and the owner has archived the repository. These instructions worked for me. – Ferial

This worked a treat! – Kazachok

The problem is that npm install -g npm installs to your personal %AppData% folder, but the PATH finds it first from the installed Program Files directory. https://mcmap.net/q/64233/-how-can-i-update-npm-on-windows obviates that. – Grassland

Answer 2

Download and run the latest MSI. The MSI will update your installed node and npm.

Deluge

Note 32 and 64 bit MSIs. Do not just click on "Windows Installer" link - that's 32 bit. Check where your current nodejs resides, in "Program Files" or on "Program Files (x86)". The "x86" means 32-bit. See the comments below about "old version was installed in a different directory". – Outsize

As of now (November 2014) this is will get you the latest node (0.10.33) but not the latest npm -- you will get npm 1.4.28. To update to a modern (2.x.x) npm on Windows, follow the instructions here: github.com/npm/npm/wiki/Troubleshooting#upgrading-on-windows – Capitalist

The node installer contains the latest version of npm that was available at the time of the node release. (on the 1.x branch) – Deluge

Current MSI package installation for version 0.12.4 includes a NPM upgrade to version 2.10.1. To update NPM to the latest version follow Option 3 from here. – Ancell

Current MSI package installation for version 4.1.2 includes a NPM upgrade to version 2.14.4 – Ulrica

MSI installed but didn't actually replace the only installation automatically. npm install npm worked for me. – Broadwater

I needed to update both npm and node (on a Windows box). I did the following (combining two of the answers above). 1. To update npm: npm install npm -g 2. To update node: go to nodejs.org/en and click the button to download the current version (v6.2.2 as of this date) You'll need this for Angular 2. – Headwaters

I had to do something similar to @RichWard but I had to use the installer from this answer to upgrade node then npm-windows-upgrade to upgrade npm. – Keele

I would recommend uninstalling your current node version from "Programs and Features" first... – Platus

@wayofthefuture: Why? In my experience, that's entirely unnecessary. – Deluge

Maybe, maybe not. I don't know how the installer works or what kind of recent coding changes have been made to it via GitHub recently. I like clean installs just my preference... – Platus

Is the exectution policy thing (and the use of npm-windows-upgrade) necessary also if using Git Bash (installed together with Git for Windows) to upgrade and run npm instead of Powershell? Or would running Git Bash as Administrator during the upgrade be enough? – Britishism

(Feb 2018; it must have gotten easier!) I've been working with Node and npm for a couple years. I get Node msi's from nodejs.org. Each msi I've used has upgraded from an older Node version without complaint or notice. Recent Node msi's have included an npm, though sometimes an old npm. docs.npmjs.com/troubleshooting/… says npm install -g npm works. I've done it; I haven't had difficulty. Very recently, I upgraded Node and got the current npm, too. – Revkah

I think the whole reason this question and these answers exist is because the nodejs documentation is terse and doesn't explicitly say anything about upgrading from older versions. I just installed over my version with the latest MSI and it worked fine. It noticed my existing node path statements and the installation didn't add new ones. Did it leave files from my old installation that are not in the new installation? I expect if any such files exist, it did leave them in place. That shouldn't harm the new installation, but is wasted space. – Rancho

WOW !! Thankyou so so much .. I have been trying all possible commands but finally this one worked – Ernest

This will work even if you are behind a proxy while the other solutions doesnt. – Auxin

Answer 3

To update NPM, this worked for me:

• Navigate in your shell to your node installation directory, eg C:\Program Files (x86)\nodejs
• run npm install npm (no -g option)

Mountain

This is actually one of the recommended approaches on Windows: github.com/npm/npm/wiki/Troubleshooting#upgrading-on-windows – Excerpta

This worked for me after I had updated node via the accepted answer. – Ahl

@singe3 The command prompt must be elevated (started as Admin) to be able to modify C:\Program Files. I don't really like this method because "npm install -g" will try to install under Program Files, thus the cmd prompt must always be run elevated to install other global packages. Option 2 in grenade's link is better IMHO: delete Program Files\nodejs\npm.cmd so it'll use the user's local npm. – Washedout

Simple and functional – Bohs

I needed to use npm install npm@latest – Smokeless

@Smokeless You should uninstall node, delete program files\node and %appdata%\node. ReInstall node. Then use npm-windows-upgrade (see my answer). npm-windows-upgrade is the best solution and does not have the pitfalls like the other answers here. The pitfall you have is now 2 npm versions on your system and depending on if the npmrc file, you could have multiple global packages and inconsistency. Like updating a global package but still getting the old version... – Foreknowledge

This doesn't update node, it installs npm into the local `.\node_modules` relative to where you execute it. – Mesenchyme

This gave me the same errors as running just npm install -g npm. What worked for me: Create a new folder directly under the drive (eg C:/Temp1), run npm install npm in it, then copy the contents into the correct locations in the global npm install directory. (eg copy C:/Temp1/node_modules/npm/bin/node.cmd to C:\Program Files\nodejs\node.cmd, and C:/Temp1/node_modules/npm to C:\Program Files\npm -- since it's expecting it a level higher) Not the most elegant, but works. – Copyholder

I have multiple users on my windows. And, npm install npm is best option. npm-windows-upgrade will only update npm copy of Administrator account. while npm install npm will work for different user account – Undone

Answer 4

Like some people, I needed to combine multiple answers, and I also needed to set a proxy.

This should work for anyone. I have zero desire to run an EXE file or MSI file .. uninstall/ reinstall, or manually delete files and folders. That is so 1999 :P

1. Run this to update NPM:

   Run PowerShell as administrator

   npm i -g npm    // This works
   

   I am not thinking this code actually upgrades your npm version below

   Set-ExecutionPolicy Unrestricted -Scope CurrentUser -Force
   npm install -g npm-windows-upgrade
   npm-windows-upgrade
   
   (courtesy of "Robert" answer)
   

Run this to update Node.js:

wget https://nodejs.org/download/release/latest/win-x64/node.exe -OutFile 'C:\Program Files (x86)\nodejs\node.exe'    (courtesy of BrunoLM answer)

If you get `wget : Could not find a part of the path .... "**, see below ...scroll down. Reading Web Response... It's at least punching through the firewall /proxy (if you have one or have already ran the code get through ...

Otherwise

You might need to set your proxy

npm config set proxy "http://proxy.yourcorp.com:811"    (yes, use quotes)

2 possible errors

1. It cannot find path of the path solution "where.exe node" (courtesy of Lonnie Best Answer)

   E.g. if Node.js is NOT living in "Program Files (x86)" perhaps with where.exe, it is living in 'C:\Program Files\nodejs\node.exe'.

   wget https://nodejs.org/download/release/latest/win-x64/node.exe -OutFile 'C:\Program Files\nodejs\node.exe'
   

2. Now perhaps it tries to upgrade but you get another error, "node.exe is being used by another process."

   • Close /shutdown other consoles .. command prompts and PowerShell windows, etc. Even if you're using npm in a command prompt, close it.

npm -v (3.10.8)

node -v ( v6.6.0)

DONE. I'm at the version that I want.

Titograd

My node is in c:\Program Files\nodejs – Carlile

This is the only answer that could still work (others looks pretty old and deprecated) and thanks god it works. – Rai

After deleted previous version of nodejs instance( like from program files, user data etc). It was giving me error like a previous version of nodejs is already install when i was trying to install 8.x version of nodejs. It solved my problem. – Robynroc

This will work only for node version greater than 8.0.0, mine is 6.x.x. It is not working for me. I wanted upgrade on ADO agent – Sergias

Answer 5

You can update your npm to the latest stable version with the following command:

 npm install npm@latest -g

Use PowerShell to run it. This command doesn't need windows administrator privileges and you can verify the result with npm -v

Forehead

Simplest and best answer for updating npm – Aspire

If you have nodejs installed, there are two version of npm installed on Windows. Running npm install npm@latest -g only update the global ( -g ) installed one ( %appdata%\npm\ ). To update npm that comes with nodejs ( %ProgramFiles%\nodejs\node_modules\npm ) you can download the .msi installer from nodejs.org/en and run it. Other official methods to upgrade npm: github.com/npm/npm/wiki/Troubleshooting#upgrading-on-windows – Slapup

This seems like the best answer because of its simplicity. – Sedimentology

Worked for me with small change. I wanted to specify a version when upgrading. So i used this: npm install npm@latest -g – Acquirement

Answer 6

You can use Chocolatey which is a package manager for windows (like apt-get for Debian Linux).

Install fresh (you might need to uninstall previously installed versions)

> choco install nodejs

Update to the latest version

> choco update nodejs

and for npm

> choco update npm

Nordgren

choco update npm is deprecated. Use npm-windows-upgrade to update npm. github.com/felixrieseberg/npm-windows-upgrade – Foreknowledge

@Robert choco update command is deprecated but we still can use choco upgrade command – Mesocarp

@Mesocarp the package npm is deprecated in chocolatey. See chocolatey.org/packages/npm – Foreknowledge

Followed this advice and chocolatey installed an incredibly old version of npm which overrode my slightly-old version, causing very bad things to happen. – Hardee

Answer 7

The previous answers will work installing a new version of Node.js (probably the best option), but if you have a dependency on a specific Node.js version then the following will work: "npm install npm -g". Verify by running npm -v before and after the command.

Reconstructionism

Sure it does @BrianDiPalma. Added screen shot to show upgrade from 2.14.12 to 3.8.2 – Reconstructionism

Answer 8

This works fine for me to update npm on Windows 7 x64:

• Windows start
• All Programs
• Node.js
• Node.js command prompt (alternative click)

• Run as administrator

  $ npm -g install npm

• remove C:\Program Files\nodejs\npm.cmd the new npm will be at C:\Users\username\appdata\roaming\npm\npm.cmd

Hope this helps.

Irs

This solution modifies the nodejs directory, leaving behind an orphaned npm. If you have more than 1 user on the machine, you just broke NPM for everybody else. This method also causes problems with global packages. the npm installed via this answer does not have the npmrc file, so global packages going forward will likely be installed in the wrong directory. If you update node, the nodejs/npm.cmd is now restored. So if nodejs updates npm, you are stuck on the old one unless you run that command again. – Foreknowledge

Answer 9

Open PowerShell as administrator.

To install a first time you can use this small script to download the latest msi and run it

$nodeLatest=((curl https://nodejs.org/download/release/latest/).Content | findstr x64.msi) -replace "<(.*?)>", "" -replace "\s+.+", "";
wget "https://nodejs.org/download/release/latest/$nodeLatest" -OutFile (join-path $env:TEMP node.msi); Start-Process (join-path $env:TEMP node.msi)

On future upgrades you can download just node.exe and update npm with

wget https://nodejs.org/download/release/latest/win-x64/node.exe -OutFile 'C:\Program Files\nodejs\node.exe'
npm i -g npm

You should now have the latest node and npm.

---

I went a little further and decided to implement a nvm for Windows.

https://github.com/brunolm/nvm

Install-Module -Name power-nvm

nvm install latest
nvm default latest

Shaefer

Excellent answer. Many would of course use C:\Program Files\nodejs\node.exe for the last part. – Unilingual

Answer 10

1. Installing latest npm version

npm install –g npm@latest 

(You can type "npm –version" to check that)

2. Installing Node

a. Install node new version via following URL: https://nodejs.org/en/download/current/ Follow the default choices
b. Remove C:\Users\\AppData\Roaming\NPM
c. Remove C:\Users\\AppData\Roaming\npm-cache

Optionally:

d. (Delete node_modules folder in your current project folder)
e. npm cache verify
f. npm install

Maria

This worked for me..You might need to use npm rebuild node-sass --force after you are done with installation because your environment has changed – Scarabaeus

Answer 11

Use Upgrade npm on Windows

This is the official document for a user to upgrade npm on Windows!

Here is my screenshot!

Selma

msi is also another choice! – Selma

From the page you linked to: "This is a small tool made by Microsoft DX engineers". So saying "this is the official document" is maybe a bit misleading. It sounds like you're saying it's official from the node or npm folks. – Firer

Answer 12

For what it's worth, I had to combine several answers...

1. Uninstall Node.js in control panel Add/remove programs.
2. Delete directories, both C:\Program Files (x86)\nodejs\ and C:\Program Files\nodejs\ if they exist.
3. Install the latest version, http://nodejs.org/download/

Flitting

Can you remember anything specific why you had to do this? I just tried it with downloading, installing and it worked instantly. – Burglary

No, But i think that the older version of node installed it in a different windows directory in the path. At least thats my assumption – Flitting

Answer 13

this is best tool to maintain version of NODE.Js i NVM

Node Version Manager (nvm) for Windows but for Windows, with an installer. Download Now! This has always been a node version manager, not an io.js manager, so there is no back-support for io.js. However, node 4+ is supported.

Washedup

Most powerful and convenient answer here? UPVOTE this one, people! If you agree. – Incidence

Answer 14

How to Update Node.js:

1. Uninstall Node.js. Click the Start menu, type "Change or Remove a Program", click on the item shown, find Node.js in the list and uninstall it.

2. Delete directories, both C:\Program Files (x86)\nodejs\ and C:\Program Files\nodejs\ if they exist.

3. Install the latest, https://nodejs.org/en/download

    The uninstall/delete/install seems unnecessary, but it often is and this will save your time.     These instructions come from Microsoft.

How to Update NPM:

    https://www.npmjs.com/package/npm-windows-upgrade

    This is the official documentation for upgrading npm on windows.

All was tested and working on Windows 10 (2017).

Novanovaculite

Answer 15

For me, after totally uninstalling node 10.29, and then installing node 4.2.2, there remained a 10.29 node.exe file in my c:\windows folder.

I found this by using the following command:

where.exe node

The command returned:

C:\Windows\node.exe
C:\Program Files\nodejs\node.exe

So even though I had successfully installed version 4.2.2 via the msi executable, the command node -v would continue to report I was running version 10.29.

I resolved the problem by deleting this file:

C:\Windows\node.exe

Thereafter, node -v reported the upgraded version instead of the unwanted remnants of the prior version.

Kileykilgore

Answer 16

To install the updates, just download the installer from the Nodejs.org site and run it again. The new version of Node.js and NPM will replace the older versions.

Hyla

this didn't work in my case with windows 10. I have npm v5.4.2 and node 7.5.0. When I wanted to install node v9.0.0 npm -v says 5.4.2 not 5.5.1 as it should be – Selfsupport

worked for me for node version 10 – Wamsley

Answer 17

For NodeJS

Download required node version msi from here and install

for Npm

Run PowerShell as Administrator

Set-ExecutionPolicy Unrestricted -Scope CurrentUser -Force
npm install -g npm-windows-upgrade
npm-windows-upgrade

Torietorii

Answer 18

I followed josh3737 and installed the latest MSI from the Node.js homepage.

But I had the additional problem that I still had the old version of Node.js and npm on the command line. The problem was caused by the new installation, and that it was installed into

C:\Program Files (x86)\nodejs\

instead of the previous installation in

C:\Program Files\nodejs\

The new installation added the new directory into my path variable after the old one. So the old installation was still the active one in the path. After removing C:\Program Files\nodejs\ from system path and C:\Users\...\AppData\Roaming\npm from user path and restarting the command line the new installation was active.

Maybe the least path was a local problem that has nothing to do with the new installation. I had two links to AppData\Roaming\npm in it. And maybe this can also be fixed by first uninstalling Node.js and installing the new version afterwards.

Manoeuvre

Answer 19

I was also facing similar issues. I followed below mentioned steps and it worked for me:

• go to Windows > Start > Node.js

  • right click on Node.js command prompt
  • click on Run as administrator

• ping registry.npmjs.org

• npm view npm version

• cd %ProgramFiles%\nodejs

• npm install npm@latest

and npm updated successfully. Earlier I was trying for CMD and that was throwing error. may be some path issue that got resolved by running NodeJs Command Prompt. hope it'll work for you. try this.

Mate

Answer 20

This works fine for me

1. Run Command Prompt as Administrator

2. Navigate to the folder containing nodejs (eg. C:\Program Files\nodejs)

3. Run Powershell -ExecutionPolicy Unrestricted

4. Run npm-windows-upgrade

5. This will show list of versions available to install. Just select your desired version by moving up/down key & Press Enter.
   
   This'll update your npm
6. To check the current version of npm

   Run npm --version

Command Prompt Screenshot

Presa

Answer 21

OK guys, I read (tried on Windows) all the previous stuff and all of these answers have their own disadvantages.

For the best way to update Node.js (at least for me), go to https://nodejs.org/en/ Then download the last version and install it in same folder you installed the previous version in - 1 min and it's done. You don't need to remove any old files.

Then update npm typing in cmd: npm install --save latest-version

Inset

Maybe during trying other solutions i accidentally updated npm. To update it type in cmd: npm install --save latest-version – Inset

Sometimes I still asks myself WHY I use windows. Thanks for your simple solution. – Lindalindahl

Answer 22

The easiest way I found so far to update Node.js is using Chocolatey. Use Chocolatey to install or update the latest version of Node.js on Windows:

Step 1: First, ensure that you already have Chocolatey installed. If not, use an administrative shell to install chocolatey through cmd.exe or PowerShell.exe. For more information, visit: https://chocolatey.org/docs/installation

Step 2: Install with cmd.exe. Run the following command:

@"%SystemRoot%\System32\WindowsPowerShell\v1.0\powershell.exe" -NoProfile -InputFormat None -ExecutionPolicy Bypass -Command "iex ((New-Object System.Net.WebClient).DownloadString('https://chocolatey.org/install.ps1'))" && SET "PATH=%PATH%;%ALLUSERSPROFILE%\chocolatey\bin"

To install with PowerShell.exe, visit: https://chocolatey.org/docs/installation

Step 3: Install or Update with following commands on cmd.exe (on administrative mode)

To Install Node.js: cinst nodejs.install

To Update Node.js: cup nodejs.install

Carnallite

Answer 23

follow these steps for window 10 or window 8

• press WIN + R and type cmd and enter
• npm i -g npm@next
• npm i -g npm@next OR npm i -g node@{version}
• Remove environment path C:\Program Files\nodejs from envrionment variable PATH.
• type refreshenv in cmd

Now you will have your new version which you installed.

Note: If you don't remove path. You will see the previous version of node.

Abhor

Answer 24

PowerShell does not execute npm directly, so I suggest using

.\npm install -g npm-windows-upgrade
.\npm-windows-upgrade

And it failed with:

You wanted to install npm 6.1.0, but the installed version is 3.10.10.

A common reason is an attempted "npm install npm" or "npm upgrade npm". As of today, the only solution is to completely uninstall and then reinstall Node.js. For a small tutorial, please see http://aka.ms/fix-npm-upgrade (dead link).

Please consider reporting your trouble to npm-windows-upgrade.

Latif

Answer 25

You can use these commands:

npm cache clean
npm update -g [package....]

If you are upgrading from a previous version of node, then you will want to update all existing global packages. You can also specify the package name to be updated.

Lingwood

Answer 26

This might help someone. Neither "npm-windows-upgrade" nor the installer alone did it for me. Powershell was still using an older version of node and npm.

So this is what I did (worked for me): 1. Download the latest installer from nodejs.org. Install node. It will update your node; everywhere (Powershell, cmd etc.). 2. Install the npm-windows-upgrade package (npm install -g npm-windows-upgrade) and run npm-windows-upgrade.

I didn't uninstall anything and didn't set any paths.

Pyxie

"Powershell was still using an older version of node and npm." You likely did some other update method in the past by modifying the path or running npm i -g npm. If you run into any issues in the future then you must do this: github.com/felixrieseberg/… – Foreknowledge

Answer 27

In my case, I discovered that I had two copies of Node.js installed. One under "C:\Program Files\nodejs" and another under "C:\Program Files (x86)\nodejs".

Hixon

Answer 28

This is what worked for me.

1. Open a local folder other than the one in which nodejs is installed.
2. Install npm in that folder with command npm install npm
3. Navigate to the folder containing node js. (C:\Program Files\nodejs\node_modules)
4. Delete the npm folder and replace it with the npm and bin folders in the local folder.
5. Run npm -v. Now you would get updated version for npm.

Note: I tried installing npm directly in "C:\Program Files\nodejs\node_modules" but it created errors.

Rubalcava

Answer 29

1. Start
2. Search for windows powershell
3. Right click and run as administrator
4. Type: where.exe node (returns the path of node.exe in your system. Copy this)
5. wget https://nodejs.org/download/release/latest/win-x64/node.exe -OutFile 'PATH-OF-NODE.EXE_WHICH_YOU_COPIED_JUST_NOW'
6. To check if it has worked, go to your Git bash/Normal command prompt and type: node -v
7. Here you can find the current version of node: https://nodejs.org/en/blog/release/

Logia