Nvm: Migrating global modules to new installation of node
Suppose I've node v0.10.32, nvm install 0.10.32, and I have global packages for that environment, for example I install express-generator, nodemon, pm2, etc in 0.10.32
I want upgrade from 0.10.32 to 0.10.34, after I install 0.10.34, and I use nvm use 0.10.34, why I can't use express-generator or nodemon anymore? Why I should install all again?
Is there a simplistic way to do such thing?
raitucarp
All 3 comments
oh sorry I didn't read copy-packages
raitucarp
on 19 Dec 2014
But It's not resolve this Issue, rather than re-installation of global modules, it takes more time
raitucarp
on 19 Dec 2014
The option has been renamed to reinstall-packages, please use that instead :-)
341 tracks the issue that non-npm modules don't really work with this method, and will involve adding a new option that actually _copies_ over modules instead of reinstalling them.
I'm closing this issue, because nvm isn't meant to be used to have a single globally installed version of node, it's meant to manage multiple ones, so global modules are your responsibility to manage. You may be thinking of https://www.npmjs.com/package/n for that.
ljharb
on 19 Dec 2014
Related issues
goalidea
·
3Comments
markedcahinde
·
5Comments
dillon
·
3Comments
serbiant
·
4Comments
cdelorme
·
5Comments
Most helpful comment
The option has been renamed to
reinstall-packages, please use that instead :-)341 tracks the issue that non-npm modules don't really work with this method, and will involve adding a new option that actually _copies_ over modules instead of reinstalling them.
I'm closing this issue, because
nvmisn't meant to be used to have a single globally installed version ofnode, it's meant to manage multiple ones, so global modules are your responsibility to manage. You may be thinking of https://www.npmjs.com/package/n for that.