Thu, 12 Dec 2013 06:10:46 UTC - release

2013.12.12, Version 0.10.23 (Stable)

  • uv: Upgrade to v0.10.20 (Timothy J Fontaine)

  • npm: Upgrade to 1.3.17 (isaacs)

  • gyp: update to 78b26f7 (Timothy J Fontaine)

  • build: include postmortem symbols on linux (Timothy J Fontaine)

  • crypto: Make Decipher._flush() emit errors. (Kai Groner)

  • dgram: fix abort when getting fd of closed dgram (Fedor Indutny)

  • events: do not accept NaN in setMaxListeners (Fedor Indutny)

  • events: avoid calling once functions twice (Tim Wood)

  • events: fix TypeError in removeAllListeners (Jeremy Martin)

  • fs: report correct path when EEXIST (Fedor Indutny)

  • process: enforce allowed signals for kill (Sam Roberts)

  • tls: emit 'end' on .receivedShutdown (Fedor Indutny)

  • tls: fix potential data corruption (Fedor Indutny)

  • tls: handle ssl.start() errors appropriately (Fedor Indutny)

  • tls: reset NPN callbacks after SNI (Fedor Indutny)

Source Code:

Macintosh Installer (Universal):

Windows Installer:

Windows x64 Installer:

Windows x64 Files:

Linux 32-bit Binary:

Linux 64-bit Binary:

Solaris 32-bit Binary:

Solaris 64-bit Binary:

Other release files:




80980a23ec1915a0d4522fd4423a2eee25bf9ba5  node-v0.10.23-darwin-x64.tar.gz
c9c0f6772f2bda746d3997f4d821da9090dcd2a3  node-v0.10.23-darwin-x86.tar.gz
4c7d17ae61c753750e8f5ae989e3d80f7c8f89ea  node-v0.10.23-linux-x64.tar.gz
afa901a312350ec8b271d402261a7882e1d3640b  node-v0.10.23-linux-x86.tar.gz
30d5e06cfed35eea80d5ee4643858c157d104a85  node-v0.10.23-sunos-x64.tar.gz
2c4ce154b8595848119bb63164ca021f4fe8457e  node-v0.10.23-sunos-x86.tar.gz
d51b641354a41243830ff6e3bdd1e03a7758fc38  node-v0.10.23-x86.msi
a7711fbb958350011641c218dae64c0c6f1f80a8  node-v0.10.23.pkg
8717942d1bdfa8902ce65cd33b4293d16b486c64  node-v0.10.23.tar.gz
12d1e0a6373bb2b67129c7f0ebc514b793b106af  node.exe
9f107c4dba21fee76bbb5ac2fe552d40e6ae5e70  node.exp
52b4c463f8b667c24a54a0d8cd583b677706ae3c  node.lib
ec619173e2e867b929d4178ecbe561639aed4cb2  node.pdb
837ff717c2842c32e0804ce6c131404fc8599d8d  pkgsrc/nodejs-ia32-0.10.23.tgz
395e9fe9e32874a24febffa17adacd7e1e387e63  pkgsrc/nodejs-x64-0.10.23.tgz
56892aadf1c9d2d2bc637ee87bd08775a139b252  x64/node-v0.10.23-x64.msi
663d9dd7face6399f5c0b7d6082ec2d5b4acc2c3  x64/node.exe
601b564b73df1f4a871ed55e2e2c9aee5b28f04d  x64/node.exp
523e3f96f45132d2e5e2eb39a1dbd0c5bf6b8822  x64/node.lib
2624cddcbd23c84d947af2bf2b91b1e0b64e3602  x64/node.pdb

Tue, 03 Dec 2013 22:13:57 UTC

As of this past weekend, Ben Noordhuis has decided to step away from Node.js and libuv, and is no longer acting as a core committer.

Ben has done a tremendous amount of great work in the past. We're sad to lose the benefit of his continued hard work and expertise, and extremely grateful for what he has added to Node.js and libuv over the years.

Many of you already have expressed your opinion regarding recent drama, and I'd like to ask that you please respect our wishes to let this issue rest, so that we can all focus on the road forward.


Tue, 26 Nov 2013 15:14:59 UTC - Charlie Robbins - npm

We know the availability and overall health of The npm Registry is paramount to everyone using Node.js as well as the larger JavaScript community and those of your using it for some awesome projects and ideas. Between November 4th and November 15th 2013 The npm Registry had several hours of downtime over three distinct time periods:

  1. November 4th -- 16:30 to 15:00 UTC
  2. November 13th -- 15:00 to 19:30 UTC
  3. November 15th -- 15:30 to 18:00 UTC

The root cause of these downtime was insufficient resources: both hardware and human. This is a full post-mortem where we will be look at how works, what went wrong, how we changed the previous architecture of The npm Registry to fix it, as well next steps we are taking to prevent this from happening again.

All of the next steps require additional expenditure from Nodejitsu: both servers and labor. This is why along with this post-mortem we are announcing our crowdfunding campaign:! Our goal is to raise enough funds so that Nodejitsu can continue to run The npm Registry as a free service for you, the community.

Please take a minute now to donate at!

How does work?

There are two distinct components that make up operated by different people:

  • The main CouchApp (Github: isaacs/ that stores both package tarballs and metadata. It is operated by Nodejitsu since we acquired IrisCouch in May. The primary system administrator is Jason Smith, the current CTO at Nodejitsu, cofounder of IrisCouch, and the System Administrator of since 2011.
  • The npmjs website that you interact with using a web browser. It is a Node.js program (Github: isaacs/npm-www) maintained and operated by Isaac and running on a Joyent Public Cloud SmartMachine.

Here is a high-level summary of the old architecture:

old npm architecture

Diagram 1. Old npm architecture

What went wrong and how was it fixed?

As illustrated above, before November 13th, 2013, npm operated as a single CouchDB server with regular daily backups. We briefly ran a multi-master CouchDB setup after downtime back in August, but after reports that npm login no longer worked correctly we rolled back to a single CouchDB server. On both November 13th and November 15th CouchDB became unresponsive on requests to the /registry database while requests to all other databases (e.g. /public_users) remained responsive. Although the root cause of the CouchDB failures have yet to be determined given that only requests to /registry were slow and/or timed out we suspect it is related to the massive number of attachments stored in the registry.

The incident on November 4th was ultimately resolved by a reboot and resize of the host machine, but when the same symptoms reoccured less than 10 days later additional steps were taken:

  1. The registry was moved to another machine of equal resources to exclude the possibility of a hardware issue.
  2. The registry database itself was compacted.

When neither of these yielded a solution Jason Smith and I decided to move to a multi-master architecture with continuous replication illustrated below:

current npm architecture

Diagram 2. Current npm architecture -- Red-lines denote continuous replication

This should have been the end of our story but unfortunately our supervision logic did not function properly to restart the secondary master on the morning of November 15th. During this time we moved briefly back to a single master architecture. Since then the secondary master has been closely monitored by the entire Nodejitsu operations team to ensure it's continued stability.

What is being done to prevent future incidents?

The public npm registry simply cannot go down. Ever. We gained a lot of operational knowledge about The npm Registry and about CouchDB as a result of these outages. This new knowledge has made clear several steps that we need to take to prevent future downtime:

  1. Always be in multi-master: The multi-master CouchDB architecture we have setup will scale to more than just two CouchDB servers. As npm grows we'll be able to add additional capacity!
  2. Decouple and Right now still depends directly on We are planning to add an additional replica to the current npm architecture so that Isaac can more easily service requests to That means it won't go down if the registry goes down.
  3. Always have a spare replica: We need have a hot spare replica running continuous replication from either to swap out when necessary. This is also important as we need to regularly run compaction on each master since the registry is growing ~10GB per week on disk.
  4. Move attachments out of CouchDB: Work has begun to move the package tarballs out of CouchDB and into Joyent's Manta service. Additionally, MaxCDN has generously offered to provide CDN services for npm, once the tarballs are moved out of the registry database. This will help improve delivery speed, while dramatically reducing the file system I/O load on the CouchDB servers. Work is progressing slowly, because at each stage in the plan, we are making sure that current replication users are minimally impacted.

When these new infrastructure components are in-place The npm Registry will look like this:

planned npm architecture

Diagram 3. Planned npm architecture -- Red-lines denote continuous replication

You are npm! And we need your help!

The npm Registry has had a 10x year. In November 2012 there were 13.5 million downloads. In October 2013 there were 114.6 million package downloads. We're honored to have been a part of sustaining this growth for the community and we want to see it continue to grow to a billion package downloads a month and beyond.

But we need your help! All of these necessary improvements require more servers, more time from Nodejitsu staff and an overall increase to what we spend maintaining the public npm registry as a free service for the Node.js community.

Please take a minute now to donate at!

Thu, 21 Nov 2013 00:40:35 UTC - release

2013.11.20, Version 0.11.9 (Unstable)

  • uv: upgrade to v0.11.15 (Timothy J Fontaine)

  • v8: upgrade to (Timothy J Fontaine)

  • buffer: remove warning when no encoding is passed (Trevor Norris)

  • build: make v8 use random seed for hash tables (Ben Noordhuis)

  • crypto: build with shared openssl without NPN (Ben Noordhuis)

  • crypto: update root certificates (Ben Noordhuis)

  • debugger: pass on v8 debug switches (Ben Noordhuis)

  • domain: use AsyncListener API (Trevor Norris)

  • fs: add recursive subdirectory support to (Nick Simmons)

  • fs: make non-recursive by default (Ben Noordhuis)

  • http: cleanup freeSockets when socket destroyed (fengmk2)

  • http: force socket encoding to be null (isaacs)

  • http: make DELETE requests set req.method (Nathan Rajlich)

  • node: add AsyncListener support (Trevor Norris)

  • src: remove global HandleScope that hid memory leaks (Ben Noordhuis)

  • tls: add ECDH ciphers support (Erik Dubbelboer)

  • tls: do not default to 'localhost' servername (Fedor Indutny)

  • tls: more accurate wrapping of connecting socket (Fedor Indutny)

Source Code:

Macintosh Installer (Universal):

Windows Installer:

Windows x64 Installer:

Windows x64 Files:

Linux 32-bit Binary:

Linux 64-bit Binary:

Solaris 32-bit Binary:

Solaris 64-bit Binary:

Other release files:




3a1af0d716042d617e51a82b43b2f97542f6c03a  node-v0.11.9-darwin-x64.tar.gz
580696c5b2f30c8394cdee265c4888ad67e03b89  node-v0.11.9-darwin-x86.tar.gz
585df0690254afc22b29d7dc5f12fcb50f1bb588  node-v0.11.9-linux-x64.tar.gz
16fb7e69b90b6b6ac84a9120202918f197d4c0c0  node-v0.11.9-linux-x86.tar.gz
bff51e2ab3752f4ae338adca14c2c453294e6017  node-v0.11.9-sunos-x64.tar.gz
9a7ada5c862174d6ce4b524d5816e26a36b763a8  node-v0.11.9-sunos-x86.tar.gz
3a4de2ae0dd8268592546b4fdcbd78f1cbc68118  node-v0.11.9-x86.msi
8c70de5cd39ecd33e6c02d4b0f6ca4010d21372e  node-v0.11.9.pkg
b4fc0e38ccde4edae45db198f331499055d77ca2  node-v0.11.9.tar.gz
9a4b04f0d40251696fac9161567e97c228d4e57d  node.exe
96bfa67a417599c96818461d6d27f50401a74a36  node.exp
5f56ef7c2204ea75916876f6ab9e641b312dff11  node.lib
2db6eb844b36d96a0e34370ad1d311a57facd3d6  node.pdb
4a3590db0e6131739661628632ae1b8d70e2247b  pkgsrc/nodejs-ia32-0.11.9.tgz
3ce0291cf0972ac5a2c0543fd1672d8b20569891  pkgsrc/nodejs-x64-0.11.9.tgz
9b736ec896e6b1b5856730869471c7e736f6ce78  x64/node-v0.11.9-x64.msi
1ec3593262b6e281457748ff3f3f195cd682592d  x64/node.exe
1cf9ba6d503d5f8b18bfc2c1554bce04eba8a536  x64/node.exp
0a3e79ceecd05add6dab97bb6d9f460a61adddbc  x64/node.lib
2037b32bbcb14e24d10c6cb2abe128bc9a85a932  x64/node.pdb

← Page 2

Page 4 →