https://minhhh.github.io/tags/conda/Recent content in Conda on Huy Minh HaHugo -- gohugo.ioen-usFri, 09 Aug 2019 00:00:00 +0700https://minhhh.github.io/posts/nodejs-with-conda-and-nodeenv/Fri, 09 Aug 2019 00:00:00 +0700https://minhhh.github.io/posts/nodejs-with-conda-and-nodeenv/<p>When you want to develop your nodejs project on different node versions, you have some tools to help you install multiple node versions such as <code>nave</code>, <code>nvm</code>, <code>n</code>. However, this is still not as nice as <code>virtualenv</code> in Python, where you have completely isolated environments so one project does not affect the others.</p> <p>Fortunately, there is a tool called <a class="link" href="https://github.com/ekalinin/nodeenv" target="_blank" rel="noopener" >nodeenv</a> that can help you create isolated node.js environment the same way as <code>virtualenv</code>. Using <code>nodeenv</code> is already good enough, but if you don&rsquo;t want to store the virtualenv folder in the same project folder, then you would need some other tool to manage virtualenv folders globally. There are 2 options: <code>conda</code> and <code>pipenv</code>. <code>pipenv</code> does not integrate very well with shell scripts because you have to start a separate pipenv shell. <code>conda</code> is perfect because it can manage all kinds of packages, not just Python or nodejs and it&rsquo;s very compatible with shell scripts.</p> <p>In conclusion, using <code>conda</code> and <code>nodeenv</code> is a much better choice than just <code>nave</code> or <code>nvm</code>.</p>