84 doc/blog/Uncategorized/ldapjs-a-reprise-of-ldap.md
View file
@@ -0,0 +1,84 @@
title: ldapjs: A reprise of LDAP
author: mcavage
date: Thu Sep 08 2011 14:25:43 GMT-0700 (PDT)
status: publish
category: Uncategorized
slug: ldapjs-a-reprise-of-ldap

This post has been about 10 years in the making. My first job out of college was at IBM working on the <a title="Tivoli Directory Server" href="http://www-01.ibm.com/software/tivoli/products/directory-server/">Tivoli Directory Server</a>, and at the time I had a preconceived notion that working on anything related to Internet RFCs was about as hot as you could get. I spent a lot of time back then getting "down and dirty" with everything about LDAP: the protocol, performance, storage engines, indexing and querying, caching, customer use cases and patterns, general network server patterns, etc. Basically, I soaked up as much as I possibly could while I was there. On top of that, I listened to all the "gray beards" tell me about the history of LDAP, which was a bizarre marriage of telecommunications conglomerates and graduate students. The point of this blog post is to give you a crash course in LDAP, and explain what makes <a title="ldapjs" href="http://ldapjs.org">ldapjs</a> different. Allow me to be the gray beard for a bit...
<h2>What is LDAP and where did it come from?</h2>

