-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
Comments
Same here, npm remained at 2.13.0 Windows 8.1, 64-bit |
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. |
is this a PATH issue? perhaps npm was upgraded independently and is in a preferred PATH? |
I guess no because I tried to run |
FYI - upgraded from |
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. |
I solved the problem and it's what I found. Initially I had npm Also if remove nodejs from computer at all and install Thus, I assume that the problem wasn't in PATH but in the installer. |
Upgraded node 5.00 and my npm version(3.3.6) is correct. In my C:\Users\IBM_ADMIN\AppData\Roaming\npm, there is no npm at all, so the npm I was wondering if you have installed npm yourself before? I experiment this npm install -g npm c:\Users\IBM_ADMIN\AppData\Roaming\npm\node_modules>npm install -g npm c:\Users\IBM_ADMIN\AppData\Roaming\npm\node_modules>dir Directory of c:\Users\IBM_ADMIN\AppData\Roaming\npm\node_modules 10/31/2015 09:27 PM npm 10/27/2015 12:00 AM strongloop |
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... |
For those having problems on windows, I would uninstall node, delete nodejs out of |
Closing as it appears there is nothing further to do on this item. Can reopen if necessary |
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.
The text was updated successfully, but these errors were encountered: