install nodejs 4.2 with newer npm #3350

Activity

2. Fishrock123

   added

   windowsIssues and PRs related to the Windows platform.Issues and PRs related to the Windows platform.

   buildIssues and PRs related to Node.js builds or CI infrastructure.Issues and PRs related to Node.js builds or CI infrastructure.

   questionIssues asking questions about Node.js.Issues asking questions about Node.js.

   npmIssues and PRs related to the npm client dependency or the npm registry.Issues and PRs related to the npm client dependency or the npm registry.

   and removed

   buildIssues and PRs related to Node.js builds or CI infrastructure.Issues and PRs related to Node.js builds or CI infrastructure.

   on Oct 13, 2015
3. Fishrock123 commented on Oct 13, 2015

   

   Fishrock123

   on Oct 13, 2015

   Contributor

   More actions

   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.
4. Trott commented on Oct 13, 2015

   

   Trott

   on Oct 13, 2015

   Member

   More actions

   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 npm@3.3.4.
5. kenany commented on Oct 13, 2015

   

   kenany

   on Oct 13, 2015

   Contributor

   More actions

   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).
6. jasnell

   closed this as completedon Oct 14, 2015
7. jasnell commented on Oct 14, 2015

   

   jasnell

   on Oct 14, 2015

   Member

   More actions

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