Thu, 23 Jan 2014 19:43:30 UTC - release

2014.01.23, Version 0.10.25 (Stable)

  • uv: Upgrade to v0.10.23

  • npm: Upgrade to v1.3.24

  • v8: Fix enumeration for objects with lots of properties

  • child_process: fix spawn() optional arguments (Sam Roberts)

  • cluster: report more errors to workers (Fedor Indutny)

  • domains: exit() only affects active domains (Ryan Graham)

  • src: OnFatalError handler must abort() (Timothy J Fontaine)

  • stream: writes may return false but forget to emit drain (Yang Tianyang)

Source Code: http://nodejs.org/dist/v0.10.25/node-v0.10.25.tar.gz

Macintosh Installer (Universal): http://nodejs.org/dist/v0.10.25/node-v0.10.25.pkg

Windows Installer: http://nodejs.org/dist/v0.10.25/node-v0.10.25-x86.msi

Windows x64 Installer: http://nodejs.org/dist/v0.10.25/x64/node-v0.10.25-x64.msi

Windows x64 Files: http://nodejs.org/dist/v0.10.25/x64/

Linux 32-bit Binary: http://nodejs.org/dist/v0.10.25/node-v0.10.25-linux-x86.tar.gz

Linux 64-bit Binary: http://nodejs.org/dist/v0.10.25/node-v0.10.25-linux-x64.tar.gz

Solaris 32-bit Binary: http://nodejs.org/dist/v0.10.25/node-v0.10.25-sunos-x86.tar.gz

Solaris 64-bit Binary: http://nodejs.org/dist/v0.10.25/node-v0.10.25-sunos-x64.tar.gz

Other release files: http://nodejs.org/dist/v0.10.25/

Website: http://nodejs.org/docs/v0.10.25/

Documentation: http://nodejs.org/docs/v0.10.25/api/

Shasums:

b347508376ceef724b464e6009ec2daead7ea572  node-v0.10.25-darwin-x64.tar.gz
f7b3c7a36b45a83360bcd9e541e64bf18ef29272  node-v0.10.25-darwin-x86.tar.gz
7c75e7e13561be1222bddd438a84a8f228fe1bc3  node-v0.10.25-linux-x64.tar.gz
16a2c861de5b27ef907dc18253fcd4f33d506662  node-v0.10.25-linux-x86.tar.gz
05bdc1cd7933ccfa95c2f1f058ff0125eacbdc2d  node-v0.10.25-sunos-x64.tar.gz
250a48c9a2b6c6a8a6feebb0d7d33f96bf8d82f4  node-v0.10.25-sunos-x86.tar.gz
ce78cc8b49e339f71888f627c4e985dda0a83e27  node-v0.10.25-x86.msi
abab975e86250b51a7434d229d13b30acdf4e82e  node-v0.10.25.pkg
1e330b4fbb6f7bb858a0b37d8573dd4956f40885  node-v0.10.25.tar.gz
e3779ed14a68dc6f711ead628fe11a127d09547c  node.exe
35521b6142d39fa371aba7d1fda87a1836db78e4  node.exp
35eb46e5d04fdb1c1417876d1712b85eea6be03c  node.lib
cc749498572b4cf4b277225404beefdd75a4e903  node.pdb
9bf1bf3a59a3f0dc0fd32f9504e8011e5b4ebc42  pkgsrc/nodejs-ia32-0.10.25.tgz
f4a6e7d561c321b917c1b6a021fe38cd330a374e  pkgsrc/nodejs-x64-0.10.25.tgz
aab984860cc02e1d27a0932c4c8d34e5e3551ebf  x64/node-v0.10.25-x64.msi
d2f884d75d5f30693f62625787f27fb2a8824178  x64/node.exe
75cdbe43984c9a9f6c5f1e5875fa7422c97b2d62  x64/node.exp
108c2d9dd6ecf7cad83c4cb5cd62303f51c5570a  x64/node.lib
a7c37dadc994c281d08f6a55bfbd01ecf738fe66  x64/node.pdb

Thu, 16 Jan 2014 23:00:00 UTC - Timothy J Fontaine

As the new project lead for Node.js I am excited for our future, and want to give you an update on where we are.

One of Node's major goals is to provide a small core, one that provides the right amount of surface area for consumers to achieve and innovate, without Node itself getting in the way. That ethos is alive and well, we're going to continue to provide a small, simple, and stable set of APIs that facilitate the amazing uses the community finds for Node. We're going to keep providing backward compatible APIs, so code you write today will continue to work on future versions of Node. And of course, performance tuning and bug fixing will always be an important part of every release cycle.

