n or nvm for managing node versions - is keeping global modules for each version a good idea? : <p>I've been using docker containers for node, unfortunatly on OSX <code>gulp watch</code> is super slow and buggy. So I'm back to installing tools on host machine :( unfortunatly.</p>

<p>Choosing between <code>n</code> and <code>nvm</code></p>

<p>One major difference I see between these is the global packages, <code>n</code> keeps single global repo for all versions, and <code>nvm</code> keeps em separate.</p>

<p>Not having worked on many node.js projects, I have a feeling this is an important distinction, but I'm not sure if it really matters in real life.</p>

<p>any ideas?</p>
