Cannot update npm (node 8.4.0) #300

t0lkman · 2017-09-07T08:12:19Z

manuelbieh · 2017-09-07T12:36:03Z

Same problem here.

kuncevic · 2017-09-10T23:58:36Z

I had the same issue, and here is how I got through :

run npm install -g npm and while it is running:
remove(backup) files npm.cmd and npm from c:\Program Files\nodejs\
remove(backup) .bin folder from c:\Program Files\nodejs\node_modules\npm\node_modules, then it should succeed
If you have Refusing to deleteissues with any other npm module files/folders you have to just remove these and restart update process. To restart copy npm.cmd back to c:\Program Files\nodejs\ . Then once npm install -g npm is running, remove npm.cmd, otherwise you get in to Refusing to delete npm.cmd issue, you might repeat that process until npm install -g npm is happy.

To remove the files you can use this shortcut: mv npm.cmd "c:\Program Files\nodejs\node_modules\npm\node_modules" as suggested by @farnetani

my env:
windows 7 x64, node 8.4, nvm 1.1.6

alexgorbatchev · 2017-09-16T01:28:24Z

Seeing same problem

cannap · 2017-09-17T12:44:35Z

same
windows 10
node 8.5.0
npm 5.3.0
nvm 1.1.0

MichalLytek · 2017-09-22T14:52:02Z

@kuncevic
The easier solution is to copy dir node_modules/npm from the nodejs location, remove the npm bin and cmd, and run node npm-cli.js i -g npm@latest inside bin dir in the copied folder.

wayofthefuture · 2017-09-23T17:57:08Z

So much for production. Good luck doing in a script.

wayofthefuture · 2017-09-23T17:58:21Z

They should rename continuous integration to continuous intebreaktion

wayofthefuture · 2017-09-25T15:55:32Z

@19majkel94 Couldn't get it working with your method... any other ideas which I could script?

coreybutler · 2017-09-25T22:17:27Z

It appears as though npm has changed how it updates itself... without telling anyone. npx was also introduced with only a minor version change (as opposed to a major change).... which is semantically correct, but still hard to follow along.

Apparently there is some file sandboxing happening. I spent the better part of today investigating and attempting a fix, but each fix surfaces another issue. Bear with me, I'll get it fixed as soon as I can. I'm the only one working on this at the moment... and I happen to be in the middle of a different product launch (after 2yrs of work), so a PR would gladly be accepted.

wayne-werner · 2017-09-26T15:53:48Z

I wish I could help, but I have an observation... I think that the issues are related to the shortcut to "C:/Program Files/nodejs". Perhaps if a junction were used instead of a shortcut? Windows can't tell the difference between a 'real' directory and a junction. So, it would look like node was really and truly installed in the default directory. No more 'operating' in a directory outside of the resolved directory.

https://docs.microsoft.com/en-us/sysinternals/downloads/junction

wayne-werner · 2017-09-26T16:02:01Z

BTW, using a junction should future proof nvm4w against any future changes to npm's behavior.

MichalLytek · 2017-09-26T16:21:29Z

@wayne-oscme
Have you read the readme?

The second option is to use a symlink. This concept requires putting the symlink in the system PATH, then updating its target to the node installation directory you want to use. This is a straightforward approach, and seems to be what people recommend.... until they realize just how much of a pain symlinks are on Windows. This is why it hasn't happened before.

In order to create/modify a symlink, you must be running as an admin, and you must get around Windows UAC (that annoying prompt). Luckily, this is a challenge I already solved with some helper scripts in node-windows. As a result, NVM for Windows maintains a single symlink that is put in the system PATH during installation only. Switching to different versions of node is a matter of switching the symlink target. As a result, this utility does not require you to run nvm use x.x.x every time you open a console window. When you do run nvm use x.x.x, the active version of node is automatically updated across all open console windows. It also persists between system reboots, so you only need to use nvm when you want to make a change.

wayne-werner · 2017-09-26T16:55:05Z

@19majkel94
Please read about junctions. The 'symlink' aka window's shortcut has problems re resolution of target directory from processes. While window's explorer and terminal seem to handle them nicely, they aren't handled nicely in other processes. Open notepad, choose open file to get the standard window's file dialog. Navigate to "C:/Program Files/nodejs" and see where you end up.

Being a redirect to the target directory, which as we see is where processes end up, can lead to some interesting issues.

Junctions are the equivalent of hard links in *nix. Windows only supports these to directories, and not to files, but that's all we need here. They are not redirects. They are, for all intents and purposes, the directory, no different than the path created when the directory was first created.

They don't redirect, they are the destination. They can be deleted and created again with each 'use' command. Therefore, they will have the same effects and capabilities as shortcuts, but none of the downfalls that are creating the current problem.

coreybutler · 2017-09-27T13:38:13Z

This has nothing to do with junctions/hard links/symlinks. @kuncevic provided a screenshot citing npm errors, the key part being Refusing to delete ... which is outside of ..... That is a hard-coded message in npm, preventing further operations. Bottom line: npm is refusing to full update itself.

This didn't seem to be an issue until npm 5.x.x, and I'm still digging through the details to figure out what has changed. I may have to write a workaround (i.e. hack), which I'm never fond of. I'm also looking into utilizing the msi packages, which seems to be the only way to get the attention of the folks at npm.

If you're in dire need of updating npm, you can download it via https://github.com/npm/npm/archive/vX.X.X.zip and extract it into the node_modules directory of your node installation root. You'll need to manually create a symlink in the node installation root to npm.cmd and npx.cmd. The final file structure should look something like:

nvm
- v8.5.0
   - node_modules
       - npm
          - bin
               - npm.cmd
               - npx.cmd
          ...
   - node.exe
   - npm.cmd (symlink to v8.5.0/node_modules/npm/bin/npm.cmd)
   - npx.cmd (symlink to v8.5.0/node_modules/npm/bin/npx.cmd)

wayne-werner · 2017-09-28T03:50:35Z

Okay, I guess I should try before selling. I replaced the shortcut with a junction, and got the same exact issue. Thought I had something there. Sorry to waste your time.

…

On Wed, Sep 27, 2017 at 9:38 AM, Corey Butler ***@***.***> wrote: This has nothing to do with junctions/hard links/symlinks. @kuncevic <https://github.com/kuncevic> provided a screenshot citing npm errors, the key part being Refusing to delete ... which is outside of ..... That is a hard-coded message in npm, preventing further operations. Bottom line: npm is refusing to full update itself. This didn't seem to be an issue until npm 5.x.x, and I'm still digging through the details to figure out what has changed. I may have to write a workaround (i.e. hack), which I'm never fond of. I'm also looking into utilizing the msi packages, which seems to be the only way to get the attention of the folks at npm. If you're in dire need of updating npm, you can download it via https://github.com/npm/npm/archive/vX.X.X.zip and extract it into the node_modules directory of your node installation root. You'll need to manually create a symlink in the *node installation root* to npm.cmd and npx.cmd. The final file structure should look something like: nvm - v8.5.0 - node_modules - npm - bin - npm.cmd - npx.cmd ... - node.exe - npm.cmd (symlink to v8.5.0/node_modules/npm/bin/npm.cmd) - npx.cmd (symlink to v8.5.0/node_modules/npm/bin/npx.cmd) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#300 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEZgRbY_GVys0bfnD_kaM_PYl6QUmZKDks5smk_PgaJpZM4PPcf-> .

kuncevic · 2017-09-29T11:24:10Z

Just updated 5.4.1 → 5.4.2 with no issues.

c:\>npm install npm -g
C:\Program Files\nodejs\npx -> C:\Program Files\nodejs\node_modules\npm\bin\npx-cli.js
C:\Program Files\nodejs\npm -> C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js
+ npm@5.4.2
removed 1 package and updated 2 packages in 12.125s

coreybutler · 2017-09-29T15:41:10Z

@kuncevic - thanks... that's indicative the problem must be within npm 5.4.3+.

wayne-werner · 2017-09-29T15:53:27Z

npm -g install npm@5.4.2 still fails for me, same errors. [Edit] BTW, that's starting from 5.3.0, which was installed with nvm install 8.5.0

…

