Heya,I've been using - quite successfully - nvm to manage my node versions, but, having changed from rvm to chruby recently for Ruby, I'd like to explore n as a similarly (at least from the outside) more simple option for Node.However, I'm unable to really find a good comparison between nvm and n, as in - what does each do well, and what does each do poorly?I read that there's an issue with npm when you switch versions with n - how is this different to nvm, and can I just use yarn as an npm substitute to skip around this all together?TL; DR: Pros and cons of NVM and N (or any of the other version managers, and whether I can use a node virtual env type package too)e.g. Which one is faster on resources, which one is easier to manage project specific node versions with, which one is it easier to install nightlies with, etc.Cheers!
Submitted March 02, 2017 at 05:49AM by DoubleDroz
No comments:
Post a Comment