Node v4.2.0 – Stable version released

Rate this post


Node.js v4.2.0 “Argon” (Stable) was released in 2015-10-12, the first release covered under the new Long Term Support plan!

As an LTS release, support for v4.x will continue for a period of 30 months from today. This means that individuals and businesses building on Node.js will have a stable and supported platform on which to grow. For more details on what LTS means for Node.js, see Rod Vagg’s blog post.


To better differentiate LTS releases from regular Node.js releases, we have introduced a naming convention based on the Periodic Table of Elements that applies only to LTS releases. The name selected for v4.2.0 is “Argon”, so as to be in alphabetical order by the first letter.

Developers can easily determine if they are working with an LTS version of Node.js by checking the process.release.lts property within node. This property will be undefined in regular releases.

$ node -v
$ node -pe process.release.lts

Notable changes

The first Node.js LTS release! See for details of the LTS process.

  • icu: Updated to version 56 with significant performance improvements (Steven R. Loomis)
  • node:
    • Added new -c (or –check) command line argument for checking script syntax without executing the code (Dave Eddy)
    • Added to hold the current ICU library version (Evan Lucas)
    • Added process.release.lts to hold the current LTS codename when the binary is from an active LTS release line (Rod Vagg)
  • npm: Upgraded to npm 2.14.7 from 2.14.4, see release notes for full details (Kat Marchán)

Known issues

See for a complete and current list of known issues.

  • Some problems with unreferenced timers running during beforeExit are still to be resolved.
  • Surrogate pair in REPL can freeze terminal.
  • Calling dns.setServers() while a DNS query is in progress can cause the process to crash on a failed assertion.
  • url.resolve may transfer the auth portion of the URL when resolving between two full hosts.

More info – Download Node v4.2.0

Thanks for watching my post. If you have any question, feel free to feedback here. I and colleagues are willing to support you. Goodluck!

Check Also


Why Node.js beats Java and .Net for Web, mobile, and IoT apps

Rate this post Today, I’ll be sharing to you a very great blog from InfoWorld ...