On Fri, Sep 29, 2017 at 11:41 AM, Corey Butler ***@***.***> wrote: @kuncevic <https://github.com/kuncevic> - thanks... that's indicative the problem must be within npm 5.4.3+. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#300 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEZgRQnw_jxuz_dDZl3OsZVO_MNkHlBGks5snQ-qgaJpZM4PPcf-> .

doug2k1 · 2017-09-29T16:06:03Z

For me it fails from Node 8.4.0 and up. It installs NPM 5.3.0, and then won't allow me to upgrade it.
Older Node versions (I have 4.8.4) allow NPM to update normally.

manuelbieh · 2017-10-02T15:39:06Z

Man. npm 5 and nvm really sucks big time (but I blame npm 5 here since 4 works perfectly fine). I've downgraded to npm 4.6.1 last week and just tried to give 5.4.2 another try. Looks like npm has been uninstalled while trying to install react-native-cli, a completely different package:

Manuel@Manuel-406 /cygdrive/d/htdocs/wallet
$ npm install -g react-native-cli
C:\Program Files\nodejs\npx -> C:\Program Files\nodejs\node_modules\npm\bin\npx-cli.js
npm WARN Error: EPERM: operation not permitted, scandir 'C:\Program Files\nodejs\node_modules\npm\node_modules\libnpx\node_modules\yargs\node_modules\os-locale\node_modules\execa\node_modules\cross-spawn\node_modules\shebang-command\node_modules'
npm WARN  { Error: EPERM: operation not permitted, scandir 'C:\Program Files\nodejs\node_modules\npm\node_modules\libnpx\node_modules\yargs\node_modules\os-locale\node_modules\execa\node_modules\cross-spawn\node_modules\shebang-command\node_modules'
npm WARN   stack: 'Error: EPERM: operation not permitted, scandir \'C:\\Program Files\\nodejs\\node_modules\\npm\\node_modules\\libnpx\\node_modules\\yargs\\node_modules\\os-locale\\node_modules\\execa\\node_modules\\cross-spawn\\node_modules\\shebang-command\\node_modules\'',
npm WARN   errno: -4048,
npm WARN   code: 'EPERM',
npm WARN   syscall: 'scandir',
npm WARN   path: 'C:\\Program Files\\nodejs\\node_modules\\npm\\node_modules\\libnpx\\node_modules\\yargs\\node_modules\\os-locale\\node_modules\\execa\\node_modules\\cross-spawn\\node_modules\\shebang-command\\node_modules' }
npm ERR! path C:\Program Files\nodejs\npm
npm ERR! code EPERM
npm ERR! errno -4048
npm ERR! syscall open
npm ERR! Error: EPERM: operation not permitted, open 'C:\Program Files\nodejs\npm'
npm ERR!  { Error: EPERM: operation not permitted, open 'C:\Program Files\nodejs\npm'
npm ERR!   cause:
npm ERR!    { Error: EPERM: operation not permitted, open 'C:\Program Files\nodejs\npm'
npm ERR!      errno: -4048,
npm ERR!      code: 'EPERM',
npm ERR!      syscall: 'open',
npm ERR!      path: 'C:\\Program Files\\nodejs\\npm' },
npm ERR!   stack: 'Error: EPERM: operation not permitted, open \'C:\\Program Files\\nodejs\\npm\'',
npm ERR!   errno: -4048,
npm ERR!   code: 'EPERM',
npm ERR!   syscall: 'open',
npm ERR!   path: 'C:\\Program Files\\nodejs\\npm',
npm ERR!   parent: 'v8.5.0' }
npm ERR!
npm ERR! Please try running this command again as root/Administrator.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\Manuel\AppData\Roaming\npm-cache\_logs\2017-10-02T14_54_04_833Z-debug.log

Manuel@Manuel-406 /cygdrive/d/htdocs/_git/wallet
$ npm install -g react-native-cli
sh: npm: Kommando nicht gefunden.

yavorski · 2017-10-04T12:54:46Z

ubuntu: 16.04.2 LTS
nodejs: 8.6.0
npm: 5.3.0

npm i -g npm@latest

/home/user/.npm-global/bin/npm -> /home/user/.npm-global/lib/node_modules/npm/bin/npm-cli.js
/home/user/.npm-global/bin/npx -> /home/user/.npm-global/lib/node_modules/npm/bin/npx-cli.js
+ npm@5.4.2
added 68 packages, removed 164 packages and updated 14 packages in 14.307s

