Node.js javascript runtime

Node.js v6.12.3 & v8.9.4 (LTS) release, server-side JavaScript runtime environment


Node.js is a JavaScript runtime based on the  Chrome V8 engine. Node.js uses efficient, lightweight event-driven, non-blocking I/O models that makes it lightweight and efficient. The Node.js package ecosystem, npm, is the largest ecosystem of open source libraries in the world.

The Node.js project maintains multiple types of releases:

  • Current: Released from active development branches of this repository, versioned by SemVer and signed by a member of the Release Team. Code for Current releases is organized in this repository by major version number. For example v4.x. The major version number of Current releases will increment every 6 months allowing for breaking changes to be introduced. This happens in April and October every year. Current release lines beginning in October each year have a maximum support life of 8 months. Current release lines beginning in April each year will convert to LTS (see below) after 6 months and receive further support for 30 months.
  • LTS: Releases that receive Long-term Support, with a focus on stability and security. Every second Current release line (major version) will become an LTS line and receive 18 months of Active LTS support and a further 12 months of Maintenance. LTS release lines are given alphabetically ordered codenames, beginning with v4 Argon. LTS releases are less frequent and will attempt to maintain consistent major and minor version numbers, only incrementing patch version numbers. There are no breaking changes or feature additions, except in some special circumstances.
  • Nightly: Versions of code in this repository on the current Current branch, automatically built every 24-hours where changes exist. Use with caution.

Node.js v6.12.3(LTS) was released, and the changelog is as follows:

  • build:
    • configure can now be run from any directory (Gibson Fahnestock) #17321


  • [b1b975370f] – benchmark,path: remove unused variables (薛定谔的猫) #15789
  • [ac6f345f70] – build: allow running configure from any directory (Gibson Fahnestock) #17321
  • [017492eca2] – build: add serial commas to messages in configure script (Rich Trott) #17464
  • [ad9a8578ee] – build: fix test-v8 target (Michaël Zasso) #17269
  • [9ba35e859f] – build: remove empty VCLibrarianTool entry (Daniel Bevenius) #17191
  • [3d22e81d70] – build: minor corrections to configure descriptions (Daniel Bevenius) #17094
  • [92f41e553a] – build: allow enabling the –trace-maps flag in V8 (Evan Lucas) #14018
  • [b563908ff9] – crypto: use SetNull instead of Set (Daniel Bevenius) #17521
  • [b287b9e64b] – deps: V8: cherry-pick e8e9c07 from upstream (Ali Ijaz Sheikh)
  • [9804e7f3bb] – deps: V8: cherry-pick 9622696 from upstream (Ali Ijaz Sheikh)


Windows 32-bit Installer:
Windows 64-bit Installer:
Windows 32-bit Binary:
Windows 64-bit Binary:
macOS 64-bit Installer:
macOS 64-bit Binary:

Node.js v8.9.4(LTS) was released, and the changelog is as follows:

  • deps:
    • upgrade npm to 5.6.0 (Kat Marchán) #17535
  • build:
    • configure can now be run from any directory (Gibson Fahnestock) #17321
  • [62ad4cca07] – tools/doc: add tools/remark-* to eslintignore (Ivan Wei) #17240
  • [ce91a38970] – benchmark: fix http/simple.js benchmark (Anatoli Papirovski) #17583
  • [3fe7f9f102] – benchmark: set maxHeaderListPairs in h2 headers.js (Anatoli Papirovski) #17194
  • [4597bd753a] – benchmark: use unique filenames in fs benchmarks (Rich Trott) #16776
  • [92723701cd] – benchmark,path: remove unused variables (薛定谔的猫) #15789
  • [58a667c884] – build: add a make help option for common targets (Gibson Fahnestock) #17323
  • [5b04621c40] – build: allow running configure from any directory (Gibson Fahnestock) #17321
  • [6ed330610a] – build: define HAVE_OPENSSL macro for cctest (Matheus Marchini) #17461


Leave a Reply

Your email address will not be published. Required fields are marked *