Directory services were largely pioneered by the telecommunications companies (e.g., AT&amp;T) to allow fast information retrieval of all the crap you'd expect would be in a telephone book and directory. That is, given a name, or an address, or an area code, or a number, or a foo support looking up customer records, billing information, routing information, etc. The efforts of several telcos came to exist in the <a title="X.500" href="http://en.wikipedia.org/wiki/X.500">X.500</a> standard(s). An X.500 directory is one of the most complicated beasts you can possibly imagine, but on a high note, there's
probably not a thing you can imagine in a directory service that wasn't thought of in there. It is literally the kitchen sink. Oh, and it doesn't run over IP (it's <em>actually</em> on the <a title="OSI Model" href="http://en.wikipedia.org/wiki/OSI_model">OSI</a> model).

Several years after X.500 had been deployed (at telcos, academic institutions, etc.), it became clear that the Internet was "for real." <a title="LDAP" href="http://en.wikipedia.org/wiki/Lightweight_Directory_Access_Protocol">LDAP</a>, the "Lightweight Directory Access Protocol," was invented to act purely as an IP-accessible gateway to an X.500 directory.

At some point in the early 90's, a <a title="Tim Howes" href="http://en.wikipedia.org/wiki/Tim_Howes">graduate student</a> at the University of Michigan (with some help) cooked up the "grandfather" implementation of the LDAP protocol, which wasn't actually a "gateway," but rather a stand-alone implementation of LDAP. Said implementation, like many things at the time, was a process-per-connection concurrency model, and had "backends" (aka storage engine) for the file system and the Unix DB API. At some point the <a title="Berkeley Database" href="http://www.oracle.com/technetwork/database/berkeleydb/index.html">Berkeley Database </a>(BDB) was put in, and still remains the de facto storage engine for most LDAP directories.

Ok, so some a graduate student at UM wrote an LDAP server that wasn't a gateway. So what? Well, that UM code base turns out to be the thing that pretty much every vendor did a source license for. Those graduate students went off to Netscape later in the 90's, and largely dominated the market of LDAP middleware until <a title="Active Directory" href="http://en.wikipedia.org/wiki/Active_Directory">Active Directory</a> came along many years later (as far as I know, Active Directory is "from scratch", since while it's "almost" LDAP, it's different in a lot of ways). That Netscape code base was further bought and sold over the years to iPlanet, Sun Microsystems, and Red Hat (I'm probably missing somebody in that chain). It now lives in the Fedora umbrella as '<a title="389 Directory Server" href="http://directory.fedoraproject.org/">389 Directory Server</a>.' Probably the most popular fork of that code base now is <a title="OpenLDAP" href="http://www.openldap.org/">OpenLDAP</a>.

IBM did the same thing, and the Directory Server I worked on was a fork of the UM code too, but it heavily diverged from the Netscape branches. The divergence was primarily due to: (1) backing to DB2 as opposed to BDB, and (2) needing to run on IBM's big iron like OS/400 and Z series mainframes.

Macro point is that there have actually been very few "fresh" implementations of LDAP, and it gets a pretty bad reputation because at the end of the day you've got 20 years of "bolt-ons" to grad student code. Oh, and it was born out of ginormous telcos, so of course the protocol is overly complex.

That said, while there certainly is some wacky stuff in the LDAP protocol itself, it really suffered from poor and buggy implementations more than the fact that LDAP itself was fundamentally flawed. As <a title="Engine Yard LDAP" href="http://www.engineyard.com/blog/2009/ldap-directories-the-forgotten-nosql/">engine yard pointed out a few years back</a>, you can think of LDAP as the original NoSQL store.
<h2>LDAP: The Good Parts</h2>

So what's awesome about LDAP? Since it's a directory system it maintains a hierarchy of your data, which as an information management pattern aligns
with _a lot_ of use case (the quintessential example is white pages for people in your company, but subscriptions to SaaS applications, "host groups"
for tracking machines/instances, physical goods tracking, etc., all have use cases that fit that organization scheme). For example, presumably at your job
you have a "reporting chain." Let's say a given record in LDAP (I'll use myself as a guinea pig here) looks like:
<pre> firstName: Mark
lastName: Cavage
city: Seattle
uid: markc
state: Washington
mail: mcavagegmailcom
phone: (206) 555-1212
title: Software Engineer
department: 123456
objectclass: joyentPerson</pre>
The record for me would live under the tree of engineers I report to (and as an example some other popular engineers under said vice president) would look like:
<pre> uid=david
/
uid=bryan
/ | \
uid=markc uid=ryah uid=isaacs</pre>
Ok, so we've got a tree. It's not tremendously different from your filesystem, but how do we find people? LDAP has a rich search filter syntax that makes a lot of sense for key/value data (far more than tacking Map Reduce jobs on does, imo), and all search queries take a "start point" in the tree. Here's an example: let's say I wanted to find all "Software Engineers" in the entire company, a filter would look like:
<pre>     (title="Software Engineer")</pre>
And I'd just start my search from 'uid=david' in the example above. Let's say I wanted to find all software engineers who worked in Seattle:
<pre>     (&amp;(title="Software Engineer")(city=Seattle))</pre>
I could keep going, but the gist is that LDAP has "full" boolean predicate logic, wildcard filters, etc. It's really rich.

Oh, and on top of the technical merits, better or worse, it's an established standard for both administrators and applications (i.e., most "shipped" intranet software has either a local user repository or the ability to leverage an LDAP server somewhere). So there's a lot of compelling reasons to look at leveraging LDAP.
<h2>ldapjs: Why do I care?</h2>

As I said earlier, I spent a lot of time at IBM observing how customers used LDAP, and the real items I took away from that experience were:
<ul>
<li>LDAP implementations have suffered a lot from never having been designed from the ground up for a large number of concurrent connections with asynchronous operations.</li>
<li>There are use cases for LDAP that just don't always fit the traditional "here's my server and storage engine" model. A lot of simple customer use cases wanted an LDAP access point, but not be forced into taking the heavy backends that came with it (they wanted the original gateway model!). There was an entire "sub" industry for this known as "<a title="Metadirectory" href="http://en.wikipedia.org/wiki/Metadirectory">meta directories</a>" back in the late 90's and early 2000's.</li>
<li>Replication was always a sticking point. LDAP vendors all tried to offer a big multi-master, multi-site replication model. It was a lot of "bolt-on" complexity, done before the <a title="CAP Theorem" href="http://en.wikipedia.org/wiki/CAP_theorem">CAP theorem</a> was written, and certainly before it was accepted as "truth."</li>
<li>Nobody uses all of the protocol. In fact, 20% of the features solve 80% of the use cases (I'm making that number up, but you get the idea).</li>
</ul>

For all the good parts of LDAP, those are really damned big failing points, and even I eventually abandoned LDAP for the greener pastures of NoSQL somewhere
along the way. But it always nagged at me that LDAP didn't get it's due because of a lot of implementation problems (to be clear, if I could, I'd change some
aspects of the protocol itself too, but that's a lot harder).

Well, in the last year, I went to work for <a title="Joyent" href="http://www.joyent.com/">Joyent</a>, and like everyone else, we have several use problems that are classic directory service problems. If you break down the list I outlined above:
<ul>
<li><strong>Connection-oriented and asynchronous:</strong> Holy smokes batman, <a title="node.js" href="http://nodejs.org/">node.js</a> is a completely kick-ass event-driven asynchronous server platform that manages connections like a boss. Check!</li>
<li><strong>Lots of use cases:</strong> Yeah, we've got some. Man, the <a title="sinatra" href="http://www.sinatrarb.com/">sinatra</a>/<a title="express" href="http://expressjs.com/">express</a> paradigm is so easy to slap over anything. How about we just do that and leave as many use cases open as we can. Check!</li>
<li><strong>Replication is hard. CAP is right:</strong> There are a lot of distributed databases out vying to solve exactly this problem. At Joyent we went with <a title="Riak" href="http://www.basho.com/">Riak</a>. Check!</li>
<li><strong>Don't need all of the protocol:</strong> I'm lazy. Let's just skip the stupid things most people don't need. Check!</li>
</ul>

So that's the crux of ldapjs right there. Giving you the ability to put LDAP back into your application while nailing those 4 fundamental problems that plague most existing LDAP deployments.

The obvious question is how it turned out, and the answer is, honestly, better than I thought it would. When I set out to do this, I actually assumed I'd be shipping a much smaller percentage of the RFC than is there. There's actually about 95% of the core RFC implemented. I wasn't sure if the marriage of this protocol to node/JavaScript would work out, but if you've used express ever, this should be _really_ familiar. And I tried to make it as natural as possible to use "pure" JavaScript objects, rather than requiring the developer to understand <a title="ASN.1" href="http://en.wikipedia.org/wiki/Abstract_Syntax_Notation_One">ASN.1</a> (the binary wire protocol) or the<a title="RFC 4510" href="http://tools.ietf.org/html/rfc4510"> LDAP RFC</a> in detail (this one mostly worked out; ldap_modify is still kind of a PITA).

Within 24 hours of releasing ldapjs on <a title="twitter" href="http://twitter.com/#!/mcavage/status/106767571012952064">Twitter</a>, there was an <a title="github ldapjs address book" href="https://gist.github.com/1173999">implementation of an address book</a> that works with Thunderbird/Evolution, by the end of that weekend there was some <a href="http://i.imgur.com/uR16U.png">slick integration with CouchDB</a>, and ldapjs even got used in one of the <a href="http://twitter.com/#!/jheusala/status/108977708649811970">node knockout apps</a>. Off to a pretty good start!

<h2>The Road Ahead</h2>

Hopefully you've been motivated to learn a little bit more about LDAP and try out <a href="http://ldapjs.org">ldapjs</a>. The best place to start is probably the <a title="ldapjs guide" href="http://ldapjs.org/guide.html">guide</a>. After that you'll probably need to pick up a book from <a href="http://www.amazon.com/Understanding-Deploying-LDAP-Directory-Services/dp/0672323168">back in the day</a>. ldapjs itself is still in its infancy; there's quite a bit of room to add some slick client-side logic (e.g., connection pools, automatic reconnects), easy to use schema validation, backends, etc. By the time this post is live, there will be experimental <a href="http://en.wikipedia.org/wiki/DTrace">dtrace</a> support if you're running on Mac OS X or preferably Joyent's <a href="http://smartos.org/">SmartOS</a> (shameless plug). And that nagging percentage of the protocol I didn't do will get filled in over time I suspect. If you've got an interest in any of this, send me some pull requests, but most importantly, I just want to see LDAP not just be a skeleton in the closet and get used in places where you should be using it. So get out there and write you some LDAP.
45 doc/blog/Uncategorized/libuv-status-report.md
View file
@@ -0,0 +1,45 @@
title: libuv status report
author: ryandahl
date: Fri Sep 23 2011 12:45:50 GMT-0700 (PDT)
status: publish
category: Uncategorized
slug: libuv-status-report

We <a href="http://blog.nodejs.org/2011/06/23/porting-node-to-windows-with-microsoft%E2%80%99s-help/">announced</a> back in July that with Microsoft's support Joyent would be porting Node to Windows. This effort is ongoing but I thought it would be nice to make a status report post about the new platform library <code><a href="https://github.com/joyent/libuv">libuv</a></code> which has resulted from porting Node to Windows.

<code>libuv</code>'s purpose is to abstract platform-dependent code in Node into one place where it can be tested for correctness and performance before bindings to V8 are added. Since Node is totally non-blocking, <code>libuv</code> turns out to be a rather useful library itself: a BSD-licensed, minimal, high-performance, cross-platform networking library.

We attempt to not reinvent the wheel where possible. The entire Unix backend sits heavily on Marc Lehmann's beautiful libraries <a href="http://software.schmorp.de/pkg/libev.html">libev</a> and <a href="http://software.schmorp.de/pkg/libeio.html">libeio</a>. For DNS we integrated with Daniel Stenberg's <a href="http://c-ares.haxx.se/">C-Ares</a>. For cross-platform build-system support we're relying on Chrome's <a href="http://code.google.com/p/gyp/">GYP</a> meta-build system.

The current implmented features are:
<ul>
<li>Non-blocking TCP sockets (using IOCP on Windows)</li>
<li>Non-blocking named pipes</li>
<li>UDP</li>
<li>Timers</li>
<li>Child process spawning</li>
<li>Asynchronous DNS via <a href="http://c-ares.haxx.se/">c-ares</a> or <code>uv_getaddrinfo</code>.</li>
<li>Asynchronous file system APIs <code>uv_fs_*</code></li>
<li>High resolution time <code>uv_hrtime</code></li>
<li>Current executable path look up <code>uv_exepath</code></li>
<li>Thread pool scheduling <code>uv_queue_work</code></li>
</ul>
The features we are working on still are
<ul>
<li>File system events (Currently supports inotify, <code>ReadDirectoryChangesW</code> and will support kqueue and event ports in the near future.) <code>uv_fs_event_t</code></li>
<li>VT100 TTY <code>uv_tty_t</code></li>
<li>Socket sharing between processes <code>uv_ipc_t (<a href="https://gist.github.com/1233593">planned API</a>)</code></li>
</ul>
For complete documentation see the header file: <a href="https://github.com/joyent/libuv/blob/03d0c57ea216abd611286ff1e58d4e344a459f76/include/uv.h">include/uv.h</a>. There are a number of tests in <a href="https://github.com/joyent/libuv/tree/3ca382be741ec6ce6a001f0db04d6375af8cd642/test">the test directory</a> which demonstrate the API.

<code>libuv</code> supports Microsoft Windows operating systems since Windows XP SP2. It can be built with either Visual Studio or MinGW. Solaris 121 and later using GCC toolchain. Linux 2.6 or better using the GCC toolchain. Macinotsh Darwin using the GCC or XCode toolchain. It is known to work on the BSDs but we do not check the build regularly.

In addition to Node v0.5, a number of projects have begun to use <code>libuv</code>:
<ul>
<li>Mozilla's <a href="https://github.com/graydon/rust">Rust</a></li>
<li>Tim Caswell's <a href="https://github.com/creationix/luanode">LuaNode</a></li>
<li>Ben Noordhuis and Bert Belder's <a href="https://github.com/bnoordhuis/phode">Phode</a> async PHP project</li>
<li>Kerry Snyder's <a href="https://github.com/kersny/libuv-csharp">libuv-csharp</a></li>
<li>Andrea Lattuada's <a href="https://gist.github.com/1195428">web server</a></li>
</ul>
We hope to see more people contributing and using <code>libuv</code> in the future!
11 doc/blog/Uncategorized/node-meetup-this-thursday.md
View file
@@ -0,0 +1,11 @@
title: Node Meetup this Thursday
author: ryandahl
date: Tue Aug 02 2011 21:37:02 GMT-0700 (PDT)
status: publish
category: Uncategorized
slug: node-meetup-this-thursday

<a href="http://nodejs.org/meetup/" title="http://nodejs.org/meetup/ ">http://nodejs.org/meetup/</a>
<a href="http://nodemeetup.eventbrite.com/">http://nodemeetup.eventbrite.com/</a>

Three companies will describe their distributed Node applications. Sign up soon, space is limited!
12 doc/blog/Uncategorized/node-office-hours-cut-short.md
View file
@@ -0,0 +1,12 @@
title: Node Office Hours Cut Short
author: ryandahl
date: Thu Apr 28 2011 09:04:35 GMT-0700 (PDT)
status: publish
category: Uncategorized
slug: node-office-hours-cut-short

This week office hours are only from 4pm to 6pm. Isaac will be in the Joyent office in SF - everyone else is out of town. Sign up at http://nodeworkup.eventbrite.com/ if you would like to come.

The week after, Thursday May 5th, we will all be at NodeConf in Portland.

Normal office hours resume Thursday May 12th.
12 doc/blog/Uncategorized/office-hours.md
View file
@@ -0,0 +1,12 @@
title: Office Hours
author: ryandahl
date: Wed Mar 23 2011 21:42:47 GMT-0700 (PDT)
status: publish
category: Uncategorized
slug: office-hours

Starting next Thursday Isaac, Tom, and I will be holding weekly office hours at <a href="http://maps.google.com/maps?q=345+California+St,+San+Francisco,+CA+94104&amp;layer=c&amp;sll=37.793040,-122.400491&amp;cbp=13,178.31,,0,-60.77&amp;cbll=37.793131,-122.400484&amp;hl=en&amp;sspn=0.006295,0.006295&amp;ie=UTF8&amp;hq=&amp;hnear=345+California+St,+San+Francisco,+California+94104&amp;ll=37.793131,-122.400484&amp;spn=0.001295,0.003428&amp;z=19&amp;panoid=h0dlz3VG-hMKlzOu0LxMIg">Joyent HQ</a> in San Francisco. Office hours are meant to be subdued working time - there are no talks and no alcohol. Bring your bugs or just come and hack with us.

Our building requires that everyone attending be on a list so you must sign up at <a href="http://nodeworkup01.eventbrite.com/">Event Brite</a>.

We start at 4p and end promptly at 8p.
12 doc/blog/Uncategorized/porting-node-to-windows-with-microsoft%e2%80%99s-help.md
View file
@@ -0,0 +1,12 @@
title: Porting Node to Windows With Microsoft’s Help
author: ryandahl
date: Thu Jun 23 2011 15:22:58 GMT-0700 (PDT)
status: publish
category: Uncategorized
slug: porting-node-to-windows-with-microsoft%e2%80%99s-help

I'm pleased to announce that Microsoft is partnering with Joyent in formally contributing resources towards porting Node to Windows. As you may have heard in <a href="http://nodejs.org/nodeconf.pdf" title="a talk">a talk</a> we gave earlier this year, we have started the undertaking of a native port to Windows - targeting the high-performance IOCP API.

This requires a rather large modification of the core structure, and we're very happy to have official guidance and engineering resources from Microsoft. <a href="https://www.cloudkick.com/">Rackspace</a> is also contributing <a href="https://github.com/piscisaureus">Bert Belder</a>'s time to this undertaking.

The result will be an official binary node.exe releases on nodejs.org, which will work on Windows Azure and other Windows versions as far back as Server 2003.
60 doc/blog/Uncategorized/profiling-node-js.md
View file
@@ -0,0 +1,60 @@
title: Profiling Node.js
author: Dave Pacheco
date: Wed Apr 25 2012 13:48:58 GMT-0700 (PDT)
status: publish
category: Uncategorized
slug: profiling-node-js

It's incredibly easy to visualize where your Node program spends its time using DTrace and <a href="http://github.com/davepacheco/node-stackvis">node-stackvis</a> (a Node port of Brendan Gregg's <a href="http://github.com/brendangregg/FlameGraph/">FlameGraph</a> tool):

<ol>
<li>Run your Node.js program as usual.</li>
<li>In another terminal, run:
<pre>
$ dtrace -o stacks.out -n 'profile-97/execname == "node" &amp;&amp; arg1/{
@[jstack(100, 8000)] = count(); } tick-60s { exit(0); }'</pre>
This will sample about 100 times per second for 60 seconds and emit results to stacks.out. <strong>Note that this will sample all running programs called "node". If you want a specific process, replace <code>execname == "node"</code> with <code>pid == 12345</code> (the process id).</strong>
</li>
<li>Use the "stackvis" tool to transform this directly into a flame graph. First, install it:
<pre>$ npm install -g stackvis</pre>
then use <code>stackvis</code> to convert the DTrace output to a flamegraph:
<pre>$ stackvis dtrace flamegraph-svg &lt; stacks.out &gt; stacks.svg</pre>
</li>
<li>Open stacks.svg in your favorite browser.</li>
</ol>

You'll be looking at something like this:

<a href="http://www.cs.brown.edu/~dap/helloworld.svg"><img src="http://dtrace.org/blogs/dap/files/2012/04/helloworld-flamegraph-550x366.png" alt="" title="helloworld-flamegraph" width="550" height="366" class="aligncenter size-large wp-image-1047" /></a>

This is a visualization of all of the profiled call stacks. This example is from the "hello world" HTTP server on the <a href="http://nodejs.org">Node.js</a> home page under load. Start at the bottom, where you have "main", which is present in most Node stacks because Node spends most on-CPU time in the main thread. Above each row, you have the functions called by the frame beneath it. As you move up, you'll see actual JavaScript function names. The boxes in each row are not in chronological order, but their width indicates how much time was spent there. When you hover over each box, you can see exactly what percentage of time is spent in each function. This lets you see at a glance where your program spends its time.

That's the summary. There are a few prerequisites:

<ul>
<li>You must gather data on a system that supports DTrace with the Node.js ustack helper. For now, this pretty much means <a href="http://illumos.org/">illumos</a>-based systems like <a href="http://smartos.org/">SmartOS</a>, including the Joyent Cloud. <strong>MacOS users:</strong> OS X supports DTrace, but not ustack helpers. The way to get this changed is to contact your Apple developer liason (if you're lucky enough to have one) or <strong>file a bug report at bugreport.apple.com</strong>. I'd suggest referencing existing bugs 5273057 and 11206497. More bugs filed (even if closed as dups) show more interest and make it more likely Apple will choose to fix this.</li>
<li>You must be on 32-bit Node.js 0.6.7 or later, built <code>--with-dtrace</code>. The helper doesn't work with 64-bit Node yet. On illumos (including SmartOS), development releases (the 0.7.x train) include DTrace support by default.</li>
</ul>

There are a few other notes:

<ul>
<li>You can absolutely profile apps <strong>in production</strong>, not just development, since compiling with DTrace support has very minimal overhead. You can start and stop profiling without restarting your program.</li>
<li>You may want to run the stacks.out output through <code>c++filt</code> to demangle C++ symbols. Be sure to use the <code>c++filt</code> that came with the compiler you used to build Node. For example:
<pre>c++filt &lt; stacks.out &gt; demangled.out</pre>
then you can use demangled.out to create the flamegraph.
</li>
<li>If you want, you can filter stacks containing a particular function. The best way to do this is to first collapse the original DTrace output, then grep out what you want:
<pre>
$ stackvis dtrace collapsed &lt; stacks.out | grep SomeFunction &gt; collapsed.out
$ stackvis collapsed flamegraph-svg &lt; collapsed.out &gt; stacks.svg</pre>
</li>
<li>If you've used Brendan's FlameGraph tools, you'll notice the coloring is a little different in the above flamegraph. I ported his tools to Node first so I could incorporate it more easily into other Node programs, but I've also been playing with different coloring options. The current default uses hue to denote stack depth and saturation to indicate time spent. (These are also indicated by position and size.) Other ideas include coloring by module (so V8, JavaScript, libc, etc. show up as different colors.)
</li>
</ul>

For more on the underlying pieces, see my <a href="http://dtrace.org/blogs/dap/2012/01/05/where-does-your-node-program-spend-its-time/">previous post on Node.js profiling</a> and <a href="http://dtrace.org/blogs/brendan/2011/12/16/flame-graphs/">Brendan's post on Flame Graphs</a>.

<hr />

Dave Pacheco blogs at <a href="http://dtrace.org/blogs/dap">dtrace.org</a>
13 doc/blog/Uncategorized/some-new-node-projects.md
View file
@@ -0,0 +1,13 @@
title: Some New Node Projects
author: ryandahl
date: Mon Aug 29 2011 08:30:41 GMT-0700 (PDT)
status: publish
category: Uncategorized
slug: some-new-node-projects

<ul>
<li>Superfeedr released <a href="http://blog.superfeedr.com/node-xmpp-server/">a Node XMPP Server</a>. "<i>Since <a href="http://spaceboyz.net/~astro/">astro</a> had been doing an <strong>amazing work</strong> with his <a href="https://github.com/astro/node-xmpp">node-xmpp</a> library to build <em>Client</em>, <em>Components</em> and even <em>Server to server</em> modules, the logical next step was to try to build a <em>Client to Server</em> module so that we could have a full blown server. That&#8217;s what we worked on the past couple days, and <a href="https://github.com/superfeedr/node-xmpp">it&#8217;s now on Github</a>!</i></li>

<li>Joyent's Mark Cavage released <a href="http://ldapjs.org/">LDAP.js</a>. "<i>ldapjs is a pure JavaScript, from-scratch framework for implementing <a href="http://tools.ietf.org/html/rfc4510">LDAP</a> clients and servers in <a href="http://nodejs.org">Node.js</a>. It is intended for developers used to interacting with HTTP services in node and <a href="http://expressjs.com">express</a>.</i></li>

<li>Microsoft's Tomasz Janczuk released <a href="http://tomasz.janczuk.org/2011/08/hosting-nodejs-applications-in-iis-on.html">iisnode</a> "<i>The <a href="https://github.com/tjanczuk/iisnode">iisnode</a> project provides a native IIS 7.x module that allows hosting of node.js applications in IIS.</i><br /><br />Scott Hanselman posted <a href="http://www.hanselman.com/blog/InstallingAndRunningNodejsApplicationsWithinIISOnWindowsAreYouMad.aspx">a detailed walkthrough</a> of how to get started with iisnode
10 doc/blog/Uncategorized/the-videos-from-node-meetup.md
View file
@@ -0,0 +1,10 @@
title: The Videos from the Meetup
author: ryandahl
date: Fri Aug 12 2011 00:14:34 GMT-0700 (PDT)
status: publish
category: Uncategorized
slug: the-videos-from-node-meetup

Uber, Voxer, and Joyent described how they use Node in production

<a href="http://joyeur.com/2011/08/11/node-js-meetup-distributed-web-architectures/">http://joyeur.com/2011/08/11/node-js-meetup-distributed-web-architectures/</a>
17 doc/blog/Uncategorized/trademark.md
View file
@@ -0,0 +1,17 @@
title: Trademark
author: ryandahl
date: Fri Apr 29 2011 01:54:18 GMT-0700 (PDT)
status: publish
category: Uncategorized
slug: trademark

One of the things Joyent accepted when we took on the Node project was to provide resources to help the community grow. The Node project is amazing because of the expertize, dedication and hard work of the community. However in all communities there is the possibility of people acting inappropriately. We decided to introduce trademarks on the “Node.js” and the “Node logo” in order to ensure that people or organisations who are not investing in the Node community misrepresent, or create confusion about the role of themselves or their products with Node.

We are big fans of the people who have contributed to Node and we have worked hard to make sure that existing members of the community will be unaffected by this change. For most people they don’t have to do anything they are free to use the Node.js marks in their free open source projects (see guidelines). For others we’ve already granted them licenses to use Node.js marks in their domain names and their businesses. We value all of these contributions to the Node community and hope that we can continue to protect their good names and hard work.

Where does our trademark policy come from? We started by looking at popular open source foundations like the Apache Software Foundation and Linux. By strongly basing our policy on the one used by the Apache Software Foundation we feel that we’ve created a policy which is liberal enough to allow the open source community to easily make use of the mark in the context of free open source software, but secure enough to protect the community’s work from being misrepresented by other organisations.

While we realise that any changes involving lawyers can be intimidating to the community we want to make this transition as smoothly as possible and welcome your questions and feedback on the policy and how we are implementing it.

<a href="http://nodejs.org/trademark-policy.pdf">http://nodejs.org/trademark-policy.pdf</a>
trademark@joyent.com
12 doc/blog/Uncategorized/version-0-6.md
View file
@@ -0,0 +1,12 @@
title: Version 0.6 Coming Soon
author: ryandahl
date: Tue Oct 25 2011 15:26:23 GMT-0700 (PDT)
status: publish
category: Uncategorized
slug: version-0-6

Version 0.6.0 will be released next week. Please spend some time this week upgrading your code to v0.5.10. Report any API differences at <a href="https://github.com/joyent/node/wiki/API-changes-between-v0.4-and-v0.6">https://github.com/joyent/node/wiki/API-changes-between-v0.4-and-v0.6</a> or report a bug to us at <a href="http://github.com/joyent/node/issues">http://github.com/joyent/node/issues</a> if you hit problems.

The API changes between v0.4.12 and v0.5.10 are 99% cosmetic, minor, and easy to fix. Most people are able to migrate their code in 10 minutes. Don't fear.

Once you've ported your code to v0.5.10 please help out by testing third party modules. Make bug reports. Encourage authors to publish new versions of their modules. Go through the list of modules at <a href="http://search.npmjs.org/">http://search.npmjs.org/</a> and try out random ones. This is especially encouraged of Windows users!
89 doc/blog/module/multi-server-continuous-deployment-with-fleet.md
View file
@@ -0,0 +1,89 @@
title: multi-server continuous deployment with fleet
author: Isaac Schlueter
date: Wed May 02 2012 11:00:00 GMT-0700 (PDT)
status: publish
category: module
slug: multi-server-continuous-deployment-with-fleet

<p><img style="float:right;margin-left:1.2em;" alt="substack" src="http://substack.net/images/substackistan.png"><i>This is a guest post by James "SubStack" Halliday, originally posted <a href="http://substack.net/posts/16a9d8/multi-server-continuous-deployment-with-fleet">on his blog</a>, and reposted here with permission.</i></p>

<p>Writing applications as a sequence of tiny services that all talk to each other over the network has many upsides, but it can be annoyingly tedious to get all the subsystems up and running. </p>

<p>Running a <a href="http://substack.net/posts/7a1c42">seaport</a> can help with getting all the services to talk to each other, but running the processes is another matter, especially when you have new code to push into production. </p>

<p><a href="http://github.com/substack/fleet">fleet</a> aims to make it really easy for anyone on your team to push new code from git to an armada of servers and manage all the processes in your stack. </p>

<p>To start using fleet, just install the fleet command with <a href="http://npmjs.org">npm</a>: </p>

<pre style="">npm install -g fleet </pre>

<p>Then on one of your servers, start a fleet hub. From a fresh directory, give it a passphrase and a port to listen on: </p>

<pre style="">fleet hub --port=7000 --secret=beepboop </pre>

<p>Now fleet is listening on :7000 for commands and has started a git server on :7001 over http. There's no ssh keys or post commit hooks to configure, just run that command and you're ready to go! </p>

<p>Next set up some worker drones to run your processes. You can have as many workers as you like on a single server but each worker should be run from a separate directory. Just do: </p>

<pre style="">fleet drone --hub=x.x.x.x:7000 --secret=beepboop </pre>

<p>where <span class="code">x.x.x.x</span> is the address where the fleet hub is running. Spin up a few of these drones. </p>

<p>Now navigate to the directory of the app you want to deploy. First set a remote so you don't need to type <span class="code">--hub</span> and <span class="code">--secret</span> all the time. </p>

<pre style="">fleet remote add default --hub=x.x.x.x:7000 --secret=beepboop </pre>

<p>Fleet just created a <span class="code">fleet.json</span> file for you to save your settings. </p>

<p>From the same app directory, to deploy your code just do: </p>

<pre style="">fleet deploy </pre>

<p>The deploy command does a <span class="code">git push</span> to the fleet hub's git http server and then the hub instructs all the drones to pull from it. Your code gets checked out into a new directory on all the fleet drones every time you deploy. </p>

<p>Because fleet is designed specifically for managing applications with lots of tiny services, the deploy command isn't tied to running any processes. Starting processes is up to the programmer but it's super simple. Just use the <span class="code">fleet spawn</span> command: </p>

<pre style="">fleet spawn -- node server.js 8080 </pre>

<p>By default fleet picks a drone at random to run the process on. You can specify which drone you want to run a particular process on with the <span class="code">--drone</span> switch if it matters. </p>

<p>Start a few processes across all your worker drones and then show what is running with the <span class="code">fleet ps</span> command: </p>

<pre style="">fleet ps
drone#3dfe17b8
├─┬ pid#1e99f4
│ ├── status: running
│ ├── commit: webapp/1b8050fcaf8f1b02b9175fcb422644cb67dc8cc5
│ └── command: node server.js 8888
└─┬ pid#d7048a
├── status: running
├── commit: webapp/1b8050fcaf8f1b02b9175fcb422644cb67dc8cc5
└── command: node server.js 8889</pre>

<p>Now suppose that you have new code to push out into production. By default, fleet lets you spin up new services without disturbing your existing services. If you <span class="code">fleet deploy</span> again after checking in some new changes to git, the next time you <span class="code">fleet spawn</span> a new process, that process will be spun up in a completely new directory based on the git commit hash. To stop a process, just use <span class="code">fleet stop</span>. </p>

<p>This approach lets you verify that the new services work before bringing down the old services. You can even start experimenting with heterogeneous and incremental deployment by hooking into a custom <a href="http://substack.net/posts/5bd18d">http proxy</a>! </p>

<p>Even better, if you use a service registry like <a href="http://substack.net/posts/7a1c42">seaport</a> for managing the host/port tables, you can spin up new ad-hoc staging clusters all the time without disrupting the normal operation of your site before rolling out new code to users. </p>

<p>Fleet has many more commands that you can learn about with its git-style manpage-based help system! Just do <span class="code">fleet help</span> to get a list of all the commands you can run. </p>

<pre style="">fleet help
Usage: fleet &lt;command&gt; [&lt;args&gt;]

The commands are:
deploy Push code to drones.
drone Connect to a hub as a worker.
exec Run commands on drones.
hub Create a hub for drones to connect.
monitor Show service events system-wide.
ps List the running processes on the drones.
remote Manage the set of remote hubs.
spawn Run services on drones.
stop Stop processes running on drones.

For help about a command, try `fleet help `.</pre>

<p><span class="code">npm install -g fleet</span> and <a href="https://github.com/substack/fleet">check out the code on github</a>! </p>

<img src="http://substack.net/images/fleet.png" width="849" height="568">
337 doc/blog/module/service-logging-in-json-with-bunyan.md
View file

Large diffs are not rendered by default.

165 doc/blog/npm/managing-node-js-dependencies-with-shrinkwrap.md
View file

Large diffs are not rendered by default.

64 doc/blog/npm/npm-1-0-global-vs-local-installation.md
View file
@@ -0,0 +1,64 @@
title: npm 1.0: Global vs Local installation
author: Isaac Schlueter
date: Wed Mar 23 2011 23:07:13 GMT-0700 (PDT)
status: publish
category: npm
slug: npm-1-0-global-vs-local-installation

<p><i>npm 1.0 is in release candidate mode. <a href="http://groups.google.com/group/npm-/browse_thread/thread/43d3e76d71d1f141">Go get it!</a></i></p>

<p>More than anything else, the driving force behind the npm 1.0 rearchitecture was the desire to simplify what a package installation directory structure looks like.</p>

<p>In npm 0.x, there was a command called <code>bundle</code> that a lot of people liked. <code>bundle</code> let you install your dependencies locally in your project, but even still, it was basically a hack that never really worked very reliably.</p>

<p>Also, there was that activation/deactivation thing. That&#8217;s confusing.</p>

<h2>Two paths</h2>

<p>In npm 1.0, there are two ways to install things:</p>

<ol> <li>globally &#8212;- This drops modules in <code>{prefix}/lib/node_modules</code>, and puts executable files in <code>{prefix}/bin</code>, where <code>{prefix}</code> is usually something like <code>/usr/local</code>. It also installs man pages in <code>{prefix}/share/man</code>, if they&#8217;re supplied.</li> <li>locally &#8212;- This installs your package in the current working directory. Node modules go in <code>./node_modules</code>, executables go in <code>./node_modules/.bin/</code>, and man pages aren&#8217;t installed at all.</li> </ol>

<h2>Which to choose</h2>

<p>Whether to install a package globally or locally depends on the <code>global</code> config, which is aliased to the <code>-g</code> command line switch.</p>

<p>Just like how global variables are kind of gross, but also necessary in some cases, global packages are important, but best avoided if not needed.</p>

<p>In general, the rule of thumb is:</p>

<ol> <li>If you&#8217;re installing something that you want to use <em>in</em> your program, using <code>require('whatever')</code>, then install it locally, at the root of your project.</li> <li>If you&#8217;re installing something that you want to use in your <em>shell</em>, on the command line or something, install it globally, so that its binaries end up in your <code>PATH</code> environment variable.</li> </ol>

<h2>When you can't choose</h2>

<p>Of course, there are some cases where you want to do both. <a href="http://coffeescript.org/">Coffee-script</a> and <a href="http://expressjs.com/">Express</a> both are good examples of apps that have a command line interface, as well as a library. In those cases, you can do one of the following:</p>

<ol> <li>Install it in both places. Seriously, are you that short on disk space? It&#8217;s fine, really. They&#8217;re tiny JavaScript programs.</li> <li>Install it globally, and then <code>npm link coffee-script</code> or <code>npm link express</code> (if you&#8217;re on a platform that supports symbolic links.) Then you only need to update the global copy to update all the symlinks as well.</li> </ol>

<p>The first option is the best in my opinion. Simple, clear, explicit. The second is really handy if you are going to re-use the same library in a bunch of different projects. (More on <code>npm link</code> in a future installment.)</p>

<p>You can probably think of other ways to do it by messing with environment variables. But I don&#8217;t recommend those ways. Go with the grain.</p>

<h2 id="slight_exception_it8217s_not_always_the_cwd">Slight exception: It&#8217;s not always the cwd.</h2>

<p>Let&#8217;s say you do something like this:</p>

<pre style="background:#333!important;color:#ccc!important;overflow:auto!important;padding:2px!important;"><code>cd ~/projects/foo # go into my project
npm install express # ./node_modules/express
cd lib/utils # move around in there
vim some-thing.js # edit some stuff, work work work
npm install redis # ./lib/utils/node_modules/redis!? ew.</code></pre>

<p>In this case, npm will install <code>redis</code> into <code>~/projects/foo/node_modules/redis</code>. Sort of like how git will work anywhere within a git repository, npm will work anywhere within a package, defined by having a <code>node_modules</code> folder.</p>

<h2>Test runners and stuff</h2>

<p>If your package's <code>scripts.test</code> command uses a command-line program installed by one of your dependencies, not to worry. npm makes <code>./node_modules/.bin</code> the first entry in the <code>PATH</code> environment variable when running any lifecycle scripts, so this will work fine, even if your program is not globally installed:

<pre style="background:#333!important;color:#ccc!important;overflow:auto!important;padding:2px!important;"><code>{ "name" : "my-program"
, "version" : "1.2.3"
, "dependencies": { "express": "*", "coffee-script": "*" }
, "devDependencies": { "vows": "*" }
, "scripts":
{ "test": "vows test/*.js"
, "preinstall": "cake build" } }</code></pre>
114 doc/blog/npm/npm-1-0-link.md
View file
@@ -0,0 +1,114 @@
title: npm 1.0: link
author: Isaac Schlueter
date: Wed Apr 06 2011 17:40:33 GMT-0700 (PDT)
status: publish
category: npm
slug: npm-1-0-link

<p><i>npm 1.0 is in release candidate mode. <a href="http://groups.google.com/group/npm-/browse_thread/thread/43d3e76d71d1f141">Go get it!</a></i></p>

<p>In npm 0.x, there was a command called <code>link</code>. With it, you could &#8220;link-install&#8221; a package so that changes would be reflected in real-time. This is especially handy when you&#8217;re actually building something. You could make a few changes, run the command again, and voila, your new code would be run without having to re-install every time.</p>

<p>Of course, compiled modules still have to be rebuilt. That&#8217;s not ideal, but it&#8217;s a problem that will take more powerful magic to solve.</p>

<p>In npm 0.x, this was a pretty awful kludge. Back then, every package existed in some folder like:</p>

<pre><code>prefix/lib/node/.npm/my-package/1.3.6/package
</code></pre>

<p>and the package&#8217;s version and name could be inferred from the path. Then, symbolic links were set up that looked like:</p>

<pre><code>prefix/lib/node/my-package@1.3.6 -&gt; ./.npm/my-package/1.3.6/package
</code></pre>

<p>It was easy enough to point that symlink to a different location. However, since the <em>package.json file could change</em>, that meant that the connection between the version and the folder was not reliable.</p>

<p>At first, this was just sort of something that we dealt with by saying, &#8220;Relink if you change the version.&#8221; However, as more and more edge cases arose, eventually the solution was to give link packages this fakey version of &#8220;9999.0.0-LINK-hash&#8221; so that npm knew it was an imposter. Sometimes the package was treated as if it had the 9999.0.0 version, and other times it was treated as if it had the version specified in the package.json.</p>

<h2 id="a_better_way">A better way</h2>

<p>For npm 1.0, we backed up and looked at what the actual use cases were. Most of the time when you link something you want one of the following:</p>

<ol>
<li>globally install this package I&#8217;m working on so that I can run the command it creates and test its stuff as I work on it.</li>
<li>locally install my thing into some <em>other</em> thing that depends on it, so that the other thing can <code>require()</code> it.</li>
</ol>

<p>And, in both cases, changes should be immediately apparent and not require any re-linking.</p>

<p><em>Also</em>, there&#8217;s a third use case that I didn&#8217;t really appreciate until I started writing more programs that had more dependencies:</p>

<ol start="3"> <li><p>Globally install something, and use it in development in a bunch of projects, and then update them all at once so that they all use the latest version. </ol>

<p>Really, the second case above is a special-case of this third case.</p>

<h2 id="link_devel_global">Link devel &rarr; global</h2>

<p>The first step is to link your local project into the global install space. (See <a href="http://blog.nodejs.org/2011/03/23/npm-1-0-global-vs-local-installation/">global vs local installation</a> for more on this global/local business.)</p>

<p>I do this as I&#8217;m developing node projects (including npm itself).</p>

<pre><code>cd ~/dev/js/node-tap # go into the project dir
npm link # create symlinks into {prefix}
</code></pre>

<p>Because of how I have my computer set up, with <code>/usr/local</code> as my install prefix, I end up with a symlink from <code>/usr/local/lib/node_modules/tap</code> pointing to <code>~/dev/js/node-tap</code>, and the executable linked to <code>/usr/local/bin/tap</code>.</p>

<p>Of course, if you <a href="http://blog.nodejs.org/2011/04/04/development-environment/">set your paths differently</a>, then you&#8217;ll have different results. (That&#8217;s why I tend to talk in terms of <code>prefix</code> rather than <code>/usr/local</code>.)</p>

<h2 id="link_global_local">Link global &rarr; local</h2>

<p>When you want to link the globally-installed package into your local development folder, you run <code>npm link pkg</code> where <code>pkg</code> is the name of the package that you want to install.</p>

<p>For example, let&#8217;s say that I wanted to write some tap tests for my node-glob package. I&#8217;d <em>first</em> do the steps above to link tap into the global install space, and <em>then</em> I&#8217;d do this:</p>

<pre><code>cd ~/dev/js/node-glob # go to the project that uses the thing.
npm link tap # link the global thing into my project.
</code></pre>

<p>Now when I make changes in <code>~/dev/js/node-tap</code>, they&#8217;ll be immediately reflected in <code>~/dev/js/node-glob/node_modules/tap</code>.</p>

<h2 id="link_to_stuff_you_don8217t_build">Link to stuff you <em>don&#8217;t</em> build</h2>

<p>Let&#8217;s say I have 15 sites that all use express. I want the benefits of local development, but I also want to be able to update all my dev folders at once. You can globally install express, and then link it into your local development folder.</p>

<pre><code>npm install express -g # install express globally
cd ~/dev/js/my-blog # development folder one
npm link express # link the global express into ./node_modules
cd ~/dev/js/photo-site # other project folder
npm link express # link express into here, as well

# time passes
# TJ releases some new stuff.
# you want this new stuff.

npm update express -g # update the global install.
# this also updates my project folders.
</code></pre>

<h2 id="caveat_not_for_real_servers">Caveat: Not For Real Servers</h2>

<p>npm link is a development tool. It&#8217;s <em>awesome</em> for managing packages on your local development box. But deploying with npm link is basically asking for problems, since it makes it super easy to update things without realizing it.</p>

<h2 id="caveat_2_sorry_windows">Caveat 2: Sorry, Windows!</h2>

<p>I highly doubt that a native Windows node will ever have comparable symbolic link support to what Unix systems provide. I know that there are junctions and such, and I've heard legends about symbolic links on Windows 7.</p>

<p>When there is a native windows port of Node, if that native windows port has `fs.symlink` and `fs.readlink` support that is exactly identical to the way that they work on Unix, then this should work fine.</p>

<p>But I wouldn't hold my breath. Any bugs about this not working on a native Windows system (ie, not Cygwin) will most likely be closed with <code>wontfix</code>.</p>


<h2 id="aside_credit_where_credit8217s_due">Aside: Credit where Credit&#8217;s Due</h2>

<p>Back before the Great Package Management Wars of Node 0.1, before npm or kiwi or mode or seed.js could do much of anything, and certainly before any of them had more than 2 users, Mikeal Rogers invited me to the Couch.io offices for lunch to talk about this npm registry thingie I&#8217;d mentioned wanting to build. (That is, to convince me to use CouchDB for it.)</p>

<p>Since he was volunteering to build the first version of it, and since couch is pretty much the ideal candidate for this use-case, it was an easy sell.</p>

<p>While I was there, he said, &#8220;Look. You need to be able to link a project directory as if it was installed as a package, and then have it all Just Work. Can you do that?&#8221;</p>

<p>I was like, &#8220;Well, I don&#8217;t know&#8230; I mean, there&#8217;s these edge cases, and it doesn&#8217;t really fit with the existing folder structure very well&#8230;&#8221;</p>

<p>&#8220;Dude. Either you do it, or I&#8217;m going to have to do it, and then there&#8217;ll be <em>another</em> package manager in node, instead of writing a registry for npm, and it won&#8217;t be as good anyway. Don&#8217;t be python.&#8221;</p>

<p>The rest is history.</p>
36 doc/blog/npm/npm-1-0-released.md
View file
@@ -0,0 +1,36 @@
title: npm 1.0: Released
author: Isaac Schlueter
date: Sun May 01 2011 08:09:45 GMT-0700 (PDT)
status: publish
category: npm
slug: npm-1-0-released

<p>npm 1.0 has been released. Here are the highlights:</p>

<ul> <li><a href="http://blog.nodejs.org/2011/03/23/npm-1-0-global-vs-local-installation/">Global vs local installation</a></li> <li><a href="http://blog.nodejs.org/2011/03/17/npm-1-0-the-new-ls/">ls displays a tree</a>, instead of being a remote search</li> <li>No more &#8220;activation&#8221; concept - dependencies are nested</li> <li><a href="http://blog.nodejs.org/2011/04/06/npm-1-0-link/">Updates to link command</a></li> <li>Install script cleans up any 0.x cruft it finds. (That is, it removes old packages, so that they can be installed properly.)</li> <li>Simplified &#8220;search&#8221; command. One line per package, rather than one line per version.</li> <li>Renovated &#8220;completion&#8221; approach</li> <li>More help topics</li> <li>Simplified folder structure</li> </ul>

<p>The focus is on npm being a development tool, rather than an apt-wannabe.</p>

<h2 id="installing_it">Installing it</h2>

<p>To get the new version, run this command:</p>

<pre style="background:#333;color:#ccc;overflow:auto;padding:2px;"><code>curl http://npmjs.org/install.sh | sh </code></pre>

<p>This will prompt to ask you if it&#8217;s ok to remove all the old 0.x cruft. If you want to not be asked, then do this:</p>

<pre style="background:#333;color:#ccc;overflow:auto;padding:2px;"><code>curl http://npmjs.org/install.sh | clean=yes sh </code></pre>

<p>Or, if you want to not do the cleanup, and leave the old stuff behind, then do this:</p>

<pre style="background:#333;color:#ccc;overflow:auto;padding:2px;"><code>curl http://npmjs.org/install.sh | clean=no sh </code></pre>

<p>A lot of people in the node community were brave testers and helped make this release a lot better (and swifter) than it would have otherwise been. Thanks :)</p>

<h2 id="code_freeze">Code Freeze</h2>

<p>npm will not have any major feature enhancements or architectural changes <span style="border-bottom:1px dotted;cursor:default;" title="That is, the freeze ends no sooner than November 1, 2011">for at least 6 months</span>. There are interesting developments planned that leverage npm in some ways, but it&#8217;s time to let the client itself settle. Also, I want to focus attention on some other problems for a little while.</p>

<p>Of course, <a href="https://github.com/isaacs/npm/issues">bug reports</a> are always welcome.</p>

<p>See you at NodeConf!</p>
144 doc/blog/npm/npm-1-0-the-new-ls.md
View file
@@ -0,0 +1,144 @@
title: npm 1.0: The New "ls"
author: Isaac Schlueter
date: Thu Mar 17 2011 23:22:17 GMT-0700 (PDT)
status: publish
category: npm
slug: npm-1-0-the-new-ls

<p><em>This is the first in a series of hopefully more than 1 posts, each detailing some aspect of npm 1.0.</em></p>

<p>In npm 0.x, the <code>ls</code> command was a combination of both searching the registry as well as reporting on what you have installed.</p>

<p>As the registry has grown in size, this has gotten unwieldy. Also, since npm 1.0 manages dependencies differently, nesting them in <code>node_modules</code> folder and installing locally by default, there are different things that you want to view.</p>

<p>The functionality of the <code>ls</code> command was split into two different parts. <code>search</code> is now the way to find things on the registry (and it only reports one line per package, instead of one line per version), and <code>ls</code> shows a tree view of the packages that are installed locally.</p>

<p>Here&#8217;s an example of the output:</p>

<pre style="background:#333;color:#ccc;overflow:auto;padding:2px;"><code>$ npm ls
npm@1.0.0 /Users/isaacs/dev-src/js/npm
├── semver@1.0.1
├─┬ ronn@0.3.5
│ └── opts@1.2.1
└─┬ express@2.0.0rc3 <span style="background:#000;color:#0f0;">extraneous</span>
├─┬ connect@1.1.0
│ ├── qs@0.0.7
│ └── mime@1.2.1
├── mime@1.2.1
└── qs@0.0.7
</code></pre>

<p>This is after I&#8217;ve done <code>npm install semver ronn express</code> in the npm source directory. Since express isn&#8217;t actually a dependency of npm, it shows up with that &#8220;extraneous&#8221; marker.</p>

<p>Let&#8217;s see what happens when we create a broken situation:</p>

<pre style="background:#333;color:#ccc;overflow:auto;padding:2px;"><code>$ rm -rf ./node_modules/express/node_modules/connect
$ npm ls
npm@1.0.0 /Users/isaacs/dev-src/js/npm
├── semver@1.0.1
├─┬ ronn@0.3.5
│ └── opts@1.2.1
└─┬ express@2.0.0rc3 <span style="background:#000;color:#0f0;">extraneous</span>
├── <span style="background:#000;color:#f00;">UNMET DEPENDENCY</span> connect &gt;= 1.1.0 &lt; 2.0.0
├── mime@1.2.1
└── qs@0.0.7
</code></pre>

<p>Tree views are great for human readability, but some times you want to pipe that stuff to another program. For that output, I took the same datastructure, but instead of building up a treeview string for each line, it spits out just the folders like this:</p>

<pre style="background:#333;color:#ccc;overflow:auto;padding:2px;"><code>$ npm ls -p
/Users/isaacs/dev-src/js/npm
/Users/isaacs/dev-src/js/npm/node_modules/semver
/Users/isaacs/dev-src/js/npm/node_modules/ronn
/Users/isaacs/dev-src/js/npm/node_modules/ronn/node_modules/opts
/Users/isaacs/dev-src/js/npm/node_modules/express
/Users/isaacs/dev-src/js/npm/node_modules/express/node_modules/connect
/Users/isaacs/dev-src/js/npm/node_modules/express/node_modules/connect/node_modules/qs
/Users/isaacs/dev-src/js/npm/node_modules/express/node_modules/connect/node_modules/mime
/Users/isaacs/dev-src/js/npm/node_modules/express/node_modules/mime
/Users/isaacs/dev-src/js/npm/node_modules/express/node_modules/qs
</code></pre>

<p>Since you sometimes want a bigger view, I added the <code>--long</code> option to (shorthand: <code>-l</code>) to spit out more info:</p>

<pre style="background:#333;color:#ccc;overflow:auto;padding:2px;"><code>$ npm ls -l
npm@1.0.0
│ /Users/isaacs/dev-src/js/npm
│ A package manager for node
│ git://github.com/isaacs/npm.git
│ http://npmjs.org/
├── semver@1.0.1
│ ./node_modules/semver
│ The semantic version parser used by npm.
│ git://github.com/isaacs/node-semver.git
├─┬ ronn@0.3.5
│ │ ./node_modules/ronn
│ │ markdown to roff and html converter
│ └── opts@1.2.1
│ ./node_modules/ronn/node_modules/opts
│ Command line argument parser written in the style of commonjs. To be used with node.js
└─┬ express@2.0.0rc3 <span style="background:#000;color:#0f0;">extraneous</span>
│ ./node_modules/express
│ Sinatra inspired web development framework
├─┬ connect@1.1.0
│ │ ./node_modules/express/node_modules/connect
│ │ High performance middleware framework
│ │ git://github.com/senchalabs/connect.git
│ ├── qs@0.0.7
│ │ ./node_modules/express/node_modules/connect/node_modules/qs
│ │ querystring parser
│ └── mime@1.2.1
│ ./node_modules/express/node_modules/connect/node_modules/mime
│ A comprehensive library for mime-type mapping
├── mime@1.2.1
│ ./node_modules/express/node_modules/mime
│ A comprehensive library for mime-type mapping
└── qs@0.0.7
./node_modules/express/node_modules/qs
querystring parser

$ npm ls -lp
/Users/isaacs/dev-src/js/npm:npm@1.0.0::::
/Users/isaacs/dev-src/js/npm/node_modules/semver:semver@1.0.1::::
/Users/isaacs/dev-src/js/npm/node_modules/ronn:ronn@0.3.5::::
/Users/isaacs/dev-src/js/npm/node_modules/ronn/node_modules/opts:opts@1.2.1::::
/Users/isaacs/dev-src/js/npm/node_modules/express:express@2.0.0rc3:EXTRANEOUS:::
/Users/isaacs/dev-src/js/npm/node_modules/express/node_modules/connect:connect@1.1.0::::
/Users/isaacs/dev-src/js/npm/node_modules/express/node_modules/connect/node_modules/qs:qs@0.0.7::::
/Users/isaacs/dev-src/js/npm/node_modules/express/node_modules/connect/node_modules/mime:mime@1.2.1::::
/Users/isaacs/dev-src/js/npm/node_modules/express/node_modules/mime:mime@1.2.1::::
/Users/isaacs/dev-src/js/npm/node_modules/express/node_modules/qs:qs@0.0.7::::
</code></pre>

<p>And, if you want to get at the globally-installed modules, you can use ls with the global flag:</p>

<pre style="background:#333;color:#ccc;overflow:auto;padding:2px;"><code>$ npm ls -g
/usr/local
├─┬ A@1.2.3 -&gt; /Users/isaacs/dev-src/js/A
│ ├── B@1.2.3 -&gt; /Users/isaacs/dev-src/js/B
│ └─┬ npm@0.3.15
│ └── semver@1.0.1
├─┬ B@1.2.3 -&gt; /Users/isaacs/dev-src/js/B
│ └── A@1.2.3 -&gt; /Users/isaacs/dev-src/js/A
├── glob@2.0.5
├─┬ npm@1.0.0 -&gt; /Users/isaacs/dev-src/js/npm
│ ├── semver@1.0.1
│ └─┬ ronn@0.3.5
│ └── opts@1.2.1
└── supervisor@0.1.2 -&gt; /Users/isaacs/dev-src/js/node-supervisor

$ npm ls -gpl
/usr/local:::::
/usr/local/lib/node_modules/A:A@1.2.3::::/Users/isaacs/dev-src/js/A
/usr/local/lib/node_modules/A/node_modules/npm:npm@0.3.15::::/Users/isaacs/dev-src/js/A/node_modules/npm
/usr/local/lib/node_modules/A/node_modules/npm/node_modules/semver:semver@1.0.1::::/Users/isaacs/dev-src/js/A/node_modules/npm/node_modules/semver
/usr/local/lib/node_modules/B:B@1.2.3::::/Users/isaacs/dev-src/js/B
/usr/local/lib/node_modules/glob:glob@2.0.5::::
/usr/local/lib/node_modules/npm:npm@1.0.0::::/Users/isaacs/dev-src/js/npm
/usr/local/lib/node_modules/npm/node_modules/semver:semver@1.0.1::::/Users/isaacs/dev-src/js/npm/node_modules/semver
/usr/local/lib/node_modules/npm/node_modules/ronn:ronn@0.3.5::::/Users/isaacs/dev-src/js/npm/node_modules/ronn
/usr/local/lib/node_modules/npm/node_modules/ronn/node_modules/opts:opts@1.2.1::::/Users/isaacs/dev-src/js/npm/node_modules/ronn/node_modules/opts
/usr/local/lib/node_modules/supervisor:supervisor@0.1.2::::/Users/isaacs/dev-src/js/node-supervisor
</code></pre>

<p>Those <code>-&gt;</code> flags are indications that the package is link-installed, which will be covered in the next installment.</p>
25 doc/blog/release/node-v0-4-10.md
View file
@@ -0,0 +1,25 @@
version: 0.4.10
title: Node v0.4.10
author: ryandahl
date: Wed Jul 20 2011 07:36:38 GMT-0700 (PDT)
status: publish
category: release
slug: node-v0-4-10

2011.07.19, Version 0.4.10 (stable)
<ul><li>#394 Fix Buffer drops last null character in UTF-8
<li>#829 Backport r8577 from V8 (Ben Noordhuis)
<li>#877 Don't wait for HTTP Agent socket pool to establish connections.
<li>#915 Find kqueue on FreeBSD correctly (Brett Kiefer)
<li>#1085 HTTP: Fix race in abort/dispatch code (Stefan Rusu)
<li>#1274 debugger improvement (Yoshihiro Kikuchi)
<li>#1291 Properly respond to HEAD during end(body) hot path (Reid Burke)
<li>#1304 TLS: Fix race in abort/connection code (Stefan Rusu)
<li>#1360 Allow _ in url hostnames.
<li>Revert 37d529f8 - unbreaks debugger command parsing.
<li>Bring back global execScript
<li>Doc improvements</ul>

Download: <a href="http://nodejs.org/dist/node-v0.4.10.tar.gz">http://nodejs.org/dist/node-v0.4.10.tar.gz</a>
Website: <a href="http://nodejs.org/docs/v0.4.10">http://nodejs.org/docs/v0.4.10</a>
Documentation: <a href="http://nodejs.org/docs/v0.4.10/api">http://nodejs.org/docs/v0.4.10/api</a>
39 doc/blog/release/node-v0-4-11.md
View file
@@ -0,0 +1,39 @@
version: 0.4.11
title: Node v0.4.11
author: ryandahl
date: Thu Aug 18 2011 01:44:42 GMT-0700 (PDT)
status: publish
category: release
slug: node-v0-4-11

2011.08.17, Version 0.4.11 (stable)
<ul><li><a href="http://github.com/joyent/node/issues/738">#738</a> Fix crypto encryption/decryption with Base64. (SAWADA Tadashi)

<li><a href="http://github.com/joyent/node/issues/1202">#1202</a> net.createConnection defer DNS lookup error events to next tick (Ben Noordhuis)

<li><a href="http://github.com/joyent/node/issues/1374">#1374</a> fix setting ServerResponse.statusCode in writeHead (Trent Mick)

<li><a href="http://github.com/joyent/node/issues/1417">#1417</a> Fix http.ClientRequest crashes if end() was called twice

<li><a href="http://github.com/joyent/node/issues/1497">#1497</a> querystring: Replace 'in' test with 'hasOwnProperty' (isaacs)

<li><a href="http://github.com/joyent/node/issues/1546">#1546</a> http perf improvement

<li>fix memleak in libeio (Tom Hughes)

<li>cmake improvements (Tom Hughes)

<li>node_net.cc: fix incorrect sizeof() (Tom Hughes)

<li>Windows/cygwin: no more GetConsoleTitleW errors on XP (Bert Belder)

<li>Doc improvements (koichik, Logan Smyth, Ben Noordhuis, Arnout Kazemier)</ul>




Download: <a href="http://nodejs.org/dist/node-v0.4.11.tar.gz">http://nodejs.org/dist/node-v0.4.11.tar.gz</a>

Website: <a href="http://nodejs.org/docs/v0.4.11/">http://nodejs.org/docs/v0.4.11/</a>

Documentation: <a href="http://nodejs.org/docs/v0.4.11/api/">http://nodejs.org/docs/v0.4.11/api/</a>
29 doc/blog/release/node-v0-4-12.md
View file
@@ -0,0 +1,29 @@
version: 0.4.12
title: Node v0.4.12
author: ryandahl
date: Thu Sep 15 2011 17:32:07 GMT-0700 (PDT)
status: publish
category: release
slug: node-v0-4-12

2011.09.15, Version 0.4.12 (stable)

<ul>
<li>Improve docs
<li>#1563 overflow in ChildProcess custom_fd.
<li>#1569, parse error on multi-line HTTP headers. (Ben Noordhuis)
<li>#1586 net: Socket write encoding case sensitivity (koichik)
<li>#1610 Remove DigiNotar CA from trusted list (isaacs)
<li>#1624 buffer: Avoid overrun with 'binary' encoding. (koichik)
<li>#1633 buffer: write() should always set _charsWritten. (koichik)
<li>#1707 hasOwnProperty usage security hole in querystring (isaacs)
<li>#1719 Drain OpenSSL error queue
<li>Fix error reporting in net.Server.listen</ul>



Download: <a href="http://nodejs.org/dist/node-v0.4.12.tar.gz">http://nodejs.org/dist/node-v0.4.12.tar.gz</a>

Website: <a href="http://nodejs.org/docs/v0.4.12/">http://nodejs.org/docs/v0.4.12/</a>

Documentation: <a href="http://nodejs.org/docs/v0.4.12/api/">http://nodejs.org/docs/v0.4.12/api/</a>
33 doc/blog/release/node-v0-4-3.md
View file
@@ -0,0 +1,33 @@
version: 0.4.3
title: Node v0.4.3
author: ryandahl
date: Fri Mar 18 2011 22:17:59 GMT-0700 (PDT)
status: publish
category: release
slug: node-v0-4-3

2011.03.18, Version 0.4.3 (stable)
<ul>
<li> Don't decrease server connection counter again if destroy() is called more than once GH-431 (Andreas Reich, Anders Conbere)
<li> Documentation improvements (koichik)
<li> Fix bug with setMaxListeners GH-682
<li> Start up memory footprint improvement. (Tom Hughes)
<li> Solaris improvements.
<li> Buffer::Length(Buffer*) should not invoke itself recursively GH-759 (Ben Noordhuis)
<li> TLS: Advertise support for client certs GH-774 (Theo Schlossnagle)
<li> HTTP Agent bugs: GH-787, GH-784, GH-803.
<li> Don't call GetMemoryUsage every 5 seconds.
<li> Upgrade V8 to 3.1.8.3
</ul>



Download: http://nodejs.org/dist/node-v0.4.3.tar.gz

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

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

<a href="https://groups.google.com/d/topic/nodejs/JrYQCQtf6lM/discussion">Announcement</a>

<a href="https://github.com/joyent/node/tree/v0.4.3">commit</a>
27 doc/blog/release/node-v0-4-4.md
View file
@@ -0,0 +1,27 @@
version: 0.4.4
title: Node v0.4.4
author: ryandahl
date: Sat Mar 26 2011 08:58:45 GMT-0700 (PDT)
status: publish
category: release
slug: node-v0-4-4

2011.03.26, Version 0.4.4 (stable)
<ul>
<li> CryptoStream.end shouldn't throw if not writable GH-820
<li> Drop out if connection destroyed before connect() GH-819
<li> expose https.Agent
<li> Correctly setsid in tty.open GH-815
<li> Bug fix for failed buffer construction
<li> Added support for removing .once listeners (GH-806)
<li> Upgrade V8 to 3.1.8.5</ul>



Download: <a href="http://nodejs.org/dist/node-v0.4.4.tar.gz">http://nodejs.org/dist/node-v0.4.4.tar.gz</a>

Website: <a href="http://nodejs.org/docs/v0.4.4/">http://nodejs.org/docs/v0.4.4</a>

Documentation: <a href="http://nodejs.org/docs/v0.4.4/api/">http://nodejs.org/docs/v0.4.4/api</a>

<a href="https://groups.google.com/d/topic/nodejs/LlQCYhDEPAc/discussion">announcement</a>
29 doc/blog/release/node-v0-4-5.md
View file
@@ -0,0 +1,29 @@
version: 0.4.5
title: node v0.4.5
author: ryandahl
date: Sat Apr 02 2011 02:04:58 GMT-0700 (PDT)
status: publish
category: release
slug: node-v0-4-5

2011.04.01, Version 0.4.5 (stable)
<ul>
<li> Fix listener leak in stream.pipe() (Mikeal Rogers)
<li> Retain buffers in fs.read/write() GH-814 (Jorge Chamorro Bieling)
<li> TLS performance improvements
<li> SlowBuffer.prototype.slice bug GH-843
<li> process.stderr.write should return true
<li> Immediate pause/resume race condition GH-535 (isaacs)
<li> Set default host header properly GH-721 (isaacs)
<li> Upgrade V8 to 3.1.8.8</ul>



Download: <a href="http://nodejs.org/dist/node-v0.4.5.tar.gz">http://nodejs.org/dist/node-v0.4.5.tar.gz</a>

Website: <a href="http://nodejs.org/docs/v0.4.5">http://nodejs.org/docs/v0.4.5</a>

Documentation: <a href="http://nodejs.org/docs/v0.4.5/api">http://nodejs.org/docs/v0.4.5/api</a>


<a href="https://groups.google.com/d/topic/nodejs/aOC7SRLJhQY/discussion">announcement</a>
27 doc/blog/release/node-v0-4-6.md
View file
@@ -0,0 +1,27 @@
version: 0.4.6
title: Node v0.4.6
author: ryandahl
date: Thu Apr 14 2011 05:00:30 GMT-0700 (PDT)
status: publish
category: release
slug: node-v0-4-6

2011.04.13, Version 0.4.6 (stable)
<ul><li> Don't error on ENOTCONN from shutdown() #670
<li> Auto completion of built-in debugger suggests prefix match rather than partial match. (koichik)
<li> circular reference in vm modules. #822 (Jakub Lekstan)
<li> http response.readable should be false after 'end' #867 (Abe Fettig)
<li> Implemenet os.cpus() and os.uptime() on Solaris (Scott McWhirter)
<li> fs.ReadStream: Allow omission of end option for range reads #801 (Felix Geisendörfer)
<li> Buffer.write() with UCS-2 should not be write partial char #916 (koichik)
<Li> Pass secureProtocol through on tls.Server creation (Theo Schlossnagle)
<li> TLS use RC4-SHA by default
<li> Don't strangely drop out of event loop on HTTPS client uploads #892
<li> Doc improvements
<li> Upgrade v8 to 3.1.8.10</ul>

Download: <a href="http://nodejs.org/dist/node-v0.4.6.tar.gz">http://nodejs.org/dist/node-v0.4.6.tar.gz</a>

Website: <a href="http://nodejs.org/docs/v0.4.6/">http://nodejs.org/docs/v0.4.6/</a>

Documentation: <a href="http://nodejs.org/docs/v0.4.6/api/">http://nodejs.org/docs/v0.4.6/api/</a>
23 doc/blog/release/node-v0-4-7.md
View file
@@ -0,0 +1,23 @@
version: 0.4.7
title: Node v0.4.7
author: ryandahl
date: Sat Apr 23 2011 00:47:55 GMT-0700 (PDT)
status: publish
category: release
slug: node-v0-4-7

2011.04.22, Version 0.4.7 (stable)
<ul><li> Don't emit error on ECONNRESET from read() #670
<li> Fix: Multiple pipes to the same stream were broken #929 (Felix Geisendörfer)
<li> URL parsing/formatting corrections #954 (isaacs)
<li> make it possible to do repl.start('', stream) (Wade Simmons)
<li> Add os.loadavg for SunOS (Robert Mustacchi)
<li> Fix timeouts with floating point numbers #897 (Jorge Chamorro Bieling)
<li> Improve docs.</ul>


Download: <a href="http://nodejs.org/dist/node-v0.4.7.tar.gz">http://nodejs.org/dist/node-v0.4.7.tar.gz</a>

Website: <a href="http://nodejs.org/docs/v0.4.7/">http://nodejs.org/docs/v0.4.7/</a>

Documentation: <a href="http://nodejs.org/docs/v0.4.7/api">http://nodejs.org/docs/v0.4.7/api</a>
55 doc/blog/release/node-v0-4-8.md
View file
@@ -0,0 +1,55 @@
version: 0.4.8
title: Node v0.4.8
author: ryandahl
date: Sat May 21 2011 07:06:00 GMT-0700 (PDT)
status: publish
category: release
slug: node-v0-4-8

2011.05.20, Version 0.4.8 (stable)

* #974 Properly report traceless errors (isaacs)

* #983 Better JSON.parse error detection in REPL (isaacs)

* #836 Agent socket errors bubble up to req only if req exists

* #1041 Fix event listener leak check timing (koichik)

* #1038 Fix dns.resolve() with 'PTR' throws Error: Unknown type "PTR"
(koichik)

* #1073 Share SSL context between server connections (Fedor Indutny)

* Disable compression with OpenSSL. Improves memory perf.

* Implement os.totalmem() and os.freemem() for SunOS (Alexandre Marangone)

* Fix a special characters in URL regression (isaacs)

* Fix idle timeouts in HTTPS (Felix Geisendörfer)

* SlowBuffer.write() with 'ucs2' throws ReferenceError. (koichik)

* http.ServerRequest 'close' sometimes gets an error argument
(Felix Geisendörfer)

* Doc improvements

* cleartextstream.destroy() should close(2) the socket. Previously was being
mapped to a shutdown(2) syscall.

* No longer compile out asserts and debug statements in normal build.

* Debugger improvements.

* Upgrade V8 to 3.1.8.16.




Website: <a href="http://nodejs.org/docs/v0.4.8/">http://nodejs.org/docs/v0.4.8/</a>

Download: <a href="http://nodejs.org/dist/node-v0.4.8.tar.gz">http://nodejs.org/dist/node-v0.4.8.tar.gz</a>

Documentation: <a href="http://nodejs.org/docs/v0.4.8/api/">http://nodejs.org/docs/v0.4.8/api/</a>
30 doc/blog/release/node-v0-4-9.md
View file
@@ -0,0 +1,30 @@
version: 0.4.9
title: Node v0.4.9
author: ryandahl
date: Wed Jun 29 2011 11:41:05 GMT-0700 (PDT)
status: publish
category: release
slug: node-v0-4-9

2011.06.29, Version 0.4.9 (stable)<ul>
<li> Improve documentation
<li> #1095 error handling bug in stream.pipe() (Felix Geisendörfer)
<li> #1097 Fix a few leaks in node_crypto.cc (Ben Noordhuis)
<li> #562 #1078 Parse file:// urls properly (Ryan Petrello)
<li> #880 Option to disable SSLv2 (Jérémy Lal)
<li> #1087 Disabling SSL compression disabled with early OpenSSLs.
<li> #1144 debugger: don't allow users to input non-valid commands (Siddharth Mahendraker)
<li> Perf improvement for util.inherits
<li> #1166 Support for signature verification with RSA/DSA public keys (Mark Cavage)
<li> #1177 Remove node_modules lookup optimization to better support nested project structures (Mathias Buus)
<li> #1203 Add missing scope.Close to fs.sendfileSync
<li> #1187 Support multiple 'link' headers
<li> #1196 Fix -e/--eval can't load module from node_modules (Koichi Kobayashi)
<li> Upgrade V8 to 3.1.8.25, upgrade http-parser.</ul>


Download: <a href="http://nodejs.org/dist/node-v0.4.9.tar.gz">http://nodejs.org/dist/node-v0.4.9.tar.gz</a>

Website: <a href="http://nodejs.org/docs/v0.4.9">http://nodejs.org/docs/v0.4.9</a>

Documentation: <a href="http://nodejs.org/docs/v0.4.9/api">http://nodejs.org/docs/v0.4.9/api</a>
39 doc/blog/release/node-v0-5-0-unstable.md
View file
@@ -0,0 +1,39 @@
version: 0.5.0
title: Node v0.5.0 (Unstable)
author: ryandahl
date: Wed Jul 06 2011 02:23:17 GMT-0700 (PDT)
status: publish
category: release
slug: node-v0-5-0-unstable

2011.07.05, Version 0.5.0 (unstable)

<li> New non-default libuv backend to support IOCP on Windows. Use <code>--use-uv</code> to enable.
<li> deprecate http.cat
<li> docs improved.
<li> add child_process.fork
<li> add fs.utimes() and fs.futimes() support (Ben Noordhuis)
<li> add process.uptime() (Tom Huges)
<li> add path.relative (Tony Huang)
<li> add os.getNetworkInterfaces()
<li> add remoteAddress and remotePort for client TCP connections (Brian White)
<li> add secureOptions flag, setting ciphers, SSL_OP_CRYPTOPRO_TLSEXT_BUG to TLS (Theo Schlossnagle)
<li> add process.arch (Nathan Rajlich)
<li> add reading/writing of floats and doubles from/to buffers (Brian White)
<li> Allow script to be read from stdin
<li> #477 add Buffer::fill method to do memset (Konstantin Käfer)
<li> #573 Diffie-Hellman support to crypto module (Håvard Stranden)
<li> #695 add 'hex' encoding to buffer (isaacs)
<li> #851 Update how REPLServer uses contexts (Ben Weaver)
<li> #853 add fs.lchow, fs.lchmod, fs.fchmod, fs.fchown (isaacs)
<li> #889 Allow to remove all EventEmitter listeners at once (Felix Geisendörfer)
<li> #926 OpenSSL NPN support (Fedor Indutny)
<li> #955 Change ^C handling in REPL (isaacs)
<li> #979 add support for Unix Domain Sockets to HTTP (Mark Cavage)
<li> #1173 #1170 add AMD, asynchronous module definition (isaacs)
<li> DTrace probes: support X-Forwarded-For (Dave Pacheco) </ul>
Download: <a href="http://nodejs.org/dist/node-v0.5.0.tar.gz">http://nodejs.org/dist/node-v0.5.0.tar.gz</a>

Website: <a href="http://nodejs.org/docs/v0.5.0/">http://nodejs.org/docs/v0.5.0/</a>

Documentation: <a href="http://nodejs.org/docs/v0.5.0/api/">http://nodejs.org/docs/v0.5.0/api/</a>
30 doc/blog/release/node-v0-5-1.md
View file
@@ -0,0 +1,30 @@
version: 0.5.1
title: Node v0.5.1
author: ryandahl
date: Thu Jul 14 2011 23:48:08 GMT-0700 (PDT)
status: publish
category: release
slug: node-v0-5-1

2011.07.14, Version 0.5.1 (unstable)
<ul><li> #1233 Fix os.totalmem on FreeBSD amd64 (Artem Zaytsev)
<li> #1149 IDNA and Punycode support in url.parse (Jeremy Selier, Ben Noordhuis, isaacs)
<li> Export $CC and $CXX to uv and V8's build systems
<li> Include pthread-win32 static libraries in build (Igor Zinkovsky)
<li> #1199, #1094 Fix fs can't handle large file on 64bit platform (koichik)
<li> #1281 Make require a public member of module (isaacs)
<li> #1303 Stream.pipe returns the destination (Elijah Insua)
<li> #1229 Addons should not -DEV_MULTIPLICITY=0 (Brian White)
<li> libuv backend improvements
<li> Upgrade V8 to 3.4.10</ul>




Download: <a href="http://nodejs.org/dist/v0.5.1/node-v0.5.1.tar.gz">http://nodejs.org/dist/v0.5.1/node-v0.5.1.tar.gz</a>

Windows Build: <a href="http://nodejs.org/dist/v0.5.1/node.exe">http://nodejs.org/dist/v0.5.1/node.exe</a>

Documentation: <a href="http://nodejs.org/dist/v0.5.1/docs/api/">http://nodejs.org/dist/v0.5.1/docs/api/</a>

Website: <a href="http://nodejs.org/dist/v0.5.1/docs">http://nodejs.org/dist/v0.5.1/docs</a>
41 doc/blog/release/node-v0-5-10.md
View file
@@ -0,0 +1,41 @@
version: 0.5.10
title: Node v0.5.10
author: ryandahl
date: Fri Oct 21 2011 19:12:31 GMT-0700 (PDT)
status: publish
category: release
slug: node-v0-5-10

2011.10.21, Version 0.5.10 (unstable)
<ul><li>Remove cmake build system, support for Cygwin, legacy code base, process.ENV, process.ARGV, process.memoryUsage().vsize, os.openOSHandle</li>
<li>Documentation improvments (Igor Zinkovsky, Bert Belder, Ilya Dmitrichenko, koichik, Maciej Małecki, Guglielmo Ferri, isaacs)</li>
<li>Performance improvements (Daniel Ennis, Bert Belder, Ben Noordhuis) </li>
<li>Long process.title support (Ben Noordhuis)</li>
<li>net: register net.Server callback only once (Simen Brekken)</li>
<li>net: fix connect queue bugs (Ben Noordhuis)</li>
<li>debugger: fix backtrace err handling (Fedor Indutny)</li>
<li>Use getaddrinfo instead of c-ares for dns.lookup</li>
<li>Emit 'end' from crypto streams on close</li>
<li>repl: print out `undefined` (Nathan Rajlich)</li>
<li>#1902 buffer: use NO_NULL_TERMINATION flag (koichik)</li>
<li>#1907 http: Added support for HTTP PATCH verb (Thomas Parslow)</li>
<li>#1644 add GetCPUInfo on windows (Karl Skomski)</li>
<li>#1484, #1834, #1482, #771 Don't use a separate context for the repl. (isaacs)</li>
<li>#1882 zlib Update 'availOutBefore' value, and test (isaacs)</li>
<li>#1888 child_process.fork: don't modify args (koichik)</li>
<li>#1516 tls: requestCert unusable with Firefox and Chrome (koichik)</li>
<li>#1467 tls: The TLS API is inconsistent with the TCP API (koichik)</li>
<li>#1894 net: fix error handling in listen() (koichik)</li>
<li>#1860 console.error now goes through uv_tty_t</li>
<li>Upgrade V8 to 3.7.0</li>
<li>Upgrade GYP to r1081</li></ul>



Download: <a href="http://nodejs.org/dist/v0.5.10/node-v0.5.10.tar.gz">http://nodejs.org/dist/v0.5.10/node-v0.5.10.tar.gz</a>

Windows Executable: <a href="http://nodejs.org/dist/v0.5.10/node.exe">http://nodejs.org/dist/v0.5.10/node.exe</a>

Website: <a href="http://nodejs.org/docs/v0.5.10/">http://nodejs.org/docs/v0.5.10/</a>

Documentation: <a href="http://nodejs.org/docs/v0.5.10/api/">http://nodejs.org/docs/v0.5.10/api/</a>
27 doc/blog/release/node-v0-5-2.md
View file
@@ -0,0 +1,27 @@
version: 0.5.2
title: Node v0.5.2
author: ryandahl
date: Fri Jul 22 2011 11:40:22 GMT-0700 (PDT)
status: publish
category: release
slug: node-v0-5-2

2011.07.22, Version 0.5.2 (unstable)
<ul><li>libuv improvements; named pipe support
<li>#1242 check for SSL_COMP_get_compression_methods() (Ben Noordhuis)
<li>#1348 remove require.paths (isaacs)
<li>#1349 Delimit NODE_PATH with ; on Windows (isaacs)
<li>#1335 Remove EventEmitter from C++
<li>#1357 Load json files with require() (isaacs)
<li>#1374 fix setting ServerResponse.statusCode in writeHead (Trent Mick)
<li>Fixed: GC was being run too often.
<li>Upgrade V8 to 3.4.14
<li>doc improvements</ul>

Download: <a href="http://nodejs.org/dist/v0.5.2/node-v0.5.2.tar.gz">http://nodejs.org/dist/v0.5.2/node-v0.5.2.tar.gz</a>

Windows Executable: <a href="http://nodejs.org/dist/v0.5.2/node.exe">http://nodejs.org/dist/v0.5.2/node.exe</a>

Website: <a href="http://nodejs.org/dist/v0.5.2/docs/">http://nodejs.org/dist/v0.5.2/docs/</a>

Documentation: <a href="http://nodejs.org/dist/v0.5.2/docs/api">http://nodejs.org/dist/v0.5.2/docs/api</a>
53 doc/blog/release/node-v0-5-3.md
View file
@@ -0,0 +1,53 @@
version: 0.5.3
title: Node v0.5.3
author: ryandahl
date: Tue Aug 02 2011 08:03:06 GMT-0700 (PDT)
status: publish
category: release
slug: node-v0-5-3

2011.08.01, Version 0.5.3 (unstable)

<ul><li>Fix crypto encryption/decryption with Base64. (SAWADA Tadashi)

<li>#243 Add an optional length argument to Buffer.write() (koichik)

<li>#657 convert nonbuffer data to string in fs.writeFile/Sync (Daniel Pihlström)

<li>Add process.features, remove process.useUV (Ben Noordhuis)

<li>#324 Fix crypto hmac to accept binary keys + add test cases from rfc 2202 and 4231 (Stefan Bühler)

<li>Add Socket::bytesRead, Socket::bytesWritten (Alexander Uvarov)

<li>#572 Don't print result of --eval in CLI (Ben Noordhuis)

<li>#1223 Fix http.ClientRequest crashes if end() was called twice (koichik)

<li>#1383 Emit 'close' after all connections have closed (Felix Geisendörfer)

<li>Add sprintf-like util.format() function (Ben Noordhuis)

<li>Add support for TLS SNI (Fedor Indutny)

<li>New http agent implementation. Off by default the command line flag <code>--use-http2</code> will enable it. <code>make test-http2</code> will run the tests for the new implementation. (Mikeal Rogers)

<li>Revert AMD compatibility. (isaacs)

<li>Windows: improvements, child_process support.

<li>Remove pkg-config file.

<li>Fix startup time regressions.

<li>doc improvements</ul>



Download: <a href="http://nodejs.org/dist/v0.5.3/node-v0.5.3.tar.gz">http://nodejs.org/dist/v0.5.3/node-v0.5.3.tar.gz</a>

Windows Executable: <a href="http://nodejs.org/dist/v0.5.3/node.exe">http://nodejs.org/dist/v0.5.3/node.exe</a>

Website: <a href="http://nodejs.org/dist/v0.5.3/docs">http://nodejs.org/dist/v0.5.3/docs</a>

Documentation: <a href="http://nodejs.org/dist/v0.5.3/docs/api">http://nodejs.org/dist/v0.5.3/docs/api</a>
36 doc/blog/release/node-v0-5-4.md
View file
@@ -0,0 +1,36 @@
version: 0.5.4
title: Node v0.5.4
author: ryandahl
date: Fri Aug 12 2011 08:38:26 GMT-0700 (PDT)
status: publish
category: release
slug: node-v0-5-4

2011.08.12, Version 0.5.4 (unstable)

<ul><li>libuv/Windows compatibility improvements

<li>Build on Microsoft Visual Studio via GYP. Use generate-projects.bat in the to build sln files. (Peter Bright, Igor Zinkovsky)

<li>Make Mikeal's HTTP agent client the default. Use old HTTP client with <code>--use-http1</code>

<li>Fixes https host header default port handling. (Mikeal Rogers)

<li>#1440 strip byte order marker when loading *.js and *.json files (Ben Noordhuis)

<li>#1434 Improve util.format() compatibility with browser. (Koichi Kobayashi)

<li>Provide unchecked uint entry points for integer Buffer.read/writeInt methods. (Robert Mustacchi)

<li>CMake improvements (Tom Huges)

<li>Upgrade V8 to 3.5.4.</ul>


Download: <a href="http://nodejs.org/dist/v0.5.4/node-v0.5.4.tar.gz">http://nodejs.org/dist/v0.5.4/node-v0.5.4.tar.gz</a>

Windows Executable: <a href="http://nodejs.org/dist/v0.5.4/node.exe">http://nodejs.org/dist/v0.5.4/node.exe</a>

Website: <a href="http://nodejs.org/dist/v0.5.4/docs">http://nodejs.org/dist/v0.5.4/docs</a>

Documentation: <a href="http://nodejs.org/dist/v0.5.4/docs/api">http://nodejs.org/dist/v0.5.4/docs/api</a>
40 doc/blog/release/node-v0-5-5.md
View file
@@ -0,0 +1,40 @@
version: 0.5.5
title: Node v0.5.5
author: bennoordhuis
date: Fri Aug 26 2011 23:20:10 GMT-0700 (PDT)
status: publish
category: release
slug: node-v0-5-5

<p>2011.08.26, Version 0.5.5 (unstable)</p>
<ul>
<li>typed arrays, implementation from Plesk
<li>fix IP multicast on SunOS
<li>fix DNS lookup order: IPv4 first, IPv6 second (--use-uv only)
<li>remove support for UNIX datagram sockets (--use-uv only)
<li>UDP support for Windows (Bert Belder)
<li>#1572 improve tab completion for objects in the REPL (Nathan Rajlich)
<li>#1563 fix buffer overflow in child_process module (reported by Dean McNamee)
<li>#1546 fix performance regression in http module (reported by Brian Geffon)
<li>#1491 add PBKDF2 crypto support (Glen Low)
<li>#1447 remove deprecated http.cat() function (Mikeal Rogers)
<li>#1140 fix incorrect dispatch of vm.runInContext's filename argument<br />
(Antranig Basman)</p>
<li>#1140 document vm.runInContext() and vm.createContext() (Antranig Basman)
<li>#1428 fix os.freemem() on 64 bits freebsd (Artem Zaytsev)
<li>#1164 make all DNS lookups async, fixes uncatchable exceptions<br />
(Koichi Kobayashi)</p>
<li>fix incorrect ssl shutdown check (Tom Hughes)
<li>various cmake fixes (Tom Hughes)
<li>improved documentation (Koichi Kobayashi, Logan Smyth, Fedor Indutny,<br />
Mikeal Rogers, Maciej Małecki, Antranig Basman, Mickaël Delahaye)</p>
<li>upgrade libuv to commit 835782a
<li>upgrade V8 to 3.5.8
</ul>
<p>Download: <a href="http://nodejs.org/dist/node-v0.5.5.tar.gz">http://nodejs.org/dist/node-v0.5.5.tar.gz</a></p>
<p>Windows Executable: <a href="http://nodejs.org/dist/v0.5.5/node.exe">http://nodejs.org/dist/v0.5.5/node.exe</a></p>
<p>Website: <a href="http://nodejs.org/docs/v0.5.5/">http://nodejs.org/docs/v0.5.5/</a></p>
<p>Documentation: <a href="http://nodejs.org/docs/v0.5.5/api/">http://nodejs.org/docs/v0.5.5/api/</a></p>
<br /><br />

<b>Update:</b> The <code>.exe</code> has a bug that results in incompatibility with Windows XP and Server 2003. This has been reported in <a href="https://github.com/joyent/node/issues/1592">issue #1592</a> and fixed. A new binary was made that is compatibile with the older Windows: <a href="http://nodejs.org/dist/v0.5.5/node-186364e.exe">http://nodejs.org/dist/v0.5.5/node-186364e.exe</a>.
49 doc/blog/release/node-v0-5-6.md
View file
@@ -0,0 +1,49 @@
version: 0.5.6
title: Node v0.5.6 (unstable)
author: piscisaureus
date: Fri Sep 09 2011 16:30:39 GMT-0700 (PDT)
status: publish
category: release
slug: node-v0-5-6

2011.09.08, Version 0.5.6 (unstable)
<ul>
<li>#345, #1635, #1648 Documentation improvements (Thomas Shinnick, Abimanyu Raja, AJ ONeal, Koichi Kobayashi, Michael Jackson, Logan Smyth, Ben Noordhuis)</li>
<li>#650 Improve path parsing on windows (Bert Belder)</li>
<li>#752 Remove headers sent check in OutgoingMessage.getHeader() (Peter Lyons)</li>
<li>#1236, #1438, #1506, #1513, #1621, #1640, #1647 Libuv-related bugs fixed (Jorge Chamorro Bieling, Peter Bright, Luis Lavena, Igor Zinkovsky)</li>
<li>#1296, #1612 crypto: Fix BIO's usage. (Koichi Kobayashi)</li>
<li>#1345 Correctly set socket.remoteAddress with libuv backend (Bert Belder)</li>
<li>#1429 Don't clobber quick edit mode on windows (Peter Bright)</li>
<li>#1503 Make libuv backend default on unix, override with `node --use-legacy`</li>
<li>#1565 Fix fs.stat for paths ending with \ on windows (Igor Zinkovsky)</li>
<li>#1568 Fix x509 certificate subject parsing (Koichi Kobayashi)</li>
<li>#1586 Make socket write encoding case-insensitive (Koichi Kobayashi)</li>
<li>#1591, #1656, #1657 Implement fs in libuv, remove libeio and pthread-win32 dependency on windows (Igor Zinkovsky, Ben Noordhuis, Ryan Dahl, Isaac Schlueter)</li>
<li>#1592 Don't load-time link against CreateSymbolicLink on windows (Peter Bright)</li>
<li>#1601 Improve API consistency when dealing with the socket underlying a HTTP client request (Mikeal Rogers)</li>
<li>#1610 Remove DigiNotar CA from trusted list (Isaac Schlueter)</li>
<li>#1617 Added some win32 os functions (Karl Skomski)</li>
<li>#1624 avoid buffer overrun with 'binary' encoding (Koichi Kobayashi)</li>
<li>#1633 make Buffer.write() always set _charsWritten (Koichi Kobayashi)</li>
<li>#1644 Windows: set executables to be console programs (Peter Bright)</li>
<li>#1651 improve inspection for sparse array (Koichi Kobayashi)</li>
<li>#1672 set .code='ECONNRESET' on socket hang up errors (Ben Noordhuis)</li>
<li>Add test case for foaf+ssl client certificate (Niclas Hoyer)</li>
<li>Added RPATH environment variable to override run-time library paths (Ashok Mudukutore)</li>
<li>Added TLS client-side session resumption support (Sean Cunningham)</li>
<li>Added additional properties to getPeerCertificate (Nathan Rixham, Niclas Hoyer)</li>
<li>Don't eval repl command twice when an error is thrown (Nathan Rajlich)</li>
<li>Improve util.isDate() (Nathan Rajlich)</li>
<li>Improvements in libuv backend and bindings, upgrade libuv to bd6066cb349a9b3a1b0d87b146ddaee06db31d10</li>
<li>Show warning when using lib/sys.js (Maciej Malecki)</li>
<li>Support plus sign in url protocol (Maciej Malecki)</li>
<li>Upgrade V8 to 3.6.2</li>
</ul>
Download: <a href="http://nodejs.org/dist/v0.5.6/node-v0.5.6.tar.gz">http://nodejs.org/dist/v0.5.6/node-v0.5.6.tar.gz</a>

Windows Executable: <a href="http://nodejs.org/dist/v0.5.6/node.exe">http://nodejs.org/dist/v0.5.6/node.exe</a>

Website: <a href="http://nodejs.org/docs/v0.5.6/">http://nodejs.org/docs/v0.5.6/</a>

Documentation: <a href="http://nodejs.org/docs/v0.5.6/api/">http://nodejs.org/docs/v0.5.6/api/</a>
35 doc/blog/release/node-v0-5-7-unstable.md
View file
@@ -0,0 +1,35 @@
version: 0.5.7
title: Node v0.5.7 (unstable)
author: ryandahl
date: Fri Sep 16 2011 18:57:03 GMT-0700 (PDT)
status: publish
category: release
slug: node-v0-5-7-unstable

2011.09.16, Version 0.5.7 (unstable)
<ul>
<li>Upgrade V8 to 3.6.4
<li>Improve Windows compatibility
<li>Documentation improvements
<li>Debugger and REPL improvements (Fedor Indutny)
<li>Add legacy API support: net.Stream(fd), process.stdout.writable, process.stdout.fd
<li>Fix mkdir EEXIST handling (isaacs)
<li>Use net_uv instead of net_legacy for stdio
<li>Do not load readline from util.inspect
<li>#1673 Fix bug related to V8 context with accessors (Fedor Indutny)
<li>#1634 util: Fix inspection for Error (koichik)
<li>#1645 fs: Add positioned file writing feature to fs.WriteStream (Thomas Shinnick)
<li>#1637 fs: Unguarded fs.watchFile cache statWatchers checking fixed (Thomas Shinnick)
<li>#1695 Forward customFds to ChildProcess.spawn
<li>#1707 Fix hasOwnProperty security problem in querystring (isaacs)
<li>#1719 Drain OpenSSL error queue</ul>



Download: <a href="http://nodejs.org/dist/v0.5.7/node-v0.5.7.tar.gz">http://nodejs.org/dist/v0.5.7/node-v0.5.7.tar.gz</a>

Windows Executable: <a href="http://nodejs.org/dist/v0.5.7/node.exe">http://nodejs.org/dist/v0.5.7/node.exe</a>

Website: <a href="http://nodejs.org/docs/v0.5.7/">http://nodejs.org/docs/v0.5.7/</a>

Documentation: <a href="http://nodejs.org/docs/v0.5.7/api/">http://nodejs.org/docs/v0.5.7/api/</a>
26 doc/blog/release/node-v0-5-8.md
View file
@@ -0,0 +1,26 @@
version: 0.5.8
title: Node v0.5.8
author: ryandahl
date: Fri Sep 30 2011 16:47:11 GMT-0700 (PDT)
status: publish
category: release
slug: node-v0-5-8

2011.09.30, Version 0.5.8 (unstable)<ul><li>zlib bindings (isaacs)
<li>Windows supports TTY ANSI escape codes (Bert Belder)
<li>Debugger improvements (Fedor Indutny)
<li>crypto: look up SSL errors with ERR_print_errors() (Ben Noordhuis)
<li>dns callbacks go through MakeCallback now
<li>Raise an error when a malformed package.json file is found. (Ben Leslie)
<li>buffers: handle bad length argument in constructor (Ben Noordhuis)
<li>#1726, unref process.stdout
<li>Doc improvements (Ben Noordhuis, Fedor Indutny, koichik)
<li>Upgrade libuv to fe18438</ul>

Download: <a href="http://nodejs.org/dist/v0.5.8/node-v0.5.8.tar.gz">http://nodejs.org/dist/v0.5.8/node-v0.5.8.tar.gz</a>

Windows Executable: <a href="http://nodejs.org/dist/v0.5.8/node.exe">http://nodejs.org/dist/v0.5.8/node.exe</a>

Website: <a href="http://nodejs.org/docs/v0.5.8/">http://nodejs.org/docs/v0.5.8/</a>

Documentation: <a href="http://nodejs.org/docs/v0.5.8/api/">http://nodejs.org/docs/v0.5.8/api/</a>
27 doc/blog/release/node-v0-5-9.md
View file
@@ -0,0 +1,27 @@
version: 0.5.9
title: Node v0.5.9
author: ryandahl
date: Mon Oct 10 2011 19:06:21 GMT-0700 (PDT)
status: publish
category: release
slug: node-v0-5-9

2011.10.10, Version 0.5.9 (unstable)
<ul><li>fs.watch interface backed by kqueue, inotify, and ReadDirectoryChangesW (Igor Zinkovsky, Ben Noordhuis)</li>
<li>add dns.resolveTxt (Christian Tellnes)</li>
<li>Remove legacy http library (Ben Noordhuis)</li>
<li>child_process.fork returns and works on Windows. Allows passing handles. (Igor Zinkovsky, Bert Belder)</li>
<li>#1774 Lint and clean up for --harmony_block_scoping (Tyler Larson, Colton Baker)</li>
<li>#1813 Fix ctrl+c on Windows (Bert Belder)</li>
<li>#1844 unbreak --use-legacy (Ben Noordhuis)</li>
<li>process.stderr now goes through libuv. Both process.stdout and process.stderr are blocking when referencing a TTY.</li>
<li>net_uv performance improvements (Ben Noordhuis, Bert Belder)</li></ul>


Download: <a href="http://nodejs.org/dist/v0.5.9/node-v0.5.9.tar.gz">http://nodejs.org/dist/v0.5.9/node-v0.5.9.tar.gz</a>

Windows Executable: <a href="http://nodejs.org/dist/v0.5.9/node.exe">http://nodejs.org/dist/v0.5.9/node.exe</a>

Website: <a href="http://nodejs.org/docs/v0.5.9/">http://nodejs.org/docs/v0.5.9/</a>

Documentation: <a href="http://nodejs.org/docs/v0.5.9/api/">http://nodejs.org/docs/v0.5.9/api/</a>
80 doc/blog/release/node-v0-6-0.md
View file
@@ -0,0 +1,80 @@
version: 0.6.0
title: Node v0.6.0
author: ryandahl
date: Sat Nov 05 2011 02:07:10 GMT-0700 (PDT)
status: publish
category: release
slug: node-v0-6-0

We are happy to announce the third stable branch of Node v0.6. We will be freezing JavaScript, C++, and binary interfaces for all v0.6 releases.

The major differences between v0.4 and v0.6 are<ul>
<li>Native Windows support using I/O Completion Ports for sockets.
<li>Integrated load balancing over multiple processes. <a href="http://nodejs.org/docs/v0.6.0/api/cluster.html">docs</a>
<li>Better support for IPC between Node instances <a href="http://nodejs.org/docs/v0.6.0/api/child_processes.html#child_process.fork">docs</a>
<li>Improved command line debugger <a href="http://nodejs.org/docs/v0.6.0/api/debugger.html">docs</a>
<li>Built-in binding to zlib for compression <a href="http://nodejs.org/docs/v0.6.0/api/zlib.html">docs</a>
<li>Upgrade v8 from 3.1 to 3.6</ul>

In order to support Windows we reworked much of the core architecture. There was some fear that our work would degrade performance on UNIX systems but this was not the case. Here is a Linux system we benched for demonstration:

<table><tr> <th></th> <th>v0.4.12 (linux)</th><th>v0.6.0 (linux)</th></tr>
<tr> <td>http_simple.js /bytes/1024</td> <td>5461 r/s</td> <td>6263 r/s</td> </tr>
<tr> <td>io.js read </td> <td>19.75 mB/s</td> <td>26.63 mB/s</td> </tr>
<tr> <td>io.js write </td> <td>21.60 mB/s</td> <td>17.40 mB/s</td> </tr>
<tr> <td>startup.js </td> <td>74.7 ms</td> <td>49.6 ms</td> </tr></table>

Bigger is better in http and io benchmarks, smaller is better in startup. The http benchmark was done with 600 clients on a 10GE network served from three load generation machines.

In the last version of Node, v0.4, we could only run Node on Windows with Cygwin. Therefore we've gotten massive improvements by targeting the native APIs. Benchmarks on the same machine:

<table><tr><th></th><th>v0.4.12 (windows)</th><th>v0.6.0 (windows)</th></tr>
<tr> <td>http_simple.js /bytes/1024</td> <td>3858 r/s</td> <td>5823 r/s</td> </tr>
<tr> <td>io.js read </td> <td>12.41 mB/s</td> <td>26.51 mB/s</td> </tr>
<tr> <td>io.js write </td> <td>12.61 mB/s</td> <td>33.58 mB/s</td> </tr>
<tr> <td>startup.js </td> <td>152.81 ms</td> <td>52.04 ms</td> </tr></table>

We consider this a good intermediate stage for the Windows port. There is still work to be done. For example, we are not yet providing users with a blessed path for building addon modules in MS Visual Studio. Work will continue in later releases.

For users upgrading code bases from v0.4 to v0.6 <a href="https://github.com/joyent/node/wiki/API-changes-between-v0.4-and-v0.6">we've documented</a> most of the issues that you will run into. Most people find the change painless. Despite the long list of changes most core APIs remain untouched.

Our release cycle will be tightened dramatically now. Expect to see a new stable branch in January. We wish to eventually have our releases in sync with Chrome and V8's 6 week cycle.

Thank you to everyone who contributed code, tests, docs, or sent in bug reports.

Here are the changes between v0.5.12 and v0.6.0:

2011.11.04, Version 0.6.0 (stable)
<ul><li>print undefined on undefined values in REPL (Nathan Rajlich)</li>
<li>doc improvements (koichik, seebees, bnoordhuis, Maciej Małecki, Jacob Kragh)</li>
<li>support native addon loading in windows (Bert Belder)</li>
<li>rename getNetworkInterfaces() to networkInterfaces() (bnoordhuis)</li>
<li>add pending accepts knob for windows (igorzi)</li>
<li>http.request(url.parse(x)) (seebees)</li>
<li>#1929 zlib Respond to 'resume' events properly (isaacs)</li>
<li>stream.pipe: Remove resume and pause events</li>
<li>test fixes for windows (igorzi)</li>
<li>build system improvements (bnoordhuis)</li>
<li>#1936 tls: does not emit 'end' from EncryptedStream (koichik)</li>
<li>#758 tls: add address(), remoteAddress/remotePort</li>
<li>#1399 http: emit Error object after .abort() (bnoordhuis)</li>
<li>#1999 fs: make mkdir() default to 0777 permissions (bnoordhuis)</li>
<li>#2001 fix pipe error codes</li>
<li>#2002 Socket.write should reset timeout timer</li>
<li>stdout and stderr are blocking when associated with file too.</li>
<li>remote debugger support on windows (Bert Belder)</li>
<li>convenience methods for zlib (Matt Robenolt)</li>
<li>process.kill support on windows (igorzi)</li>
<li>process.uptime() support on windows (igorzi)</li>
<li>Return IPv4 addresses before IPv6 addresses from getaddrinfo</li>
<li>util.inspect improvements (Nathan Rajlich)</li>
<li>cluster module api changes</li>
<li>Downgrade V8 to 3.6.6.6</li></ul>

Download: <a href="http://nodejs.org/dist/v0.6.0/node-v0.6.0.tar.gz">http://nodejs.org/dist/v0.6.0/node-v0.6.0.tar.gz</a>

Windows Executable: <a href="http://nodejs.org/dist/v0.6.0/node.exe">http://nodejs.org/dist/v0.6.0/node.exe</a>

Website: <a href="http://nodejs.org/docs/v0.6.0/">http://nodejs.org/docs/v0.6.0/</a>

Documentation: <a href="http://nodejs.org/docs/v0.6.0/api/">http://nodejs.org/docs/v0.6.0/api/</a>
33 doc/blog/release/node-v0-6-1.md
View file
@@ -0,0 +1,33 @@
version: 0.6.1
title: Node v0.6.1
author: ryandahl
date: Fri Nov 11 2011 15:34:15 GMT-0800 (PST)
status: publish
category: release
slug: node-v0-6-1

2011.11.11, Version 0.6.1 (stable)
<ul><li>doc improvements (Eric Lovett, Ben Noordhuis, Scott Anderson, Yoji SHIDARA)</li>
<li>crypto: make thread-safe (Ben Noordhuis)</li>
<li>fix process.kill error object</li>
<li>debugger: correctly handle source with multi-byte characters (Shigeki Ohtsu)</li>
<li>make stdout and stderr non-destroyable (Igor Zinkovsky)</li>
<li>fs: don't close uninitialized fs.watch handle (Ben Noordhuis)</li>
<li>#2026 fix man page install on BSDs (Ben Noordhuis)</li>
<li>#2040 fix unrecognized errno assert in uv_err_name</li>
<li>#2043 fs: mkdir() should call callback if mode is omitted</li>
<li>#2045 fs: fix fs.realpath on windows to return on error (Benjamin Pasero)</li>
<li>#2047 minor cluster improvements</li>
<li>#2052 readline get window columns correctly</li>
<li>Upgrade V8 to 3.6.6.7</li></ul>


Source Code: <a href="http://nodejs.org/dist/v0.6.1/node-v0.6.1.tar.gz">http://nodejs.org/dist/v0.6.1/node-v0.6.1.tar.gz</a>

Windows Installer: <a href="http://nodejs.org/dist/v0.6.1/node-v0.6.1.msi">http://nodejs.org/dist/v0.6.1/node-v0.6.1.msi</a>

Macintosh Installer: <a href="http://nodejs.org/dist/v0.6.1/node-v0.6.1.pkg">http://nodejs.org/dist/v0.6.1/node-v0.6.1.pkg</a>

Website: <a href="http://nodejs.org/docs/v0.6.1/">http://nodejs.org/docs/v0.6.1/</a>

Documentation: <a href="http://nodejs.org/docs/v0.6.1/api/">http://nodejs.org/docs/v0.6.1/api/</a>
30 doc/blog/release/node-v0-6-10.md
View file
@@ -0,0 +1,30 @@
version: 0.6.10
title: Node v0.6.10
author: Isaac Schlueter
date: Thu Feb 02 2012 17:22:03 GMT-0800 (PST)
status: publish
category: release
slug: node-v0-6-10

<p>2012.02.02, Version 0.6.10 (stable)</p>

<ul>
<li><p>Update V8 to 3.6.6.20</p></li>
<li><p>Add npm msysgit bash shim to msi installer (isaacs)</p></li>
<li><p>buffers: fix intermittent out of bounds error (Ben Noordhuis)</p></li>
<li><p>buffers: honor length argument in base64 decoder (Ben Noordhuis)</p></li>
<li><p>windows: Fix path.exists regression (Bert Belder)</p></li>
<li><p>Make QueryString.parse run faster (Philip Tellis)</p></li>
<li><p>http: avoid freeing http-parser objects too early (koichik)</p></li>
<li><p>timers: add v0.4 compatibility hack (Ben Noordhuis)</p></li>
<li><p>Proper EPERM error code support (Igor Zinkovsky, Brandon Philips)</p></li>
<li><p>dgram: Implement udp multicast methods on windows (Bert Belder)</p></li>
</ul><p>Source Code: <a href="http://nodejs.org/dist/v0.6.10/node-v0.6.10.tar.gz">http://nodejs.org/dist/v0.6.10/node-v0.6.10.tar.gz</a></p>

<p>Windows Installer: <a href="http://nodejs.org/dist/v0.6.10/node-v0.6.10.msi">http://nodejs.org/dist/v0.6.10/node-v0.6.10.msi</a></p>

<p>Macintosh Installer: <a href="http://nodejs.org/dist/v0.6.10/node-v0.6.10.pkg">http://nodejs.org/dist/v0.6.10/node-v0.6.10.pkg</a></p>

<p>Website: <a href="http://nodejs.org/docs/v0.6.10/">http://nodejs.org/docs/v0.6.10/</a></p>

<p>Documentation: <a href="http://nodejs.org/docs/v0.6.10/api/">http://nodejs.org/docs/v0.6.10/api/</a></p>