I used to do something like this... Install global modules to a version-agnostic /use/local/share/node_modules and always export NODE_PATH (or similar).
But what I found is that I ended up chasing breaking changes when updating node anyway. So I have jumped on the wagon and now the only thing I install globally is express. And I am so anxious about adapting to express 3... On Mar 20, 2012 10:08 AM, "Mark Hahn" <[email protected]> wrote: > I love nvm and npm. However, whenever I switch to a new version of node > with nvm I have to reinstall all my global npm modules. Apparently the > global modules are stored in the node directory which is created anew. > > Is my setup normal? Is there a way around this problem? > > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > You received this message because you are subscribed to the Google > Groups "nodejs" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en > -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
