Node: Installer puts down npm 4.5.0, not 5.

[cfjedimaster]

• Version: v8.0.0
• Platform: Windows 64 bit
• Subsystem:

Running the 64 bit installer today I noticed it put down npm 4.5.0, and not 5.0. Thinking it may have been a left over, I uninstalled, confirmed the folder was gone, reinstalled, and I still see the same.

From what I can see, c:\program files\nodejs\npm is 4.5.0. But under node_modules\bin, the npm there is 5.0.

[MylesBorins]

That is beyond strange as the installer is built from the tree... which has npm 5 hardcoded.

Can you try uninstalling again and confirm that c:\program files\nodejs\npm is gone?

[cfjedimaster]

Same. Uninstalled, emptied recycle bin, confirmed node -v didn't work in prompt (ditto for npm -v), reinstalled, and get the same results.

[dnalborczyk]

@cfjedimaster since npm 4.5 was never included in a node.js release, I'm guessing you upgraded npm globally itself with npm prior installing node.js v8.0 with npm 5.0 you might have to delete the global folder for npm as well. just a guess.

[cfjedimaster]

But when I uninstall, I can't run npm at all. As I said, when I do the reinstall, I see a new file called npm (and npm.cmd) in the folder, and running that directly and specifying it returns 4.5.0. I can share a video if it will help. :)

[vsemozhetbyt]

What is the version field in the c:\Program Files\nodejs\node_modules\npm\package.json?

[cfjedimaster]

5.0.0

[dnalborczyk]

what version of Windows are you running? if it's Windows 10 or similar, check: \Users{your-username}\AppData\Roaming\npm\node_modules\npm

That's where you might find your npm v4.5.

alternatively also in the global cache folder, except I think npm v5 won't use it - and/or wipe it - not sure.

[vsemozhetbyt]

And "C:\Program Files\nodejs\npm.cmd" -v gives you 4.5.0?

[cfjedimaster]

Hey folks a real quick response as I have to run out there door. It was a global npm causing the issue. I did a npm uninstall -g npm, which removed that one, and then the npm laid down by the installer took over and was version 5. Thank you, thank Sam Roberts (coworker here at IBM who saw it ), and I guess we can close this? I'm going to blog this tomorrow just in case other people have the same issue.

Again - thank you!

[refack]

In these cases I recommend running npm config list and where npm as they uncover pre existing artifacts.

[cfjedimaster]

Afaik, I can't where npm on Windows (to be clear, I can in WSL). I did a
find on npm from the CLI, but I focused on the 2 Program Files directories
as running it on the root of C was taking too long. If I had been a bit
more patient, it may have found it.

On Tue, May 30, 2017 at 6:15 PM, Refael Ackermann [e-mail]
wrote:

In these cases I recommend running npm config list and where npm as they
uncover pre existing artifacts.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nodejs/node/issues/13311#issuecomment-305035299, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAYBvPk5bcOBlZbNygHxJOfuZ2faXYegks5r_KL9gaJpZM4NqxY-
.

--

Raymond Camden, Developer Advocate at IBM

Email : [email protected]
Blog : www.raymondcamden.com
Twitter: raymondcamden

[refack]

Afaik, I can't where npm on Windows (to be clear, I can in WSL). I did a
find on npm from the CLI, but I focused on the 2 Program Files directories
as running it on the root of C was taking too long. If I had been a bit
more patient, it may have found it.

where is a windows tool:

C:\Users\refael>where where
C:\WINDOWS\System32\where.exe

very helpful when things start acting strange...

[cfjedimaster]

Ah - I had tried in Powershell where it didn't work correctly.

On Tue, May 30, 2017 at 6:21 PM, Refael Ackermann [e-mail]
wrote:

Afaik, I can't where npm on Windows (to be clear, I can in WSL). I did a
find on npm from the CLI, but I focused on the 2 Program Files directories
as running it on the root of C was taking too long. If I had been a bit
more patient, it may have found it.

where is a windows tool:

C:\Users\refael>where whereC:\WINDOWS\System32where.exe

very helpful when things start acting strange...

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nodejs/node/issues/13311#issuecomment-305036415, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAYBvEQzbrY87LsH3RX1kQRJXM2oDkewks5r_KRqgaJpZM4NqxY-
.

--

Raymond Camden, Developer Advocate at IBM

Email : [email protected]
Blog : www.raymondcamden.com
Twitter: raymondcamden

[cfjedimaster]

Wowza, yep, where npm would have found this real quick. Will definitely
add this to my blog post. Thank you again (and everyone else :).

On Tue, May 30, 2017 at 6:22 PM, Raymond Camden [e-mail]
wrote:

Ah - I had tried in Powershell where it didn't work correctly.

On Tue, May 30, 2017 at 6:21 PM, Refael Ackermann <
[email protected]> wrote:

Afaik, I can't where npm on Windows (to be clear, I can in WSL). I did a
find on npm from the CLI, but I focused on the 2 Program Files directories
as running it on the root of C was taking too long. If I had been a bit
more patient, it may have found it.

where is a windows tool:

C:\Users\refael>where whereC:\WINDOWS\System32where.exe

very helpful when things start acting strange...

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nodejs/node/issues/13311#issuecomment-305036415, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAYBvEQzbrY87LsH3RX1kQRJXM2oDkewks5r_KRqgaJpZM4NqxY-
.

--

===============
Raymond Camden, Developer Advocate at IBM

Email : [email protected]
Blog : www.raymondcamden.com
Twitter: raymondcamden

--

Raymond Camden, Developer Advocate at IBM

Email : [email protected]
Blog : www.raymondcamden.com
Twitter: raymondcamden

[cfjedimaster]

Hey folks - a question. Should a user have expected that using the Windows uninstall feature would have removed global modules? I know I did, but I could be wrong about that expectation. If so, is this a bug that should be reopened (or perhaps I can make a new one that more clearly defines it).

[refack]

Hey folks - a question. Should a user have expected that using the Windows uninstall feature would have removed global modules? I know I did, but I could be wrong about that expectation. If so, is this a bug that should be reopened (or perhaps I can make a new one that more clearly defines it).

IMHO global modules are "user data" and should not be removed without an explicit agreement from the user (e.g. a "remove all settings and data" checkbox).
Ref: https://github.com/nodejs/node/issues/12345
^^^^^^^^ 12345 😄

[bnoordhuis]

FWIW, the UNIX installer/uninstaller is careful not to unlink the global node_modules when it contains files it didn't install.

[cfjedimaster]

Yeah, that makes sense. I told npm to install npm, and therefore, the Node uninstaller should leave it be. However, it feels like npm is a special case maybe. Perhaps the installer could notice the existence of multiple npm installs and warn the user?

[gibfahn]

FWIW, the UNIX installer/uninstaller is careful not to unlink the global node_modules when it contains files it didn't install.

What do you mean by the UNIX installer?

[bnoordhuis]

@gibfahn python tools/install.py uninstall