You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems like nvm installs the latest version available for npm, this is fine if you're also trying to install a recent version of node via nvm; however, if you're trying to install an 0.2.x version of node, npm install will fail as (npm version 0.3.x) no longer supports the 0.2.x branch of node.
I'm not sure the best way to go about this, but some kind of "recommended" or "suggested" npm version should be installed compared to the requested version of node.
Or another idea, to simply specify which version of npm you want installed when adding a new node version with nvm.
The text was updated successfully, but these errors were encountered:
I wonder if this is why I haven't been able to install v0.2.x lately. Honestly I don't want to put a bunch of stuff into nvm. I think this should be solved by npm's installer script if at all. It can tell what version of node you're using and know what version of npm to install. I don't plan on spending much time supporting 0.2.x now that 0.4.x is out and stable. I consider 0.4.0 the first stable release of node.
It seems like
nvm
installs the latest version available fornpm
, this is fine if you're also trying to install a recent version ofnode
vianvm
; however, if you're trying to install an0.2.x
version ofnode
,npm
install will fail as (npm
version0.3.x
) no longer supports the0.2.x
branch ofnode
.I'm not sure the best way to go about this, but some kind of "recommended" or "suggested"
npm
version should be installed compared to the requested version ofnode
.Or another idea, to simply specify which version of
npm
you want installed when adding a newnode
version withnvm
.The text was updated successfully, but these errors were encountered: