Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

5.0.0 didn't upgrade npm #3601

Closed
vitaly-t opened this issue Oct 30, 2015 · 12 comments
Closed

5.0.0 didn't upgrade npm #3601

vitaly-t opened this issue Oct 30, 2015 · 12 comments
Labels
install Issues and PRs related to the installers. npm Issues and PRs related to the npm client dependency or the npm registry. windows Issues and PRs related to the Windows platform.

Comments

@vitaly-t
Copy link
Contributor

My npm remains to be 2.6.0 after a successful installation of NodeJS 5.0.0, using the UI installer.

System: Windows 10 Pro, 64-bit.

@mscdex mscdex added windows Issues and PRs related to the Windows platform. install Issues and PRs related to the installers. npm Issues and PRs related to the npm client dependency or the npm registry. labels Oct 30, 2015
@jakobmulvad
Copy link

Same here, npm remained at 2.13.0

Windows 8.1, 64-bit

@Fishrock123
Copy link
Contributor

Calling in @othiym23 and @iarna -- Not sure if this is related to npm/npm#10166 or not.

As far as I know, nothing changed in the installer since 4.0.0.

@mikeal
Copy link
Contributor

mikeal commented Oct 30, 2015

is this a PATH issue? perhaps npm was upgraded independently and is in a preferred PATH?

@Fishrock123
Copy link
Contributor

I bet this is the same issue as #3606 but originating from b3c4cec

@ivantsov
Copy link

is this a PATH issue? perhaps npm was upgraded independently and is in a preferred PATH?

I guess no because I tried to run npm -v in folder where nodejs is installed and got 2.14.0.

@alexlamsl
Copy link

FYI - upgraded from 4.1.1 (Windows 8.1 x64) and 4.1.2 (Windows Server 2012 R2) to 5.0.0, both instances work as expected with npm 3.3.6 even before and after reboot.

@othiym23
Copy link
Contributor

Darn. This being a PATH issue was my guess as well. I don't have any good tips for everybody, because this feels like an installer thing, not an npm thing, and my knowledge of the Windows and Mac installers isn't what it could be. I should have some cycles to look into this next week, though.

@ivantsov
Copy link

I solved the problem and it's what I found.

Initially I had npm 3.3.6 in folder where nodejs is installed and npm 2.x.x in C:\Users\%username%\AppData\Roaming\npm\node_modules. After removing npm 2.x.x folder npm -v returns correct version - 3.3.6.

Also if remove nodejs from computer at all and install 4.2.1 first and then install 5.0.0, everything will be okay.

Thus, I assume that the problem wasn't in PATH but in the installer.

@smartmouse
Copy link

Upgraded node 5.00 and my npm version(3.3.6) is correct.
c:\strongloop>npm -v
3.3.6
I checked my path
c:\strongloop>echo %path%
C:\Users\IBM_ADMIN\AppData\Roaming\npm;C:\Program Files\nodejs500;

In my C:\Users\IBM_ADMIN\AppData\Roaming\npm, there is no npm at all, so the npm
I am picking up is the default npm from c:\Program Files\nodejs500

I was wondering if you have installed npm yourself before?
e.g. npm install -g npm@2.x.x.
Then it will add the npm to
C:\Users\IBM_ADMIN\AppData\Roaming\npm

I experiment this npm install -g npm
Then npm will be install into
C:\Users\IBM_ADMIN\AppData\Roaming
\npm\node_modulles

c:\Users\IBM_ADMIN\AppData\Roaming\npm\node_modules>npm install -g npm
C:\Users\IBM_ADMIN\AppData\Roaming\npm\npm -> C:\Users\IBM_ADMIN\AppData\Roaming
\npm\node_modules\npm\bin\npm-cli.js
C:\Users\IBM_ADMIN\AppData\Roaming\npm
└── npm@3.3.10

c:\Users\IBM_ADMIN\AppData\Roaming\npm\node_modules>dir
Volume in drive C has no label.
Volume Serial Number is 00F8-54F7

Directory of c:\Users\IBM_ADMIN\AppData\Roaming\npm\node_modules
10/31/2015 09:27 PM

.
10/31/2015 09:27 PM npm
10/27/2015 12:00 AM strongloop

@ivantsov
Copy link

ivantsov commented Nov 1, 2015

was wondering if you have installed npm yourself before?

It's very likely because I've used nodejs for 2 or 3 years and I really don't remember whether I installed npm separately or not...

@ghost
Copy link

ghost commented Nov 4, 2015

For those having problems on windows, I would uninstall node, delete nodejs out of program files, delete npm and npm-cache out of %appdata%. Then reinstall node 5 and install your global packages again.

@jasnell
Copy link
Member

jasnell commented Apr 27, 2016

Closing as it appears there is nothing further to do on this item. Can reopen if necessary

@jasnell jasnell closed this as completed Apr 27, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
install Issues and PRs related to the installers. npm Issues and PRs related to the npm client dependency or the npm registry. windows Issues and PRs related to the Windows platform.
Projects
None yet
Development

No branches or pull requests

10 participants