npm -v still prints 5.3.0 and it's not updated?

coreybutler · 2017-10-04T17:32:50Z

@yavorski - this is nvm for Windows. I think you want nvm for *nix.

coreybutler · 2017-10-04T17:35:00Z

I have confirmed this issue is sandboxing within npm 5.x.x. Prior editions of npm did not have this. Unfortunately, the fix is non-trivial, and judging by @yavorski's experience, it's not specific to this project.

yavorski · 2017-10-05T11:21:30Z

Yep no nvm in my case. Linux + Nodejs from nodesource.

larryboymi · 2017-10-20T14:46:12Z

Having same issue here...

Obiwarn · 2020-10-07T12:24:22Z

I just needed Step 4, i.e. Just download and fresh install Node JS.
Then it worked.

patricknelson · 2020-10-14T01:31:09Z

Reinstalling the node version works fine, but since this is an issue associated with nvm, why not use the power of nvm to fix the problem? For me, instead of going through add/remove programs, it was way quicker/simpler to keep it all in the command line. For example:

nvm uninstall VERSION
nvm install VERSION

After that, close and re-open the shell. Quick and easy (now that you know, at least). 😄

If you have any issues (e.g. nvm indicates that the version is already installed), then check to see if the folder associated with that version still exists (e.g. %NVM_HOME%\VERSION) and that the file node.exe isn't still there. If it is still there, make sure you didn't already have any apps potentially running node (e.g. in my case my IDE was running it, so I closed that and was able to completely remove).

EDIT: ⚠️ I suppose this simple solution comes with one important side effect: It will remove your globally installed packages... hmm... may still be simpler to manually reinstall those. Be warned! ⚠️

sandyfigueroa · 2020-11-23T21:42:50Z

This script works perfect: #300 (comment)
https://gist.github.com/nokidding/aafaf90adc80cbce54b676340817bb13

Thank you!

liuliangsir · 2020-12-23T06:09:43Z

This powershell script works perfect: #300 (comment)

Thanks!

bladeoflight16 · 2021-01-09T03:37:52Z

@ganselmo If you're installing via the Control Panel, you're not using nvm. You need to uninstall that version before you even install nvm.

bladeoflight16 · 2021-01-09T03:39:56Z

@jakobrosenberg

wouldn't npx npm-windows-upgrade run globally unless you're inside a node project with a local installation of npm-windows-upgrade?

This uses the npx executable script that you're trying to update, so it's likely to fail due to locking the file.

begin-again · 2021-02-09T17:43:49Z

I got this work by renaming npm.cmd to npm1.cmd and then deleted other npm files: npm, npx.cmd, npx. Then I ran npm1 install -g npm

MuhammadAbbasAkhtar · 2021-02-16T10:53:30Z

I had the same issue, and here is how I got through :

run npm install -g npm and while it is running:
remove(backup) files npm.cmd and npm from c:\Program Files\nodejs\
remove(backup) .bin folder from c:\Program Files\nodejs\node_modules\npm\node_modules, then it should succeed
If you have Refusing to deleteissues with any other npm module files/folders you have to just remove these and restart update process. To restart copy npm.cmd back to c:\Program Files\nodejs\ . Then once npm install -g npm is running, remove npm.cmd, otherwise you get in to Refusing to delete npm.cmd issue, you might repeat that process until npm install -g npm is happy.

To remove the files you can use this shortcut: mv npm.cmd "c:\Program Files\nodejs\node_modules\npm\node_modules" as suggested by @farnetani

my env:
windows 7 x64, node 8.4, nvm 1.1.6

Its been 3 years since this reply, but it still works!
Thank you so much

alekslario · 2021-02-23T15:02:35Z

This was my fix:
1.Uninstall npm, node, remove all related directories.
2. Remove nvm bloat if any left
3. Install Volta
4. Everything works out of the box + build in rust
5. ???
6. Profit

onx2 · 2021-02-26T16:50:45Z

This was my fix:
1.Uninstall npm, node, remove all related directories.
2. Remove nvm bloat if any left
3. Install Volta
4. Everything works out of the box + build in rust
5. ???
6. Profit

