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

install nodejs 4.2 with newer npm #3350

Closed
linquize opened this issue Oct 13, 2015 · 5 comments
Closed

install nodejs 4.2 with newer npm #3350

linquize opened this issue Oct 13, 2015 · 5 comments
Labels
npm Issues and PRs related to the npm client dependency or the npm registry. question Issues that look for answers. windows Issues and PRs related to the Windows platform.

Comments

@linquize
Copy link

I manually upgrade npm to 3.3.4 which is newer than the one nodejs 4.2 ships (2.14.7).
Will the new npm be preserved or overwritten during upgrade nodejs?
I use Windows 7 64-bit MSI to install nodejs.

@ghost
Copy link

ghost commented Oct 13, 2015

The issue tracker isn't a Q&A forum.

@Fishrock123 Fishrock123 added windows Issues and PRs related to the Windows platform. build Issues and PRs related to build files or the CI. question Issues that look for answers. npm Issues and PRs related to the npm client dependency or the npm registry. and removed build Issues and PRs related to build files or the CI. labels Oct 13, 2015
@Fishrock123
Copy link
Contributor

Probably overwritten, I think?

There was discussion about having the installer have an option to not install npm, but I'm not sure where it went.

@Trott
Copy link
Member

Trott commented Oct 13, 2015

You can try opening an issue in the help repo: https://github.com/nodejs/help/issues

The answer may depend on how it was previously installed etc., but I think it will overwrite npm. However, updating it again should be as easy as npm install -g [email protected].

@kenany
Copy link
Contributor

kenany commented Oct 13, 2015

By default, npm is installed alongside node in C:\Program Files (x86)\nodejs. npm's globally installed packages (including npm if you do npm install -g npm) are stored separately in a user-specific directory (which is currently C:\Users\<username>\AppData\Roaming\npm). Thus, it is possible to end up with two different versions of npm. I believe the msi installer puts C:\Program Files (x86)\nodejs before C:\Users\<username>\AppData\Roaming\npm in your PATH, so if you run npm --version you will get the version of npm that came with node (this has confused many Windows over at the npm issue tracker, so much so that I usually just point them to this guide).

@jasnell jasnell closed this as completed Oct 14, 2015
@jasnell
Copy link
Member

jasnell commented Oct 14, 2015

Closing. Not an actual issue ;-). @linquize ... no worries, but just for future reference, questions like this are better suited for https://github.com/nodejs/help ;-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
npm Issues and PRs related to the npm client dependency or the npm registry. question Issues that look for answers. windows Issues and PRs related to the Windows platform.
Projects
None yet
Development

No branches or pull requests

5 participants