The release of Node v0.12 is imminent, and a lot of significant work has gone into this release. There's streams3, a better keep alive agent for http, the vm module is now based on contextify, and significant performance work done in core features (Buffers, TLS, streams). We have a few APIs that are still being ironed out before we can feature freeze and branch (execSync, AsyncListeners, user definable instrumentation). We are definitely in the home stretch.

But Node is far from done. In the short term there will be new releases of v8 that we'll need to track, as well as integrating the new ABI stable C module interface. There are interesting language features that we can use to extend Node APIs (extend not replace). We need to write more tooling, we need to expose more interfaces to further enable innovation. We can explore functionality to embed Node in your existing project.

The list can go on and on. Yet, Node is larger than the software itself. Node is also the community, the businesses, the ecosystems, and their related events. With that in mind there are things we can work to improve.

The core team will be improving its procedures such that we can quickly and efficiently communicate with you. We want to provide high quality and timely responses to issues, describe our development roadmap, as well as provide our progress during each release cycle. We know you're interested in our plans for Node, and it's important we're able to provide that information. Communication should be bidirectional: we want to continue to receive feedback about how you're using Node, and what your pain points are.

After the release of v0.12 we will facilitate the community to contribute and curate content for nodejs.org. Allowing the community to continue to invest in Node will ensure nodejs.org is an excellent starting point and the primary resource for tutorials, documentation, and materials regarding Node. We have an awesome and engaged community, and they're paramount to our success.

I'm excited for Node's future, to see new and interesting use cases, and to continue to help businesses scale and innovate with Node. We have a lot we can accomplish together, and I look forward to seeing those results.

Wed, 15 Jan 2014 17:00:00 UTC - Isaac Z. Schlueter

Node's growth has continued and accelerated immensely over the last few years. More people are developing and sharing more code with Node and npm than I would have ever imagined. Countless companies are using Node, and npm along with it.

Over the last year, TJ Fontaine has become absolutely essential to the Node.js project. He's been building releases, managing the test bots, fixing nasty bugs and making decisions for the project with constant focus on the needs of our users. He was responsible for an update to MDB to support running ::findjsobjects on Linux core dumps, and is working on a shim layer that will provide a stable C interface for Node binary addons. In partnership with Joyent and The Node Firm, he's helped to create a path forward for scalable issue triaging. He's become the primary point of contact keeping us all driving the project forward together.

Anyone who's been close to the core project knows that he's been effectively leading the project for a while now, so we're making it official. Effective immediately, TJ Fontaine is the Node.js project lead. I will remain a Node core committer, and expect to continue to contribute to the project in that role. My primary focus, however, will be npm.

At this point, npm needs work, and I am eager to deliver what the Node community needs from its package manager. I am starting a company, npm, Inc., to deliver new products and services related to npm. I'll be sharing many more details soon about exactly how this is going to work, and what we'll be offering. For now, suffice it to say that everything currently free will remain free, and everything currently flaky will get less flaky. Pursuing new revenue is how we can keep providing the npm registry service in a long-term sustainable way, and it has to be done very carefully so that we don't damage what we've all built together.

npm is what I'm most passionate about, and I am now in a position to give it my full attention. I've done more than I could have hoped to accomplish in running Node core, and it's well past time to hand the control of the project off to its next gatekeeper.

TJ is exactly the leader who can help us take Node.js to 1.0 and beyond. He brings professionalism, rigor, and a continued focus on inclusive community values and culture. In the coming days, TJ will spell out his plans in greater detail. I look forward to the places that Node will go with his guidance.

Please join me in welcoming him to this new role :)

Wed, 01 Jan 2014 00:20:57 UTC - release

2013.12.31, Version 0.11.10 (Unstable)

  • http_parser: update to 2.2

  • uv: Upgrade to v0.11.17

  • v8: Upgrade to 3.22.24.10

  • buffer: optimize writeInt* methods (Paul Loyd)

  • child_process: better error handling (Alexis Campailla)

  • cluster: do not synchronously emit 'setup' event (Sam Roberts)

  • cluster: restore backwards compatibility and various fixes (Sam Roberts)

  • crypto: remove unnecessary OpenSSL_add_all_digests (Yorkie)

  • crypto: support GCM authenticated encryption mode. (Ingmar Runge)

  • dns: add resolveSoa and 'SOA' rrtype (Tu─črul Topuz)

  • events: move EE c'tor guts to EventEmitter.init (Bert Belder)

  • http: DELETE shouldn't default to chunked encoding (Lalit Kapoor)

  • http: parse the status message in a http response. (Cam Swords)

  • node: fix removing AsyncListener in callback (Vladimir Kurchatkin)

  • node: follow specification, zero-fill ArrayBuffers (Trevor Norris)

  • openssl: use ASM optimized routines (Fedor Indutny)

  • process: allow nextTick infinite recursion (Trevor Norris)

  • querystring: remove name from stringify() (Yorkie)

  • timers: setImmediate v8 optimization fix (pflannery)

  • tls: add serialNumber to getPeerCertificate() (Ben Noordhuis)

  • tls: reintroduce socket.encrypted (Fedor Indutny)

  • tls: fix handling of asterisk in SNI context (Fedor Indutny)

  • util: Format negative zero as '-0' (David Chan)

  • vm: fix race condition in timeout (Alexis Campailla)

  • windows: fix dns lookup of localhost with ipv6 (Alexis Campailla)

Source Code: http://nodejs.org/dist/v0.11.10/node-v0.11.10.tar.gz

Macintosh Installer (Universal): http://nodejs.org/dist/v0.11.10/node-v0.11.10.pkg

Windows Installer: http://nodejs.org/dist/v0.11.10/node-v0.11.10-x86.msi

Windows x64 Installer: http://nodejs.org/dist/v0.11.10/x64/node-v0.11.10-x64.msi

Windows x64 Files: http://nodejs.org/dist/v0.11.10/x64/

Linux 32-bit Binary: http://nodejs.org/dist/v0.11.10/node-v0.11.10-linux-x86.tar.gz

Linux 64-bit Binary: http://nodejs.org/dist/v0.11.10/node-v0.11.10-linux-x64.tar.gz

Solaris 32-bit Binary: http://nodejs.org/dist/v0.11.10/node-v0.11.10-sunos-x86.tar.gz

Solaris 64-bit Binary: http://nodejs.org/dist/v0.11.10/node-v0.11.10-sunos-x64.tar.gz

Other release files: http://nodejs.org/dist/v0.11.10/

Website: http://nodejs.org/docs/v0.11.10/

Documentation: http://nodejs.org/docs/v0.11.10/api/

Shasums:

4f7d0d43c1ee7593035ddb3cf09020a18a03c794  node-v0.11.10-darwin-x64.tar.gz
3b7100bcff39e39b6db5118805fcfc76d8524da2  node-v0.11.10-darwin-x86.tar.gz
3df4cb183a78bb975c831155d3c0aa29a274dec4  node-v0.11.10-linux-x64.tar.gz
12fc680b0a26cc73b4df0a0e9544b0db2bc06e96  node-v0.11.10-linux-x86.tar.gz
145417c8d801174a42255dc273da962cde94ffc9  node-v0.11.10-sunos-x64.tar.gz
981baba494e9be8978fa1bb336b3048367e809ce  node-v0.11.10-sunos-x86.tar.gz
5f4d96c37cfb1423cc844f52e0547cb5bca99dd8  node-v0.11.10-x86.msi
8bd455fb7539609a7ee6bed87875a908fd6221ea  node-v0.11.10.pkg
b860f511e4fc657a64594fc9f3f1225c1a140e5e  node-v0.11.10.tar.gz
80976bffed871310a86d31694e2767ccbe9f6c35  node.exe
f11675958a492a83f057f356dd224ad507e82c61  node.exp
5a80c4ab5b1d0984b3a118536ca6421b4b9bc14f  node.lib
207daafc40fba36200504fa52869b9c41cdbf5c9  node.pdb
3aa165e2d235888037f8099abd5bc9dca4b12100  pkgsrc/nodejs-ia32-0.11.10.tgz
1d5ef599b93c7d8c0d34ff2ab3dd4255babfaf72  pkgsrc/nodejs-x64-0.11.10.tgz
a6b16441721c34bae732b2b14134d0e1fd9706de  x64/node-v0.11.10-x64.msi
933ff8a0a42c6e69fcbd51b9eaae4e4d14f043ae  x64/node.exe
31c9abd54e5ba431f0645fa04d315f15dc010107  x64/node.exp
66bec5eae9033972463a6bd89183aa97bb84bfd1  x64/node.lib
43fbac8665dfcd121e547f56b1434a1c6039091d  x64/node.pdb

← Page 4

Page 6 →