Feels kind of mean to offer another package as a solution... but this absolutely worked out of the box for me and I love Rust. Thanks for the info @alekslario

maximborisov · 2021-03-02T10:41:22Z

I modified this answer for node 15.10.0 and npm 7.5.3 and it very helpful for me. I added one another step for renaming npx too

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

median-dxz · 2021-03-04T10:32:59Z

Another idea I've tried (I don't know if anyone has already mentioned it) is to install npm directly without using npm itself. Refer to npmjs in the “Direct Download” section, and it works.

GorvGoyl · 2021-03-13T20:00:17Z

A batch script which works fine.
https://gist.github.com/nokidding/aafaf90adc80cbce54b676340817bb13

This works. To use:

download this as updateNpm.bat file
open powershell in that same folder and run this command ./updateNpm.bat latest

spaciandd · 2021-05-18T09:07:02Z

A batch script which works fine.
https://gist.github.com/nokidding/aafaf90adc80cbce54b676340817bb13

This works. To use:

download this as updateNpm.bat file

open powershell in that same folder and run this command ./updateNpm.bat latest

That worked for me, at last.

Thank you

relu91 · 2021-07-26T07:31:48Z

nvm for Linux has this install-latest-npm command, maybe it is worth integrating the script above in nvm-windows as well.

nsmithdev · 2021-12-29T15:35:40Z

For me I only get the problem when updating npm from npm v6.
So using a newer version of npm via npx to run the upgrade works for me.

For the newest version
npx npm install -g npm

Or use a specific version
npx npm@7 install -g npm@7

SuperDzej · 2022-01-11T14:22:23Z

Hi guys, have also problem to report after Windows reinstall can't seam to get latest npm for nvm node version 6.12.0 which I need to use, tried nvm version 1.1.9 and 1.1.7, it keeps failing with:

