Upgrade AppData\Roaming\npm about npm-windows-upgrade HOT 5 CLOSED

Hey, if you didn't attempt to install npm with npm install -g npm, everything is fine. Even if you did, things are still okay - Windows will however use the npm installed with Node.js instead, since the official Node.js installer references the Node directory in PATH before the global AppData directory.

This installer is trying to minimally invasive and upgrade the npm version inside the Node.js folder (which should be the one installed used anyway, unless the user provisioned npm or node him/herself.)

If Windows is already using the one in %appdata%\npm\node_modules\npm, the installer is actually not required - and a simple npm install -g npm@latest is enough to upgrade.

Does that make sense? Or did I misunderstand you?

from npm-windows-upgrade.

I have used npm install -g npm, the main issue with this method is the npmrc file gets removed during the install. This breaks npm until you replace the npmrc file.

If this tool was only meant to upgrade npm in the Node.js folder and nodejs\node_modules\npm is the npm instance we should be using, I'm happy with that as the solution 👍

from npm-windows-upgrade.

Good point. I don't want to put myself or Microsoft into the position of telling people how to use npm. I can probably get the path of the npm installation used and update that one.

from npm-windows-upgrade.

If I am understanding everything correct, I believe the pull request I sent that was integrated should be causing the default behavior now to first query the first npm in your path for its global install location via -
npm config --global get prefix

I'd expect this to return the AppData path if that's the install you have, although my current setup is installed at another location within my home directory so I can't test that assumption very well at the moment. Perhaps this issue is fixed?

from npm-windows-upgrade.

I assume this issue is fixed no - if we fail with installing npm in AppData, we're now also installing the desired version in the NodeJS folder. I'll close this as fixed.

Thanks everybody!

from npm-windows-upgrade.