Weekly Update - Sep 4th, 2015

Yosuke Furukawa (@yosuke-furukawa)

Node.js News — September 4th

Node.js v4.0.0 is released

Node.js v4.0.0

This week is the most historical week. Finally we have released Node.js v4.0.0(stable). Thanks to the every Node/io.js collaborator. This Node.js is the most stable Node ever. We have reviewed all of patches and the state of the test suite is more stable and there are more active contributors in new Node.

We would like to talk about this news, changes, features. But currently we don't have so much spaces and times. We hope that Node community will post more blog entries or more news.

Node.js v4.0.0 Notable changes

This list of changes is relative to the last io.js v3.x branch release, v3.3.0. Please see the list of notable changes in the v3.x, v2.x and v1.x releases for a more complete list of changes from 0.12.x. Note, that some changes in the v3.x series as well as major breaking changes in this release constitute changes required for full convergence of the Node.js and io.js projects.

Known issues

See https://github.com/nodejs/node/labels/confirmed-bug for complete and current list of known issues.

  • Some uses of computed object shorthand properties are not handled correctly by the current version of V8. e.g. [{ [prop]: val }] evaluates to [{}]. #2507
  • Some problems with unreferenced timers running during beforeExit are still to be resolved. See #1264.
  • Surrogate pair in REPL can freeze terminal. #690
  • Calling dns.setServers() while a DNS query is in progress can cause the process to crash on a failed assertion. #894
  • url.resolve may transfer the auth portion of the url when resolving between two full hosts, see #1435.

Node.js v4.0.0(stable) entry is posted

  • We have posted Node v4.0.0 entry. This entry has more details about Node.js v4.0.0.

We are creating the list of modules that currently do not work with Node.js v4.0.0

  • We are listing modules that do not work with Node.js v4.0.0, If you have some troubles in your modules with Node.js v4.0.0, please provide information in this issue.

Community Updates

  • We still need a V8 maintainer for our LTS build! Head on over to GitHub to see if the requirements match your capabilities.
  • Jeremiah Senkpiel, Node TSC member, has introduced Node.js v4.0.0 deeply. Please check this blog
  • Daniel Khan posted the entry about Node.js v4.0 performance, features and LTS. His entry will help your migration.

If you have spotted or written something about Node.js and io.js, do come over to our Evangelism team repo and suggest it on the Issues page, specifically the Weekly Updates issue.

Upcoming Events

Have an event about Node.js and io.js coming up? You can put your events here through the Evangelism team repo and announce it in the Issues page, specifically the Weekly Updates issue.