C:\Program Files\nodejs
`-- (empty)

npm ERR! Windows_NT 10.0.19042
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "-g" "npm"
npm ERR! node v6.12.0
npm ERR! npm  v3.10.10
npm ERR! path C:\Program Files\nodejs\node_modules\.staging\@gar\promisify-f70bb42b
npm ERR! code ENOENT
npm ERR! errno -4058
npm ERR! syscall rename

npm ERR! enoent ENOENT: no such file or directory, rename 'C:\Program Files\nodejs\node_modules\.staging\@gar\promisify-f70bb42b' -> 'C:\Program Files\nodejs\node_modules\npm\node_modules\@gar\promisify'
npm ERR! enoent ENOENT: no such file or directory, rename 'C:\Program Files\nodejs\node_modules\.staging\@gar\promisify-f70bb42b' -> 'C:\Program Files\nodejs\node_modules\npm\node_modules\@gar\promisify'
npm ERR! enoent This is most likely not a problem with npm itself
npm ERR! enoent and is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! Please include the following file with any support request:
npm ERR!     C:\WINDOWS\system32\npm-debug.log
npm ERR! code 1

Tried all methods above all lead to this issue. Tried to make this folders, but it starts adding packages and then folder disappears and get same error. Tried installing this promisify globally doesn't help, on version 14.18.3 I'm able to update npm with that method to rename npm folder and execute that npm script in bin folder but on this no. After I do npm install it totally nukes whole npm and you can't use command anymore it throw error as whole bin folder it gone.

Tried separate 6.12.0 download from node, deleted nvm, it seams this is node issue, not nvm itself.

Latest update, I managed to update with specific version like 5.7.1, as I needed min npm version 5 so I guess will go with that if anyone needs it. Command I used was:

npm i -g npm@5.7.1

dschulten · 2022-01-13T16:50:35Z

This was my fix: 1.Uninstall npm, node, remove all related directories. 2. Remove nvm bloat if any left 3. Install Volta 4. Everything works out of the box + build in rust 5. ??? 6. Profit

Note that you need to enable Windows Developer Mode to allow Volta to set symlinks. Otherwise you get issues with access privileges similar to nvm. I have switched to Volta now but that might be helpful for nvm, too.

devtobee · 2022-01-26T16:34:04Z

Just delete the folder ...\AppData\Roaming\npm and \AppData\Roaming\npm-cache.
then try
npm install -g npm

JimiC · 2022-04-24T15:13:30Z

I was trying to upgrade npm@6.14.16 which comes along with node@14.19.1 and faced the same issue.
I ended up using #300 (comment) guide to make it finally upgrade.
Once it finished I noticed that the node folder now contained also some ps1 scripts and any upgrade or downgrade of npm works fine after that. Probably because the system calls now the ps1 script to start npm thus not getting blocked by the failure to delete the cmd files.

Using node@16.13.1 with npm@8.1.2 has no problem upgrading.

Looks like that from whatever version of npm the team fixed this issue, npm install -g npm@latest just works.

nagendragillalu · 2022-05-24T07:46:59Z

Elevating user privileges to Administrator solved the issue for me.

TrejoCode · 2022-09-28T17:06:22Z

Usage:

.\updateNpm.bat <version>

Example:

.\updateNpm.bat 8.2.0

Thank you

A batch script which works fine. https://gist.github.com/nokidding/aafaf90adc80cbce54b676340817bb13

aczekajski · 2022-10-24T06:05:57Z

How come this 5 years old issue is still not fixed..? I believe original nvm has a special command for upgrading npm and it should be the case here too. Having to rely on some obscure .bat scripts found in comments is ridiculous...

Andrew-wong-ty · 2023-03-07T03:27:46Z

I am a windows 10 user.
I tried all the ways I can find, but they still do not work for me. 😥

And finally, I uninstall nodejs and then re-install it. Then everything is ok! This is what I did:

Uninstall nodejs, and then delete the environment variable path like: C:\Program Files\nodejs
Install the latest version of nodejs from here; ⚠️ you'd better not install nodejs in disk c.
After installing, type node -v and npm -v in cmd. If you can see the version, congratulations! No "npm ERR" anymore! If not, add the nodejs environment variable path.

coreybutler · 2023-03-29T02:00:13Z

Yes folks, volta is an option, as is nodist, fnm, nvs, etc. You're welcome to use those. I'm going to remove comments about other version managers though, because they don't help this project improve... and that's the point of the issues for this project.

For anyone finding this issue from Google, please make sure you've read the instructions... specifically the ones about removing any prior versions of Node.js (https://github.com/coreybutler/nvm-windows/wiki/Common-Issues#uninstall-existing-node-installation-before-installing-nvm4w). It is possible to update npm, but you cannot have conflicts in your PATH, or permission restrictions... and there are a few older versions of npm with hardcoded pathing issues. When the v1.1.11 patch release drops, use the debug function to check your environment for potential problems.

I still cannot replicate this problem and there has been a help wanted label for 5 years. I believe it when people say they are still running into npm update problems, but without an environment to test on, it's really hard to troubleshoot. At this point though, with active development proceeding on Runtime and inconsistency in failures, it's time to close this issue. If anyone runs into this again, please open a new issue and provide details. It's important to know things like the specific build of Windows, the locale, whether it's running in an Active Directory controlled environment or not, whether developer mode is on/off, which shell is running the command, whether the shell is run as an administrator or not, whether there are special characters in your install path or not, whether Node was installed without a version manager before or not, whether another version manager was used before NVM4W, etc.

MaxiSantos · 2023-06-07T00:11:11Z

I asked CHATGPT and it suggested to upgrade npm with npm install -g npm@latest

If you're using nvm-windows to manage your Node.js versions on Windows and you want to update npm to X version, you can follow these steps:

Open a Command Prompt or PowerShell window.
Make sure you're using the Node.js version you want to update by running the following command:
```
nvm use <version>
```
Replace <version> with the Node.js version you want to use.
To update npm, you can use the following command:
```
npm install -g npm@X-version
```
This will install the X version of npm globally on your system.
Once the installation is complete, verify the npm version by running:
```
npm --version
```
You should see the X version of npm that you installed.

By following these steps, you should be able to update npm to the X version using nvm-windows on Windows.

Follow this url to know which version of npm belongs to node
https://nodejs.org/en/download/releases

This was referenced Sep 23, 2017

PACKAGE-LOCK.JSON NIGHTMARE npm/npm#18613

Open

npm@5.3: npm prune --production fails npm/npm#17781

Closed

coreybutler added the help wanted label Sep 25, 2017

coreybutler mentioned this issue Sep 26, 2017

New node v8.4.0 and 8.5.0 installation broken npm #305

Closed

28 tasks

AntonRand mentioned this issue Oct 9, 2017

EPERM: operation not permitted miickel/gulp-angular-templatecache#146

Closed

pastelmind mentioned this issue Aug 4, 2020

README lacks information about upgrading npm #522

Closed

webartoli mentioned this issue Apr 18, 2021

Cannot update global packages #638

Closed

Repository owner deleted a comment from vinicioslc Mar 29, 2023

coreybutler closed this as completed Mar 29, 2023

Cannot update npm (node 8.4.0) #300

Cannot update npm (node 8.4.0) #300

Comments

t0lkman commented Sep 7, 2017 • edited

My Environment

I'm using NVM4W version:

I have already...

My issue is related to (check only those which apply):

Expected Behavior

Actual Behavior

Steps to reproduce the problem:

manuelbieh commented Sep 7, 2017

kuncevic commented Sep 10, 2017 • edited

alexgorbatchev commented Sep 16, 2017

cannap commented Sep 17, 2017 • edited

MichalLytek commented Sep 22, 2017 • edited

wayofthefuture commented Sep 23, 2017

wayofthefuture commented Sep 23, 2017

wayofthefuture commented Sep 25, 2017

coreybutler commented Sep 25, 2017

wayne-werner commented Sep 26, 2017

wayne-werner commented Sep 26, 2017

MichalLytek commented Sep 26, 2017

wayne-werner commented Sep 26, 2017

coreybutler commented Sep 27, 2017

wayne-werner commented Sep 28, 2017 via email

kuncevic commented Sep 29, 2017 • edited

coreybutler commented Sep 29, 2017

wayne-werner commented Sep 29, 2017 via email • edited

doug2k1 commented Sep 29, 2017

manuelbieh commented Oct 2, 2017 • edited

yavorski commented Oct 4, 2017 • edited

coreybutler commented Oct 4, 2017

coreybutler commented Oct 4, 2017

yavorski commented Oct 5, 2017

larryboymi commented Oct 20, 2017

Obiwarn commented Oct 7, 2020

patricknelson commented Oct 14, 2020 • edited

sandyfigueroa commented Nov 23, 2020

liuliangsir commented Dec 23, 2020

bladeoflight16 commented Jan 9, 2021

bladeoflight16 commented Jan 9, 2021

begin-again commented Feb 9, 2021

MuhammadAbbasAkhtar commented Feb 16, 2021

alekslario commented Feb 23, 2021

onx2 commented Feb 26, 2021

maximborisov commented Mar 2, 2021

median-dxz commented Mar 4, 2021

GorvGoyl commented Mar 13, 2021

spaciandd commented May 18, 2021

relu91 commented Jul 26, 2021

nsmithdev commented Dec 29, 2021 • edited

SuperDzej commented Jan 11, 2022 • edited

dschulten commented Jan 13, 2022

devtobee commented Jan 26, 2022

JimiC commented Apr 24, 2022 • edited

nagendragillalu commented May 24, 2022

TrejoCode commented Sep 28, 2022

Usage:

aczekajski commented Oct 24, 2022

Andrew-wong-ty commented Mar 7, 2023

coreybutler commented Mar 29, 2023

MaxiSantos commented Jun 7, 2023

t0lkman commented Sep 7, 2017 •

edited

kuncevic commented Sep 10, 2017 •

edited

cannap commented Sep 17, 2017 •

edited

MichalLytek commented Sep 22, 2017 •

edited

kuncevic commented Sep 29, 2017 •

edited

wayne-werner commented Sep 29, 2017 via email •

edited

manuelbieh commented Oct 2, 2017 •

edited

yavorski commented Oct 4, 2017 •

edited

patricknelson commented Oct 14, 2020 •

edited

nsmithdev commented Dec 29, 2021 •

edited

SuperDzej commented Jan 11, 2022 •

edited

JimiC commented Apr 24, 2022 •

edited