title: nvm vs nave vs n | packages processing comparsion
body: <p>Node.js is sometimes confusing when it comes to version management...</p>
  
  <p>I am trying to arrange various projects as i am doing with ruby projects. For example:</p>
  
  <p>With ruby i can create file such as <code>.rvmrc</code> and fill with something like <code>rvm --create use 1.9.3@my-app</code></p>
  
  <p>This thing creates and uses all gems specifically to configured gemset. Which allows to have various options for any kind of project, and switch easily among them. So ruby does this in one place.</p>
  
  <p>I want to achieve this for node.js projects.</p>
  
  <p>Node works differently. I want to know the details about that, and especially of each node version management tool.</p>
  
  <h1>The point is to know which version management tool for which goal...</h1>
  
  <h2>And why there are so many.</h2>
  
  <p>More accurately: i want <code>npm install &lt;package-name&gt;</code> to chosen node version. And after switching to other versions, this installed package to be missing, or have different version installed before (or certain one). Just like <code>gemset</code> is working.</p>