<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:og="http://ogp.me/ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:schema="http://schema.org/" xmlns:sioc="http://rdfs.org/sioc/ns#" xmlns:sioct="http://rdfs.org/sioc/types#" xmlns:skos="http://www.w3.org/2004/02/skos/core#" xmlns:xsd="http://www.w3.org/2001/XMLSchema#" version="2.0" xml:base="https://www.linuxjournal.com/tag/nodejs">
  <channel>
    <title>node.js</title>
    <link>https://www.linuxjournal.com/tag/nodejs</link>
    <description/>
    <language>en</language>
    
    <item>
  <title>Node.js Version Chaos Management</title>
  <link>https://www.linuxjournal.com/content/nodejs-version-chaos-management</link>
  <description>  &lt;div data-history-node-id="1338906" class="layout layout--onecol"&gt;
    &lt;div class="layout__region layout__region--content"&gt;
      
            &lt;div class="field field--name-field-node-image field--type-image field--label-hidden field--item"&gt;  &lt;img src="https://www.linuxjournal.com/sites/default/files/nodeimage/story/nodejs.jpg" width="384" height="368" alt="" typeof="foaf:Image" class="img-responsive" /&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-author field--type-ds field--label-hidden field--item"&gt;by &lt;a title="View user profile." href="https://www.linuxjournal.com/users/shawn-powers" lang="" about="https://www.linuxjournal.com/users/shawn-powers" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Shawn Powers&lt;/a&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"&gt;&lt;p&gt;
I'm just starting out in the world of development, and many of the projects
I'm interested in exploring are written in Node.js. If you're an old hand
at such things, you already know that which version of Node you use on
a particular application is vitally important. (This is actually one of
the reasons Docker is so amazingly amazing when it comes to deploying
Node apps, but I digress.)
&lt;/p&gt;

&lt;p&gt;
For folks like me, the version issue can be confusing and
frustrating. Thankfully, I ran across a simple tool with a simple name:
n. Once you have Node.js installed on your system, using n, it's possible
to download and make active a very specific version of the program, so
your specific application works properly. In fact, when I was installing
the NOMP stratum server for Bitcoin mining recently, I had to use n to
try more than a dozen versions before I found the one that worked as expected.
&lt;/p&gt;

&lt;p&gt;
Node.js is a powerful, incredible language that is used by many smart
developers. Those of us who are just getting started, however, are easily
intimidated by version needs. If that describes you, or if you understand the
nuances but just want a quick and easy way to manage it, check out n
today. There are instructions on the Github page: &lt;a href="https://github.com/tj/n"&gt;https://github.com/tj/n&lt;/a&gt;.
&lt;/p&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-link field--type-ds field--label-hidden field--item"&gt;  &lt;a href="https://www.linuxjournal.com/content/nodejs-version-chaos-management" hreflang="und"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Thu, 17 Dec 2015 21:38:42 +0000</pubDate>
    <dc:creator>Shawn Powers</dc:creator>
    <guid isPermaLink="false">1338906 at https://www.linuxjournal.com</guid>
    </item>

  </channel>
</rss>
