BT

Node.js 4.2 "Argon" Released Under Long Term Support Plan

| by James Chesters Follow 1 Followers on Oct 20, 2015. Estimated reading time: 2 minutes |

The Node.js Foundation have released Argon, the first Node.js release covered under the working group's Long Term Support plan.

Argon, also known as Node.js version 4.2, comes with improvements and significant updates. Node.js is now updated with icu (International Components for Unicode) 56, which includes Unicode data 8.0, a reduced ICU data size, and changes to Stringsearch.

Additionally, 4.2 brings with it an upgraded npm 2.14.7, including a new user guide for npm orgs. Among other changes, npm 2.14.7 also means for developers that it no longer defaults to application/json for json requests.

Node's Argon release comes with a number of small issues, including where calling dns.setServers() while a DNS query is in progress can cause the process to crash on a failed assertion. Also reported is a bug with unreferenced timers running during beforeExit.

Commenting on the unreferenced timers issue, core team member Trevor Norris said that together with Jeremy Whitlock, Jeremiah Senkpiel and Fedor Indutny he had looked into it at length, describing it as "a bit of a rabbit hole," but that it had been determined that the behavior of beforeExit needed to be better defined.

On Reddit, in the discussion Node.js v4.2.0 will be first LTS release there was some confusion over what the significance of the Long Term Support release meant.

User runvc commented:

What difference does 'LTS' actually make for Node? As far as I can tell I just upgrade to the latest stable when I have time to upgrade or start a new project. Is this mostly for people that don't really know how Node works? Or are they planning to do something that makes old Node versions suddenly stop working?

In the blog post Essential Steps: Long Term Support for Node.js, the chair of the Node.js Foundation Technical Steering Committee, Rod Vagg, says:

The point of establishing an LTS plan for Node is to build on top of an existing stable release cycle by delivering new new versions on a predictable schedule that have a clearly defined extended support lifecycle. While this may seem at odds with the open source tradition of “release early, release often” it is an essential requirement for enterprise application development and operations teams.

Named after the noble gas, the first LTS release marks the beginning of a naming convention based on the Periodic Table of Elements that will be applied to distinguish LTS releases from regular Node.js releases. The gas' lack of chemical reactions have no bearing on the release's name, instead it having been chosen to be first in alphabetical order by the element's starting letter.

Rate this Article

Adoption Stage
Style

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread
Community comments

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Discuss

Login to InfoQ to interact with what matters most to you.


Recover your password...

Follow

Follow your favorite topics and editors

Quick overview of most important highlights in the industry and on the site.

Like

More signal, less noise

Build your own feed by choosing topics you want to read about and editors you want to hear from.

Notifications

Stay up-to-date

Set up your notifications and don't miss out on content that matters to you

BT