category: Uncategorized
slug: an-easy-way-to-build-scalable-network-programs
-Suppose you're writing a web server which does video encoding on each file upload. Video encoding is very much compute bound. Some recent blog posts suggest that Node.js would fail miserably at this.\r
-\r
-Using Node does not mean that you have to write a video encoding algorithm in JavaScript (a language without even 64 bit integers) and crunch away in the main server event loop. The suggested approach is to separate the I/O bound task of receiving uploads and serving downloads from the compute bound task of video encoding. In the case of video encoding this is accomplished by forking out to ffmpeg. Node provides advanced means of asynchronously controlling subprocesses for work like this.\r
-\r
-It has also been suggested that Node does not take advantage of multicore machines. Node has long supported load-balancing connections over multiple processes in just a few lines of code - in this way a Node server will use the available cores. In coming releases we'll make it even easier: just pass <code>--balance</code> on the command line and Node will manage the cluster of processes.\r
-\r
-Node has a clear purpose: provide an easy way to build scalable network programs. It is not a tool for every problem. Do not write a ray tracer with Node. Do not write a web browser with Node. Do however reach for Node if tasked with writing a DNS server, DHCP server, or even a video encoding server.\r
-\r
+Suppose you're writing a web server which does video encoding on each file upload. Video encoding is very much compute bound. Some recent blog posts suggest that Node.js would fail miserably at this.
+
+Using Node does not mean that you have to write a video encoding algorithm in JavaScript (a language without even 64 bit integers) and crunch away in the main server event loop. The suggested approach is to separate the I/O bound task of receiving uploads and serving downloads from the compute bound task of video encoding. In the case of video encoding this is accomplished by forking out to ffmpeg. Node provides advanced means of asynchronously controlling subprocesses for work like this.
+
+It has also been suggested that Node does not take advantage of multicore machines. Node has long supported load-balancing connections over multiple processes in just a few lines of code - in this way a Node server will use the available cores. In coming releases we'll make it even easier: just pass <code>--balance</code> on the command line and Node will manage the cluster of processes.
+
+Node has a clear purpose: provide an easy way to build scalable network programs. It is not a tool for every problem. Do not write a ray tracer with Node. Do not write a web browser with Node. Do however reach for Node if tasked with writing a DNS server, DHCP server, or even a video encoding server.
+
By relying on the kernel to schedule and preempt computationally expensive tasks and to load balance incoming connections, Node appears less magical than server platforms that employ userland scheduling. So far, our focus on simplicity and transparency has paid off: <a href="http://joyeur.com/2011/08/11/node-js-meetup-distributed-web-architectures/">the</a> <a href="http://venturebeat.com/2011/08/16/linkedin-node/">number</a> <a href="http://corp.klout.com/blog/2011/10/the-tech-behind-klout-com/">of</a> <a href="http://www.joelonsoftware.com/items/2011/09/13.html">success</a> <a href="http://pow.cx/">stories</a> from developers and corporations who are adopting the technology continues to grow.
category: Uncategorized
slug: development-environment
-If you're compiling a software package because you need a particular version (e.g. the latest), then it requires a little bit more maintenance than using a package manager like <code>dpkg</code>. Software that you compile yourself should *not* go into <code>/usr</code>, it should go into your home directory. This is part of being a software developer. \r
-\r
-One way of doing this is to install everything into <code>$HOME/local/$PACKAGE</code>. Here is how I install node on my machine:<pre>./configure --prefix=$HOME/local/node-v0.4.5 && make install</pre>\r
-\r
-To have my paths automatically set I put this inside my <code>$HOME/.zshrc</code>:<pre>PATH="$HOME/local/bin:/opt/local/bin:/usr/bin:/sbin:/bin"\r
-LD_LIBRARY_PATH="/opt/local/lib:/usr/local/lib:/usr/lib"\r
-for i in $HOME/local/*; do\r
- [ -d $i/bin ] && PATH="${i}/bin:${PATH}"\r
- [ -d $i/sbin ] && PATH="${i}/sbin:${PATH}"\r
- [ -d $i/include ] && CPATH="${i}/include:${CPATH}"\r
- [ -d $i/lib ] && LD_LIBRARY_PATH="${i}/lib:${LD_LIBRARY_PATH}"\r
- [ -d $i/lib/pkgconfig ] && PKG_CONFIG_PATH="${i}/lib/pkgconfig:${PKG_CONFIG_PATH}"\r
- [ -d $i/share/man ] && MANPATH="${i}/share/man:${MANPATH}"\r
-done</pre>\r
-\r
-Node is under sufficiently rapid development that <i>everyone</i> should be compiling it themselves. A corollary of this is that <code>npm</code> (which should be installed alongside Node) does not require root to install packages.\r
-\r
+If you're compiling a software package because you need a particular version (e.g. the latest), then it requires a little bit more maintenance than using a package manager like <code>dpkg</code>. Software that you compile yourself should *not* go into <code>/usr</code>, it should go into your home directory. This is part of being a software developer.
+
+One way of doing this is to install everything into <code>$HOME/local/$PACKAGE</code>. Here is how I install node on my machine:<pre>./configure --prefix=$HOME/local/node-v0.4.5 && make install</pre>
+
+To have my paths automatically set I put this inside my <code>$HOME/.zshrc</code>:<pre>PATH="$HOME/local/bin:/opt/local/bin:/usr/bin:/sbin:/bin"
+LD_LIBRARY_PATH="/opt/local/lib:/usr/local/lib:/usr/lib"
+for i in $HOME/local/*; do
+ [ -d $i/bin ] && PATH="${i}/bin:${PATH}"
+ [ -d $i/sbin ] && PATH="${i}/sbin:${PATH}"
+ [ -d $i/include ] && CPATH="${i}/include:${CPATH}"
+ [ -d $i/lib ] && LD_LIBRARY_PATH="${i}/lib:${LD_LIBRARY_PATH}"
+ [ -d $i/lib/pkgconfig ] && PKG_CONFIG_PATH="${i}/lib/pkgconfig:${PKG_CONFIG_PATH}"
+ [ -d $i/share/man ] && MANPATH="${i}/share/man:${MANPATH}"
+done</pre>
+
+Node is under sufficiently rapid development that <i>everyone</i> should be compiling it themselves. A corollary of this is that <code>npm</code> (which should be installed alongside Node) does not require root to install packages.
+
CPAN and RubyGems have blurred the lines between development tools and system package managers. With <code>npm</code> we wish to draw a clear line: it is not a system package manager. It is not for installing firefox or ffmpeg or OpenSSL; it is for rapidly downloading, building, and setting up Node packages. <code>npm</code> is a <i>development</i> tool. When a program written in Node becomes sufficiently mature it should be distributed as a tarball, <code>.deb</code>, <code>.rpm</code>, or other package system. It should not be distributed to end users with <code>npm</code>.
category: Uncategorized
slug: evolving-the-node-js-brand
-To echo <a href="http://nodejs.org/">Node</a>’s evolutionary nature, we have refreshed the identity to help mark an exciting time for developers, businesses and users who benefit from the pioneering technology.\r
-\r
-<strong>Building a brand</strong>\r
-\r
-We began exploring elements to express Node.js and jettisoned preconceived notions about what we thought Node should look like, and focused on what Node is: <strong>kinetic</strong>,<ins cite="mailto:EMILY%20TANAKA-DELGADO" datetime="2011-07-09T18:32"></ins><strong>connected</strong>, <strong>scalable</strong>, <strong>modular</strong>, <strong>mechanical</strong> and <strong>organic</strong>. Working with designer <a href="http://www.chrisglass.com">Chris Glass</a>, our explorations emphasized Node's dynamism and formed a visual language based on structure, relationships and interconnectedness.\r
-\r
-<img class="alignnone size-full wp-image-184" title="grid" src="http://nodeblog.files.wordpress.com/2011/07/grid.png" alt="" width="520" height="178" />\r
-\r
-Inspired by <strong>process visualization, </strong>we discovered pattern, form, and by relief, the hex shape. The angled infrastructure encourages energy to move through the letterforms.\r
-\r
-<img class="alignnone size-full wp-image-185" title="nodejs" src="http://nodeblog.files.wordpress.com/2011/07/nodejs.png" alt="" width="520" height="178" />\r
-\r
-This language can expand into the organic network topography of Node or distill down into a single hex connection point.\r
-\r
-This scaling represents the dynamic nature of Node in a simple, distinct manner.\r
-\r
-<img title="Node.js network" src="http://joyeur.files.wordpress.com/2011/07/network.png" alt="" width="560" height="270" />\r
-\r
-We look forward to exploring<ins cite="mailto:EMILY%20TANAKA-DELGADO" datetime="2011-07-09T18:30"> </ins>this visual language as the technology charges into a very promising future.\r
-\r
-<img title="Node.js nebula" src="http://joyeur.files.wordpress.com/2011/07/node.png" alt="" width="560" height="460" />\r
-\r
-We hope you'll have fun using it.\r
-\r
-To download the new logo, visit <a href="http://nodejs.org/logos/">nodejs.org/logos</a>.\r
-\r
+To echo <a href="http://nodejs.org/">Node</a>’s evolutionary nature, we have refreshed the identity to help mark an exciting time for developers, businesses and users who benefit from the pioneering technology.
+
+<strong>Building a brand</strong>
+
+We began exploring elements to express Node.js and jettisoned preconceived notions about what we thought Node should look like, and focused on what Node is: <strong>kinetic</strong>,<ins cite="mailto:EMILY%20TANAKA-DELGADO" datetime="2011-07-09T18:32"></ins><strong>connected</strong>, <strong>scalable</strong>, <strong>modular</strong>, <strong>mechanical</strong> and <strong>organic</strong>. Working with designer <a href="http://www.chrisglass.com">Chris Glass</a>, our explorations emphasized Node's dynamism and formed a visual language based on structure, relationships and interconnectedness.
+
+<img class="alignnone size-full wp-image-184" title="grid" src="http://nodeblog.files.wordpress.com/2011/07/grid.png" alt="" width="520" height="178" />
+
+Inspired by <strong>process visualization, </strong>we discovered pattern, form, and by relief, the hex shape. The angled infrastructure encourages energy to move through the letterforms.
+
+<img class="alignnone size-full wp-image-185" title="nodejs" src="http://nodeblog.files.wordpress.com/2011/07/nodejs.png" alt="" width="520" height="178" />
+
+This language can expand into the organic network topography of Node or distill down into a single hex connection point.
+
+This scaling represents the dynamic nature of Node in a simple, distinct manner.
+
+<img title="Node.js network" src="http://joyeur.files.wordpress.com/2011/07/network.png" alt="" width="560" height="270" />
+
+We look forward to exploring<ins cite="mailto:EMILY%20TANAKA-DELGADO" datetime="2011-07-09T18:30"> </ins>this visual language as the technology charges into a very promising future.
+
+<img title="Node.js nebula" src="http://joyeur.files.wordpress.com/2011/07/node.png" alt="" width="560" height="460" />
+
+We hope you'll have fun using it.
+
+To download the new logo, visit <a href="http://nodejs.org/logos/">nodejs.org/logos</a>.
+
<ins cite="mailto:EMILY%20TANAKA-DELGADO" datetime="2011-07-09T18:32"><img title="Tri-color Node" src="http://joyeur.files.wordpress.com/2011/07/tri-color-node.png" alt="" width="560" height="180" /></ins>
category: Uncategorized
slug: growing-up
-This week Microsoft announced <a href="https://www.windowsazure.com/en-us/develop/nodejs/">support for Node in Windows Azure</a>, their cloud computing platform. For the Node core team and the community, this is an important milestone. We've worked hard over the past six months reworking Node's machinery to support IO completion ports and Visual Studio to provide a good native port to Windows. The overarching goal of the port was to expand our user base to the largest number of developers. Happily, this has paid off in the form of being a first class citizen on Azure. Many users who would have never used Node as a pure unix tool are now up and running on the Windows platform. More users translates into a deeper and better ecosystem of modules, which makes for a better experience for everyone.\r
-\r
-We also redesigned <a href="http://nodejs.org">our website</a> - something that we've put off for a long time because we felt that Node was too nascent to dedicate marketing to it. But now that we have binary distributions for Macintosh and Windows, have bundled npm, and are <a href="https://twitter.com/#!/mranney/status/145778414165569536">serving millions of users</a> at various companies, we felt ready to indulge in a new website and share of a few of our success stories on the home page.\r
-\r
+This week Microsoft announced <a href="https://www.windowsazure.com/en-us/develop/nodejs/">support for Node in Windows Azure</a>, their cloud computing platform. For the Node core team and the community, this is an important milestone. We've worked hard over the past six months reworking Node's machinery to support IO completion ports and Visual Studio to provide a good native port to Windows. The overarching goal of the port was to expand our user base to the largest number of developers. Happily, this has paid off in the form of being a first class citizen on Azure. Many users who would have never used Node as a pure unix tool are now up and running on the Windows platform. More users translates into a deeper and better ecosystem of modules, which makes for a better experience for everyone.
+
+We also redesigned <a href="http://nodejs.org">our website</a> - something that we've put off for a long time because we felt that Node was too nascent to dedicate marketing to it. But now that we have binary distributions for Macintosh and Windows, have bundled npm, and are <a href="https://twitter.com/#!/mranney/status/145778414165569536">serving millions of users</a> at various companies, we felt ready to indulge in a new website and share of a few of our success stories on the home page.
+
Work is on-going. We continue to improve the software, making performance improvements and adding isolate support, but Node is growing up.
category: Uncategorized
slug: jobs-nodejs-org
-We are starting an official jobs board for Node. There are two goals for this\r
-\r
-1. Promote the small emerging economy around this platform by having a central space for employers to find Node programmers.\r
-\r
-2. Make some money. We work hard to build this platform and taking a small tax for job posts seems a like reasonable "tip jar".\r
-\r
+We are starting an official jobs board for Node. There are two goals for this
+
+1. Promote the small emerging economy around this platform by having a central space for employers to find Node programmers.
+
+2. Make some money. We work hard to build this platform and taking a small tax for job posts seems a like reasonable "tip jar".
+
<a href="http://jobs.nodejs.org">jobs.nodejs.org</a>
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...\r
-<h2>What is LDAP and where did it come from?</h2>\r
-
-Directory services were largely pioneered by the telecommunications companies (e.g., AT&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\r
-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).\r
-\r
-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.\r
-\r
-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.\r
-\r
-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>.\r
-\r
-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.\r
-\r
-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.\r
-\r
-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.\r
-<h2>LDAP: The Good Parts</h2>\r
-
-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\r
-with _a lot_ of use case (the quintessential example is white pages for people in your company, but subscriptions to SaaS applications, "host groups"\r
-for tracking machines/instances, physical goods tracking, etc., all have use cases that fit that organization scheme). For example, presumably at your job\r
-you have a "reporting chain." Let's say a given record in LDAP (I'll use myself as a guinea pig here) looks like:\r
-<pre> firstName: Mark\r
- lastName: Cavage\r
- city: Seattle\r
- uid: markc\r
- state: Washington\r
- mail: mcavagegmailcom\r
- phone: (206) 555-1212\r
- title: Software Engineer\r
- department: 123456\r
- objectclass: joyentPerson</pre>\r
-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:\r
-<pre> uid=david\r
- /\r
- uid=bryan\r
- / | \\r
- uid=markc uid=ryah uid=isaacs</pre>\r
-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:\r
-<pre> (title="Software Engineer")</pre>\r
-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:\r
-<pre> (&(title="Software Engineer")(city=Seattle))</pre>\r
-I could keep going, but the gist is that LDAP has "full" boolean predicate logic, wildcard filters, etc. It's really rich.\r
-\r
-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.\r
-<h2>ldapjs: Why do I care?</h2>\r
-
-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:\r
-<ul>\r
- <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>\r
- <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>\r
- <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>\r
- <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>\r
-</ul>\r
-\r
-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\r
-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\r
-aspects of the protocol itself too, but that's a lot harder).\r
-\r
-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:\r
-<ul>\r
- <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>\r
- <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>\r
- <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>\r
- <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>\r
-</ul>\r
-\r
-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.\r
-\r
-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).\r
-\r
-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!\r
-\r
-<h2>The Road Ahead</h2>\r
-
-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.\r
+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&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> (&(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.
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.\r
-\r
-<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.\r
-\r
-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.\r
-\r
-The current implmented features are:\r
-<ul>\r
- <li>Non-blocking TCP sockets (using IOCP on Windows)</li>\r
- <li>Non-blocking named pipes</li>\r
- <li>UDP</li>\r
- <li>Timers</li>\r
- <li>Child process spawning</li>\r
- <li>Asynchronous DNS via <a href="http://c-ares.haxx.se/">c-ares</a> or <code>uv_getaddrinfo</code>.</li>\r
- <li>Asynchronous file system APIs <code>uv_fs_*</code></li>\r
- <li>High resolution time <code>uv_hrtime</code></li>\r
- <li>Current executable path look up <code>uv_exepath</code></li>\r
- <li>Thread pool scheduling <code>uv_queue_work</code></li>\r
-</ul>\r
-The features we are working on still are\r
-<ul>\r
- <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>\r
- <li>VT100 TTY <code>uv_tty_t</code></li>\r
- <li>Socket sharing between processes <code>uv_ipc_t (<a href="https://gist.github.com/1233593">planned API</a>)</code></li>\r
-</ul>\r
-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.\r
-\r
-<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.\r
-\r
-In addition to Node v0.5, a number of projects have begun to use <code>libuv</code>:\r
-<ul>\r
- <li>Mozilla's <a href="https://github.com/graydon/rust">Rust</a></li>\r
- <li>Tim Caswell's <a href="https://github.com/creationix/luanode">LuaNode</a></li>\r
- <li>Ben Noordhuis and Bert Belder's <a href="https://github.com/bnoordhuis/phode">Phode</a> async PHP project</li>\r
- <li>Kerry Snyder's <a href="https://github.com/kersny/libuv-csharp">libuv-csharp</a></li>\r
- <li>Andrea Lattuada's <a href="https://gist.github.com/1195428">web server</a></li>\r
-</ul>\r
+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!
category: Uncategorized
slug: node-meetup-this-thursday
-<a href="http://nodejs.org/meetup/" title="http://nodejs.org/meetup/ ">http://nodejs.org/meetup/</a>\r
-<a href="http://nodemeetup.eventbrite.com/">http://nodemeetup.eventbrite.com/</a>\r
-\r
+<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!
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.\r
-\r
-The week after, Thursday May 5th, we will all be at NodeConf in Portland.\r
-\r
+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.
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&layer=c&sll=37.793040,-122.400491&cbp=13,178.31,,0,-60.77&cbll=37.793131,-122.400484&hl=en&sspn=0.006295,0.006295&ie=UTF8&hq=&hnear=345+California+St,+San+Francisco,+California+94104&ll=37.793131,-122.400484&spn=0.001295,0.003428&z=19&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.\r
-\r
-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>.\r
-\r
+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&layer=c&sll=37.793040,-122.400491&cbp=13,178.31,,0,-60.77&cbll=37.793131,-122.400484&hl=en&sspn=0.006295,0.006295&ie=UTF8&hq=&hnear=345+California+St,+San+Francisco,+California+94104&ll=37.793131,-122.400484&spn=0.001295,0.003428&z=19&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.
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.\r
- \r
-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.\r
- \r
+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.
category: Uncategorized
slug: some-new-node-projects
-<ul>\r
-<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’s what we worked on the past couple days, and <a href="https://github.com/superfeedr/node-xmpp">it’s now on Github</a>!</i></li>\r
-\r
-<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>\r
-\r
+<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’s what we worked on the past couple days, and <a href="https://github.com/superfeedr/node-xmpp">it’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
category: Uncategorized
slug: the-videos-from-node-meetup
-Uber, Voxer, and Joyent described how they use Node in production\r
-\r
+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>
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.\r
-\r
-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.\r
-\r
-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.\r
-\r
-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.\r
-\r
-<a href="http://nodejs.org/trademark-policy.pdf">http://nodejs.org/trademark-policy.pdf</a>\r
+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
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.\r
-\r
-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.\r
-\r
+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!
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>\r
-\r
-<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>\r
-\r
-<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>\r
-\r
-<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>\r
-\r
-<p>To start using fleet, just install the fleet command with <a href="http://npmjs.org">npm</a>: </p>\r
-\r
-<pre style="">npm install -g fleet </pre>\r
-\r
-<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>\r
-\r
-<pre style="">fleet hub --port=7000 --secret=beepboop </pre>\r
-\r
-<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>\r
-\r
-<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>\r
-\r
-<pre style="">fleet drone --hub=x.x.x.x:7000 --secret=beepboop </pre>\r
-\r
-<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>\r
-\r
-<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>\r
-\r
-<pre style="">fleet remote add default --hub=x.x.x.x:7000 --secret=beepboop </pre>\r
-\r
-<p>Fleet just created a <span class="code">fleet.json</span> file for you to save your settings. </p>\r
-\r
-<p>From the same app directory, to deploy your code just do: </p>\r
-\r
-<pre style="">fleet deploy </pre>\r
-\r
-<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>\r
-\r
-<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>\r
-\r
-<pre style="">fleet spawn -- node server.js 8080 </pre>\r
-\r
-<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>\r
-\r
-<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>\r
-\r
-<pre style="">fleet ps\r
-drone#3dfe17b8\r
-├─┬ pid#1e99f4\r
-│ ├── status: running\r
-│ ├── commit: webapp/1b8050fcaf8f1b02b9175fcb422644cb67dc8cc5\r
-│ └── command: node server.js 8888\r
-└─┬ pid#d7048a\r
- ├── status: running\r
- ├── commit: webapp/1b8050fcaf8f1b02b9175fcb422644cb67dc8cc5\r
- └── command: node server.js 8889</pre>\r
-\r
-<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>\r
-\r
-<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>\r
-\r
-<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>\r
-\r
-<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>\r
-\r
-<pre style="">fleet help\r
-Usage: fleet <command> [<args>]\r
-\r
-The commands are:\r
- deploy Push code to drones.\r
- drone Connect to a hub as a worker.\r
- exec Run commands on drones.\r
- hub Create a hub for drones to connect.\r
- monitor Show service events system-wide.\r
- ps List the running processes on the drones.\r
- remote Manage the set of remote hubs.\r
- spawn Run services on drones.\r
- stop Stop processes running on drones.\r
-\r
-For help about a command, try `fleet help `.</pre>\r
-\r
-<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>\r
-\r
+<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 <command> [<args>]
+
+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">
category: module
slug: service-logging-in-json-with-bunyan
-<div style="float:right;margin:0 0 15px 15px;">\r
-<img class="alignnone size-full wp-image-469" title="Bunyan" src="http://nodeblog.files.wordpress.com/2012/03/bunyan.png" alt="Paul Bunyan and Babe the Blue Ox" width="240" height="320" /><br />\r
-<a href="http://www.flickr.com/photos/stublag/2876034487">Photo by Paul Carroll</a>\r
-</div>\r
-\r
-<p>Service logs are gold, if you can mine them. We scan them for occasional debugging. Perhaps we grep them looking for errors or warnings, or setup an occasional nagios log regex monitor. If that. This is a waste of the best channel for data about a service.</p>\r
-\r
-<p><a href="http://www.youtube.com/watch?v=01-2pNCZiNk">"Log. (Huh) What is it good for. Absolutely ..."</a></p>\r
-\r
-<ul>\r
-<li>debugging</li>\r
-<li>monitors tools that alert operators</li>\r
-<li>non real-time analysis (business or operational analysis)</li>\r
-<li>historical analysis</li>\r
-</ul>\r
-\r
-<p>These are what logs are good for. The current state of logging is barely adequate for the first of these. Doing reliable analysis, and even monitoring, of varied <a href="http://journal.paul.querna.org/articles/2011/12/26/log-for-machines-in-json/">"printf-style" logs</a> is a grueling or hacky task that most either don't bother with, fallback to paying someone else to do (viz. Splunk's great successes), or, for web sites, punt and use the plethora of JavaScript-based web analytics tools.</p>\r
-\r
-<p>Let's log in JSON. Let's format log records with a filter <em>outside</em> the app. Let's put more info in log records by not shoehorning into a printf-message. Debuggability can be improved. Monitoring and analysis can <em>definitely</em> be improved. Let's <em>not</em> write another regex-based parser, and use the time we've saved writing tools to collate logs from multiple nodes and services, to query structured logs (from all services, not just web servers), etc.</p>\r
-\r
-<p>At <a href="http://joyent.com">Joyent</a> we use node.js for running many core services -- loosely coupled through HTTP REST APIs and/or AMQP. In this post I'll draw on experiences from my work on Joyent's <a href="http://www.joyent.com/products/smartdatacenter/">SmartDataCenter product</a> and observations of <a href="http://www.joyentcloud.com/">Joyent Cloud</a> operations to suggest some improvements to service logging. I'll show the (open source) <strong>Bunyan logging library and tool</strong> that we're developing to improve the logging toolchain.</p>\r
-\r
-<h1 style="margin:48px 0 24px;" id="current-state-of-log-formatting">Current State of Log Formatting</h1>\r
-\r
-<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code># apache access log\r
-10.0.1.22 - - [15/Oct/2010:11:46:46 -0700] "GET /favicon.ico HTTP/1.1" 404 209\r
-fe80::6233:4bff:fe29:3173 - - [15/Oct/2010:11:46:58 -0700] "GET / HTTP/1.1" 200 44\r
-\r
-# apache error log\r
-[Fri Oct 15 11:46:46 2010] [error] [client 10.0.1.22] File does not exist: /Library/WebServer/Documents/favicon.ico\r
-[Fri Oct 15 11:46:58 2010] [error] [client fe80::6233:4bff:fe29:3173] File does not exist: /Library/WebServer/Documents/favicon.ico\r
-\r
-# Mac /var/log/secure.log\r
-Oct 14 09:20:56 banana loginwindow[41]: in pam_sm_authenticate(): Failed to determine Kerberos principal name.\r
-Oct 14 12:32:20 banana com.apple.SecurityServer[25]: UID 501 authenticated as user trentm (UID 501) for right 'system.privilege.admin'\r
-\r
-# an internal joyent agent log\r
-[2012-02-07 00:37:11.898] [INFO] AMQPAgent - Publishing success.\r
-[2012-02-07 00:37:11.910] [DEBUG] AMQPAgent - { req_id: '8afb8d99-df8e-4724-8535-3d52adaebf25',\r
- timestamp: '2012-02-07T00:37:11.898Z',\r
-\r
-# typical expressjs log output\r
-[Mon, 21 Nov 2011 20:52:11 GMT] 200 GET /foo (1ms)\r
-Blah, some other unstructured output to from a console.log call.\r
-</code></pre>\r
-\r
-<p>What're we doing here? Five logs at random. Five different date formats. As <a href="http://journal.paul.querna.org/articles/2011/12/26/log-for-machines-in-json/">Paul Querna points out</a> we haven't improved log parsability in 20 years. Parsability is enemy number one. You can't use your logs until you can parse the records, and faced with the above the inevitable solution is a one-off regular expression.</p>\r
-\r
-<p>The current state of the art is various <a href="http://search.cpan.org/~akira/Apache-ParseLog-1.02/ParseLog.pm">parsing libs</a>, <a href="http://www.webalizer.org/">analysis</a> <a href="http://awstats.sourceforge.net/">tools</a> and homebrew scripts ranging from grep to Perl, whose scope is limited to a few niches log formats.</p>\r
-\r
-<h1 style="margin:48px 0 24px;" id="json-for-logs">JSON for Logs</h1>\r
-\r
-<p><code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">JSON.parse()</code> solves all that. Let's log in JSON. But it means a change in thinking: <strong>The first-level audience for log files shouldn't be a person, but a machine.</strong></p>\r
-\r
-<p>That is not said lightly. The "Unix Way" of small focused tools lightly coupled with text output is important. JSON is less "text-y" than, e.g., Apache common log format. JSON makes <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">grep</code> and <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">awk</code> awkward. Using <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">less</code> directly on a log is handy.</p>\r
-\r
-<p>But not handy enough. That <a href="http://bit.ly/wTPlN3">80's pastel jumpsuit awkwardness</a> you're feeling isn't the JSON, it's your tools. Time to find a <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">json</code> tool -- <a href="https://github.com/trentm/json">json</a> is one, <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">bunyan</code> described below is another one. Time to learn your JSON library instead of your regex library: <a href="https://developer.mozilla.org/en/JSON">JavaScript</a>, <a href="http://docs.python.org/library/json.html">Python</a>, <a href="http://flori.github.com/json/">Ruby</a>, <a href="http://json.org/java/">Java</a>, <a href="http://search.cpan.org/~makamaka/JSON-2.53/lib/JSON.pm">Perl</a>.</p>\r
-\r
-<p>Time to burn your log4j Layout classes and move formatting to the tools side. Creating a log message with semantic information and throwing that away to make a string is silly. The win at being able to trivially parse log records is huge. The possibilities at being able to add ad hoc structured information to individual log records is interesting: think program state metrics, think feeding to Splunk, or loggly, think easy audit logs.</p>\r
-\r
-<h1 style="margin:48px 0 24px;" id="introducing-bunyan">Introducing Bunyan</h1>\r
-\r
-<p><a href="https://github.com/trentm/node-bunyan">Bunyan</a> is <strong>a node.js module for logging in JSON</strong> and <strong>a <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">bunyan</code> CLI tool</strong> to view those logs.</p>\r
-\r
-<p>Logging with Bunyan basically looks like this:</p>\r
-\r
-<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code>$ cat hi.js\r
-var Logger = require('bunyan');\r
-var log = new Logger({name: 'hello' /*, ... */});\r
-log.info("hi %s", "paul");\r
-</code></pre>\r
-\r
-<p>And you'll get a log record like this:</p>\r
-\r
-<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code>$ node hi.js\r
-{"name":"hello","hostname":"banana.local","pid":40026,"level":30,"msg":"hi paul","time":"2012-03-28T17:25:37.050Z","v":0}\r
-</code></pre>\r
-\r
-<p>Pipe that through the <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">bunyan</code> tool that is part of the "node-bunyan" install to get more readable output:</p>\r
-\r
-<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code>$ node hi.js | ./node_modules/.bin/bunyan # formatted text output\r
-[2012-02-07T18:50:18.003Z] INFO: hello/40026 on banana.local: hi paul\r
-\r
-$ node hi.js | ./node_modules/.bin/bunyan -j # indented JSON output\r
-{\r
- "name": "hello",\r
- "hostname": "banana.local",\r
- "pid": 40087,\r
- "level": 30,\r
- "msg": "hi paul",\r
- "time": "2012-03-28T17:26:38.431Z",\r
- "v": 0\r
-}\r
-</code></pre>\r
-\r
-<p>Bunyan is log4j-like: create a Logger with a name, call <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">log.info(...)</code>, etc. However it has no intention of reproducing much of the functionality of log4j. IMO, much of that is overkill for the types of services you'll tend to be writing with node.js.</p>\r
-\r
-<h1 style="margin:48px 0 24px;" id="longer-bunyan-example">Longer Bunyan Example</h1>\r
-\r
-<p>Let's walk through a bigger example to show some interesting things in Bunyan. We'll create a very small "Hello API" server using the excellent <a href="https://github.com/mcavage/node-restify">restify</a> library -- which we used heavily here at <a href="http://joyent.com">Joyent</a>. (Bunyan doesn't require restify at all, you can easily use Bunyan with <a href="http://expressjs.com/">Express</a> or whatever.)</p>\r
-\r
-<p><em>You can follow along in <a href="https://github.com/trentm/hello-json-logging">https://github.com/trentm/hello-json-logging</a> if you like. Note that I'm using the current HEAD of the bunyan and restify trees here, so details might change a bit. Prerequisite: a node 0.6.x installation.</em></p>\r
-\r
-<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code>git clone https://github.com/trentm/hello-json-logging.git\r
-cd hello-json-logging\r
-make\r
-</code></pre>\r
-\r
-<h2 id="bunyan-logger">Bunyan Logger</h2>\r
-\r
-<p>Our <a href="https://github.com/trentm/hello-json-logging/blob/master/server.js">server</a> first creates a Bunyan logger:</p>\r
-\r
-<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code>var Logger = require('bunyan');\r
-var log = new Logger({\r
- name: 'helloapi',\r
- streams: [\r
- {\r
- stream: process.stdout,\r
- level: 'debug'\r
- },\r
- {\r
- path: 'hello.log',\r
- level: 'trace'\r
- }\r
- ],\r
- serializers: {\r
- req: Logger.stdSerializers.req,\r
- res: restify.bunyan.serializers.response,\r
- },\r
-});\r
-</code></pre>\r
-\r
-<p>Every Bunyan logger must have a <strong>name</strong>. Unlike log4j, this is not a hierarchical dotted namespace. It is just a name field for the log records.</p>\r
-\r
-<p>Every Bunyan logger has one or more <strong>streams</strong>, to which log records are written. Here we've defined two: logging at DEBUG level and above is written to stdout, and logging at TRACE and above is appended to 'hello.log'.</p>\r
-\r
-<p>Bunyan has the concept of <strong>serializers</strong>: a registry of functions that know how to convert a JavaScript object for a certain log record field to a nice JSON representation for logging. For example, here we register the <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">Logger.stdSerializers.req</code> function to convert HTTP Request objects (using the field name "req") to JSON. More on serializers later.</p>\r
-\r
-<h2 id="restify-server">Restify Server</h2>\r
-\r
-<p>Restify 1.x and above has bunyan support baked in. You pass in your Bunyan logger like this:</p>\r
-\r
-<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code>var server = restify.createServer({\r
- name: 'Hello API',\r
- log: log // Pass our logger to restify.\r
-});\r
-</code></pre>\r
-\r
-<p>Our simple API will have a single <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">GET /hello?name=NAME</code> endpoint:</p>\r
-\r
-<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code>server.get({path: '/hello', name: 'SayHello'}, function(req, res, next) {\r
- var caller = req.params.name || 'caller';\r
- req.log.debug('caller is "%s"', caller);\r
- res.send({"hello": caller});\r
- return next();\r
-});\r
-</code></pre>\r
-\r
-<p>If we run that, <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">node server.js</code>, and call the endpoint, we get the expected restify response:</p>\r
-\r
-<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code>$ curl -iSs http://0.0.0.0:8080/hello?name=paul\r
-HTTP/1.1 200 OK\r
-Access-Control-Allow-Origin: *\r
-Access-Control-Allow-Headers: Accept, Accept-Version, Content-Length, Content-MD5, Content-Type, Date, X-Api-Version\r
-Access-Control-Expose-Headers: X-Api-Version, X-Request-Id, X-Response-Time\r
-Server: Hello API\r
-X-Request-Id: f6aaf942-c60d-4c72-8ddd-bada459db5e3\r
-Access-Control-Allow-Methods: GET\r
-Connection: close\r
-Content-Length: 16\r
-Content-MD5: Xmn3QcFXaIaKw9RPUARGBA==\r
-Content-Type: application/json\r
-Date: Tue, 07 Feb 2012 19:12:35 GMT\r
-X-Response-Time: 4\r
-\r
-{"hello":"paul"}\r
-</code></pre>\r
-\r
-<h2 id="setup-server-logging">Setup Server Logging</h2>\r
-\r
-<p>Let's add two things to our server. First, we'll use the <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">server.pre</code> to hook into restify's request handling before routing where we'll <strong>log the request</strong>.</p>\r
-\r
-<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code>server.pre(function (request, response, next) {\r
- request.log.info({req: request}, 'start'); // (1)\r
- return next();\r
-});\r
-</code></pre>\r
-\r
-<p>This is the first time we've seen this <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">log.info</code> style with an object as the first argument. Bunyan logging methods (<code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">log.trace</code>, <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">log.debug</code>, ...) all support an optional <strong>first object argument with extra log record fields</strong>:</p>\r
-\r
-<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code>log.info(<object> fields, <string> msg, ...)\r
-</code></pre>\r
-\r
-<p>Here we pass in the restify Request object, <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">req</code>. The "req" serializer we registered above will come into play here, but bear with me.</p>\r
-\r
-<p>Remember that we already had this debug log statement in our endpoint handler:</p>\r
-\r
-<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code>req.log.debug('caller is "%s"', caller); // (2)\r
-</code></pre>\r
-\r
-<p>Second, use the restify server <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">after</code> event to <strong>log the response</strong>:</p>\r
-\r
-<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code>server.on('after', function (req, res, route) {\r
- req.log.info({res: res}, "finished"); // (3)\r
-});\r
-</code></pre>\r
-\r
-<h2 id="log-output">Log Output</h2>\r
-\r
-<p>Now lets see what log output we get when somebody hits our API's endpoint:</p>\r
-\r
-<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code>$ curl -iSs http://0.0.0.0:8080/hello?name=paul\r
-HTTP/1.1 200 OK\r
-...\r
-X-Request-Id: 9496dfdd-4ec7-4b59-aae7-3fed57aed5ba\r
-...\r
-\r
-{"hello":"paul"}\r
-</code></pre>\r
-\r
-<p>Here is the server log:</p>\r
-\r
-<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code>[trentm@banana:~/tm/hello-json-logging]$ node server.js\r
-... intro "listening at" log message elided ...\r
-{"name":"helloapi","hostname":"banana.local","pid":40341,"level":30,"req":{"method":"GET","url":"/hello?name=paul","headers":{"user-agent":"curl/7.19.7 (universal-apple-darwin10.0) libcurl/7.19.7 OpenSSL/0.9.8r zlib/1.2.3","host":"0.0.0.0:8080","accept":"*/*"},"remoteAddress":"127.0.0.1","remotePort":59831},"msg":"start","time":"2012-03-28T17:37:29.506Z","v":0}\r
-{"name":"helloapi","hostname":"banana.local","pid":40341,"route":"SayHello","req_id":"9496dfdd-4ec7-4b59-aae7-3fed57aed5ba","level":20,"msg":"caller is \"paul\"","time":"2012-03-28T17:37:29.507Z","v":0}\r
-{"name":"helloapi","hostname":"banana.local","pid":40341,"route":"SayHello","req_id":"9496dfdd-4ec7-4b59-aae7-3fed57aed5ba","level":30,"res":{"statusCode":200,"headers":{"access-control-allow-origin":"*","access-control-allow-headers":"Accept, Accept-Version, Content-Length, Content-MD5, Content-Type, Date, X-Api-Version","access-control-expose-headers":"X-Api-Version, X-Request-Id, X-Response-Time","server":"Hello API","x-request-id":"9496dfdd-4ec7-4b59-aae7-3fed57aed5ba","access-control-allow-methods":"GET","connection":"close","content-length":16,"content-md5":"Xmn3QcFXaIaKw9RPUARGBA==","content-type":"application/json","date":"Wed, 28 Mar 2012 17:37:29 GMT","x-response-time":3}},"msg":"finished","time":"2012-03-28T17:37:29.510Z","v":0}\r
-</code></pre>\r
-\r
-<p>Lets look at each in turn to see what is interesting -- pretty-printed with <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">node server.js | ./node_modules/.bin/bunyan -j</code>:</p>\r
-\r
-<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code>{ // (1)\r
- "name": "helloapi",\r
- "hostname": "banana.local",\r
- "pid": 40442,\r
- "level": 30,\r
- "req": {\r
- "method": "GET",\r
- "url": "/hello?name=paul",\r
- "headers": {\r
- "user-agent": "curl/7.19.7 (universal-apple-darwin10.0) libcurl/7.19.7 OpenSSL/0.9.8r zlib/1.2.3",\r
- "host": "0.0.0.0:8080",\r
- "accept": "*/*"\r
- },\r
- "remoteAddress": "127.0.0.1",\r
- "remotePort": 59834\r
- },\r
- "msg": "start",\r
- "time": "2012-03-28T17:39:44.880Z",\r
- "v": 0\r
-}\r
-</code></pre>\r
-\r
-<p>Here we logged the incoming request with <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">request.log.info({req: request}, 'start')</code>. The use of the "req" field triggers the <a href="https://github.com/trentm/node-bunyan/blob/master/lib/bunyan.js#L857-870">"req" serializer</a> <a href="https://github.com/trentm/hello-json-logging/blob/master/server.js#L24">registered at Logger creation</a>.</p>\r
-\r
-<p>Next the <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">req.log.debug</code> in our handler:</p>\r
-\r
-<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code>{ // (2)\r
- "name": "helloapi",\r
- "hostname": "banana.local",\r
- "pid": 40442,\r
- "route": "SayHello",\r
- "req_id": "9496dfdd-4ec7-4b59-aae7-3fed57aed5ba",\r
- "level": 20,\r
- "msg": "caller is \"paul\"",\r
- "time": "2012-03-28T17:39:44.883Z",\r
- "v": 0\r
-}\r
-</code></pre>\r
-\r
-<p>and the log of response in the "after" event:</p>\r
-\r
-<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code>{ // (3)\r
- "name": "helloapi",\r
- "hostname": "banana.local",\r
- "pid": 40442,\r
- "route": "SayHello",\r
- "req_id": "9496dfdd-4ec7-4b59-aae7-3fed57aed5ba",\r
- "level": 30,\r
- "res": {\r
- "statusCode": 200,\r
- "headers": {\r
- "access-control-allow-origin": "*",\r
- "access-control-allow-headers": "Accept, Accept-Version, Content-Length, Content-MD5, Content-Type, Date, X-Api-Version",\r
- "access-control-expose-headers": "X-Api-Version, X-Request-Id, X-Response-Time",\r
- "server": "Hello API",\r
- "x-request-id": "9496dfdd-4ec7-4b59-aae7-3fed57aed5ba",\r
- "access-control-allow-methods": "GET",\r
- "connection": "close",\r
- "content-length": 16,\r
- "content-md5": "Xmn3QcFXaIaKw9RPUARGBA==",\r
- "content-type": "application/json",\r
- "date": "Wed, 28 Mar 2012 17:39:44 GMT",\r
- "x-response-time": 5\r
- }\r
- },\r
- "msg": "finished",\r
- "time": "2012-03-28T17:39:44.886Z",\r
- "v": 0\r
-}\r
-</code></pre>\r
-\r
-<p>Two useful details of note here:</p>\r
-\r
-<ol>\r
-<li><p>The last two log messages include <strong>a "req_id" field</strong> (added to the <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">req.log</code> logger by restify). Note that this is the same UUID as the "X-Request-Id" header in the <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">curl</code> response. This means that if you use <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">req.log</code> for logging in your API handlers you will get an easy way to collate all logging for particular requests.</p>\r
-\r
-<p>If your's is an SOA system with many services, a best practice is to carry that X-Request-Id/req_id through your system to enable collating handling of a single top-level request.</p></li>\r
-<li><p>The last two log messages include <strong>a "route" field</strong>. This tells you to which handler restify routed the request. While possibly useful for debugging, this can be very helpful for log-based monitoring of endpoints on a server.</p></li>\r
-</ol>\r
-\r
-<p>Recall that we also setup all logging to go the "hello.log" file. This was set at the TRACE level. Restify will log more detail of its operation at the trace level. See <a href="https://gist.github.com/1761772">my "hello.log"</a> for an example. The <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">bunyan</code> tool does a decent job of <a href="https://gist.github.com/1761772#file_2.+cat+hello.log+pipe+bunyan">nicely formatting</a> multiline messages and "req"/"res" keys (with color, not shown in the gist).</p>\r
-\r
-<p><em>This</em> is logging you can use effectively.</p>\r
-\r
-<h1 style="margin:48px 0 24px;" id="other-tools">Other Tools</h1>\r
-\r
-<p>Bunyan is just one of many options for logging in node.js-land. Others (that I know of) supporting JSON logging are <a href="https://github.com/flatiron/winston#readme">winston</a> and <a href="https://github.com/pquerna/node-logmagic/">logmagic</a>. Paul Querna has <a href="http://journal.paul.querna.org/articles/2011/12/26/log-for-machines-in-json/">an excellent post on using JSON for logging</a>, which shows logmagic usage and also touches on topics like the GELF logging format, log transporting, indexing and searching.</p>\r
-\r
-<h1 style="margin:48px 0 24px;" id="final-thoughts">Final Thoughts</h1>\r
-\r
-<p>Parsing challenges won't ever completely go away, but it can for your logs if you use JSON. Collating log records across logs from multiple nodes is facilitated by a common "time" field. Correlating logging across multiple services is enabled by carrying a common "req_id" (or equivalent) through all such logs.</p>\r
-\r
-<p>Separate log files for a single service is an anti-pattern. The typical Apache example of separate access and error logs is legacy, not an example to follow. A JSON log provides the structure necessary for tooling to easily filter for log records of a particular type.</p>\r
-\r
-<p>JSON logs bring possibilities. Feeding to tools like Splunk becomes easy. Ad hoc fields allow for a lightly spec'd comm channel from apps to other services: records with a "metric" could feed to <a href="http://codeascraft.etsy.com/2011/02/15/measure-anything-measure-everything/">statsd</a>, records with a "loggly: true" could feed to loggly.com.</p>\r
-\r
-<p>Here I've described a very simple example of restify and bunyan usage for node.js-based API services with easy JSON logging. Restify provides a powerful framework for robust API services. Bunyan provides a light API for nice JSON logging and the beginnings of tooling to help consume Bunyan JSON logs.</p>\r
-\r
+<div style="float:right;margin:0 0 15px 15px;">
+<img class="alignnone size-full wp-image-469" title="Bunyan" src="http://nodeblog.files.wordpress.com/2012/03/bunyan.png" alt="Paul Bunyan and Babe the Blue Ox" width="240" height="320" /><br />
+<a href="http://www.flickr.com/photos/stublag/2876034487">Photo by Paul Carroll</a>
+</div>
+
+<p>Service logs are gold, if you can mine them. We scan them for occasional debugging. Perhaps we grep them looking for errors or warnings, or setup an occasional nagios log regex monitor. If that. This is a waste of the best channel for data about a service.</p>
+
+<p><a href="http://www.youtube.com/watch?v=01-2pNCZiNk">"Log. (Huh) What is it good for. Absolutely ..."</a></p>
+
+<ul>
+<li>debugging</li>
+<li>monitors tools that alert operators</li>
+<li>non real-time analysis (business or operational analysis)</li>
+<li>historical analysis</li>
+</ul>
+
+<p>These are what logs are good for. The current state of logging is barely adequate for the first of these. Doing reliable analysis, and even monitoring, of varied <a href="http://journal.paul.querna.org/articles/2011/12/26/log-for-machines-in-json/">"printf-style" logs</a> is a grueling or hacky task that most either don't bother with, fallback to paying someone else to do (viz. Splunk's great successes), or, for web sites, punt and use the plethora of JavaScript-based web analytics tools.</p>
+
+<p>Let's log in JSON. Let's format log records with a filter <em>outside</em> the app. Let's put more info in log records by not shoehorning into a printf-message. Debuggability can be improved. Monitoring and analysis can <em>definitely</em> be improved. Let's <em>not</em> write another regex-based parser, and use the time we've saved writing tools to collate logs from multiple nodes and services, to query structured logs (from all services, not just web servers), etc.</p>
+
+<p>At <a href="http://joyent.com">Joyent</a> we use node.js for running many core services -- loosely coupled through HTTP REST APIs and/or AMQP. In this post I'll draw on experiences from my work on Joyent's <a href="http://www.joyent.com/products/smartdatacenter/">SmartDataCenter product</a> and observations of <a href="http://www.joyentcloud.com/">Joyent Cloud</a> operations to suggest some improvements to service logging. I'll show the (open source) <strong>Bunyan logging library and tool</strong> that we're developing to improve the logging toolchain.</p>
+
+<h1 style="margin:48px 0 24px;" id="current-state-of-log-formatting">Current State of Log Formatting</h1>
+
+<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code># apache access log
+10.0.1.22 - - [15/Oct/2010:11:46:46 -0700] "GET /favicon.ico HTTP/1.1" 404 209
+fe80::6233:4bff:fe29:3173 - - [15/Oct/2010:11:46:58 -0700] "GET / HTTP/1.1" 200 44
+
+# apache error log
+[Fri Oct 15 11:46:46 2010] [error] [client 10.0.1.22] File does not exist: /Library/WebServer/Documents/favicon.ico
+[Fri Oct 15 11:46:58 2010] [error] [client fe80::6233:4bff:fe29:3173] File does not exist: /Library/WebServer/Documents/favicon.ico
+
+# Mac /var/log/secure.log
+Oct 14 09:20:56 banana loginwindow[41]: in pam_sm_authenticate(): Failed to determine Kerberos principal name.
+Oct 14 12:32:20 banana com.apple.SecurityServer[25]: UID 501 authenticated as user trentm (UID 501) for right 'system.privilege.admin'
+
+# an internal joyent agent log
+[2012-02-07 00:37:11.898] [INFO] AMQPAgent - Publishing success.
+[2012-02-07 00:37:11.910] [DEBUG] AMQPAgent - { req_id: '8afb8d99-df8e-4724-8535-3d52adaebf25',
+ timestamp: '2012-02-07T00:37:11.898Z',
+
+# typical expressjs log output
+[Mon, 21 Nov 2011 20:52:11 GMT] 200 GET /foo (1ms)
+Blah, some other unstructured output to from a console.log call.
+</code></pre>
+
+<p>What're we doing here? Five logs at random. Five different date formats. As <a href="http://journal.paul.querna.org/articles/2011/12/26/log-for-machines-in-json/">Paul Querna points out</a> we haven't improved log parsability in 20 years. Parsability is enemy number one. You can't use your logs until you can parse the records, and faced with the above the inevitable solution is a one-off regular expression.</p>
+
+<p>The current state of the art is various <a href="http://search.cpan.org/~akira/Apache-ParseLog-1.02/ParseLog.pm">parsing libs</a>, <a href="http://www.webalizer.org/">analysis</a> <a href="http://awstats.sourceforge.net/">tools</a> and homebrew scripts ranging from grep to Perl, whose scope is limited to a few niches log formats.</p>
+
+<h1 style="margin:48px 0 24px;" id="json-for-logs">JSON for Logs</h1>
+
+<p><code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">JSON.parse()</code> solves all that. Let's log in JSON. But it means a change in thinking: <strong>The first-level audience for log files shouldn't be a person, but a machine.</strong></p>
+
+<p>That is not said lightly. The "Unix Way" of small focused tools lightly coupled with text output is important. JSON is less "text-y" than, e.g., Apache common log format. JSON makes <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">grep</code> and <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">awk</code> awkward. Using <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">less</code> directly on a log is handy.</p>
+
+<p>But not handy enough. That <a href="http://bit.ly/wTPlN3">80's pastel jumpsuit awkwardness</a> you're feeling isn't the JSON, it's your tools. Time to find a <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">json</code> tool -- <a href="https://github.com/trentm/json">json</a> is one, <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">bunyan</code> described below is another one. Time to learn your JSON library instead of your regex library: <a href="https://developer.mozilla.org/en/JSON">JavaScript</a>, <a href="http://docs.python.org/library/json.html">Python</a>, <a href="http://flori.github.com/json/">Ruby</a>, <a href="http://json.org/java/">Java</a>, <a href="http://search.cpan.org/~makamaka/JSON-2.53/lib/JSON.pm">Perl</a>.</p>
+
+<p>Time to burn your log4j Layout classes and move formatting to the tools side. Creating a log message with semantic information and throwing that away to make a string is silly. The win at being able to trivially parse log records is huge. The possibilities at being able to add ad hoc structured information to individual log records is interesting: think program state metrics, think feeding to Splunk, or loggly, think easy audit logs.</p>
+
+<h1 style="margin:48px 0 24px;" id="introducing-bunyan">Introducing Bunyan</h1>
+
+<p><a href="https://github.com/trentm/node-bunyan">Bunyan</a> is <strong>a node.js module for logging in JSON</strong> and <strong>a <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">bunyan</code> CLI tool</strong> to view those logs.</p>
+
+<p>Logging with Bunyan basically looks like this:</p>
+
+<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code>$ cat hi.js
+var Logger = require('bunyan');
+var log = new Logger({name: 'hello' /*, ... */});
+log.info("hi %s", "paul");
+</code></pre>
+
+<p>And you'll get a log record like this:</p>
+
+<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code>$ node hi.js
+{"name":"hello","hostname":"banana.local","pid":40026,"level":30,"msg":"hi paul","time":"2012-03-28T17:25:37.050Z","v":0}
+</code></pre>
+
+<p>Pipe that through the <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">bunyan</code> tool that is part of the "node-bunyan" install to get more readable output:</p>
+
+<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code>$ node hi.js | ./node_modules/.bin/bunyan # formatted text output
+[2012-02-07T18:50:18.003Z] INFO: hello/40026 on banana.local: hi paul
+
+$ node hi.js | ./node_modules/.bin/bunyan -j # indented JSON output
+{
+ "name": "hello",
+ "hostname": "banana.local",
+ "pid": 40087,
+ "level": 30,
+ "msg": "hi paul",
+ "time": "2012-03-28T17:26:38.431Z",
+ "v": 0
+}
+</code></pre>
+
+<p>Bunyan is log4j-like: create a Logger with a name, call <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">log.info(...)</code>, etc. However it has no intention of reproducing much of the functionality of log4j. IMO, much of that is overkill for the types of services you'll tend to be writing with node.js.</p>
+
+<h1 style="margin:48px 0 24px;" id="longer-bunyan-example">Longer Bunyan Example</h1>
+
+<p>Let's walk through a bigger example to show some interesting things in Bunyan. We'll create a very small "Hello API" server using the excellent <a href="https://github.com/mcavage/node-restify">restify</a> library -- which we used heavily here at <a href="http://joyent.com">Joyent</a>. (Bunyan doesn't require restify at all, you can easily use Bunyan with <a href="http://expressjs.com/">Express</a> or whatever.)</p>
+
+<p><em>You can follow along in <a href="https://github.com/trentm/hello-json-logging">https://github.com/trentm/hello-json-logging</a> if you like. Note that I'm using the current HEAD of the bunyan and restify trees here, so details might change a bit. Prerequisite: a node 0.6.x installation.</em></p>
+
+<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code>git clone https://github.com/trentm/hello-json-logging.git
+cd hello-json-logging
+make
+</code></pre>
+
+<h2 id="bunyan-logger">Bunyan Logger</h2>
+
+<p>Our <a href="https://github.com/trentm/hello-json-logging/blob/master/server.js">server</a> first creates a Bunyan logger:</p>
+
+<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code>var Logger = require('bunyan');
+var log = new Logger({
+ name: 'helloapi',
+ streams: [
+ {
+ stream: process.stdout,
+ level: 'debug'
+ },
+ {
+ path: 'hello.log',
+ level: 'trace'
+ }
+ ],
+ serializers: {
+ req: Logger.stdSerializers.req,
+ res: restify.bunyan.serializers.response,
+ },
+});
+</code></pre>
+
+<p>Every Bunyan logger must have a <strong>name</strong>. Unlike log4j, this is not a hierarchical dotted namespace. It is just a name field for the log records.</p>
+
+<p>Every Bunyan logger has one or more <strong>streams</strong>, to which log records are written. Here we've defined two: logging at DEBUG level and above is written to stdout, and logging at TRACE and above is appended to 'hello.log'.</p>
+
+<p>Bunyan has the concept of <strong>serializers</strong>: a registry of functions that know how to convert a JavaScript object for a certain log record field to a nice JSON representation for logging. For example, here we register the <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">Logger.stdSerializers.req</code> function to convert HTTP Request objects (using the field name "req") to JSON. More on serializers later.</p>
+
+<h2 id="restify-server">Restify Server</h2>
+
+<p>Restify 1.x and above has bunyan support baked in. You pass in your Bunyan logger like this:</p>
+
+<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code>var server = restify.createServer({
+ name: 'Hello API',
+ log: log // Pass our logger to restify.
+});
+</code></pre>
+
+<p>Our simple API will have a single <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">GET /hello?name=NAME</code> endpoint:</p>
+
+<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code>server.get({path: '/hello', name: 'SayHello'}, function(req, res, next) {
+ var caller = req.params.name || 'caller';
+ req.log.debug('caller is "%s"', caller);
+ res.send({"hello": caller});
+ return next();
+});
+</code></pre>
+
+<p>If we run that, <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">node server.js</code>, and call the endpoint, we get the expected restify response:</p>
+
+<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code>$ curl -iSs http://0.0.0.0:8080/hello?name=paul
+HTTP/1.1 200 OK
+Access-Control-Allow-Origin: *
+Access-Control-Allow-Headers: Accept, Accept-Version, Content-Length, Content-MD5, Content-Type, Date, X-Api-Version
+Access-Control-Expose-Headers: X-Api-Version, X-Request-Id, X-Response-Time
+Server: Hello API
+X-Request-Id: f6aaf942-c60d-4c72-8ddd-bada459db5e3
+Access-Control-Allow-Methods: GET
+Connection: close
+Content-Length: 16
+Content-MD5: Xmn3QcFXaIaKw9RPUARGBA==
+Content-Type: application/json
+Date: Tue, 07 Feb 2012 19:12:35 GMT
+X-Response-Time: 4
+
+{"hello":"paul"}
+</code></pre>
+
+<h2 id="setup-server-logging">Setup Server Logging</h2>
+
+<p>Let's add two things to our server. First, we'll use the <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">server.pre</code> to hook into restify's request handling before routing where we'll <strong>log the request</strong>.</p>
+
+<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code>server.pre(function (request, response, next) {
+ request.log.info({req: request}, 'start'); // (1)
+ return next();
+});
+</code></pre>
+
+<p>This is the first time we've seen this <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">log.info</code> style with an object as the first argument. Bunyan logging methods (<code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">log.trace</code>, <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">log.debug</code>, ...) all support an optional <strong>first object argument with extra log record fields</strong>:</p>
+
+<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code>log.info(<object> fields, <string> msg, ...)
+</code></pre>
+
+<p>Here we pass in the restify Request object, <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">req</code>. The "req" serializer we registered above will come into play here, but bear with me.</p>
+
+<p>Remember that we already had this debug log statement in our endpoint handler:</p>
+
+<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code>req.log.debug('caller is "%s"', caller); // (2)
+</code></pre>
+
+<p>Second, use the restify server <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">after</code> event to <strong>log the response</strong>:</p>
+
+<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code>server.on('after', function (req, res, route) {
+ req.log.info({res: res}, "finished"); // (3)
+});
+</code></pre>
+
+<h2 id="log-output">Log Output</h2>
+
+<p>Now lets see what log output we get when somebody hits our API's endpoint:</p>
+
+<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code>$ curl -iSs http://0.0.0.0:8080/hello?name=paul
+HTTP/1.1 200 OK
+...
+X-Request-Id: 9496dfdd-4ec7-4b59-aae7-3fed57aed5ba
+...
+
+{"hello":"paul"}
+</code></pre>
+
+<p>Here is the server log:</p>
+
+<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code>[trentm@banana:~/tm/hello-json-logging]$ node server.js
+... intro "listening at" log message elided ...
+{"name":"helloapi","hostname":"banana.local","pid":40341,"level":30,"req":{"method":"GET","url":"/hello?name=paul","headers":{"user-agent":"curl/7.19.7 (universal-apple-darwin10.0) libcurl/7.19.7 OpenSSL/0.9.8r zlib/1.2.3","host":"0.0.0.0:8080","accept":"*/*"},"remoteAddress":"127.0.0.1","remotePort":59831},"msg":"start","time":"2012-03-28T17:37:29.506Z","v":0}
+{"name":"helloapi","hostname":"banana.local","pid":40341,"route":"SayHello","req_id":"9496dfdd-4ec7-4b59-aae7-3fed57aed5ba","level":20,"msg":"caller is \"paul\"","time":"2012-03-28T17:37:29.507Z","v":0}
+{"name":"helloapi","hostname":"banana.local","pid":40341,"route":"SayHello","req_id":"9496dfdd-4ec7-4b59-aae7-3fed57aed5ba","level":30,"res":{"statusCode":200,"headers":{"access-control-allow-origin":"*","access-control-allow-headers":"Accept, Accept-Version, Content-Length, Content-MD5, Content-Type, Date, X-Api-Version","access-control-expose-headers":"X-Api-Version, X-Request-Id, X-Response-Time","server":"Hello API","x-request-id":"9496dfdd-4ec7-4b59-aae7-3fed57aed5ba","access-control-allow-methods":"GET","connection":"close","content-length":16,"content-md5":"Xmn3QcFXaIaKw9RPUARGBA==","content-type":"application/json","date":"Wed, 28 Mar 2012 17:37:29 GMT","x-response-time":3}},"msg":"finished","time":"2012-03-28T17:37:29.510Z","v":0}
+</code></pre>
+
+<p>Lets look at each in turn to see what is interesting -- pretty-printed with <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">node server.js | ./node_modules/.bin/bunyan -j</code>:</p>
+
+<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code>{ // (1)
+ "name": "helloapi",
+ "hostname": "banana.local",
+ "pid": 40442,
+ "level": 30,
+ "req": {
+ "method": "GET",
+ "url": "/hello?name=paul",
+ "headers": {
+ "user-agent": "curl/7.19.7 (universal-apple-darwin10.0) libcurl/7.19.7 OpenSSL/0.9.8r zlib/1.2.3",
+ "host": "0.0.0.0:8080",
+ "accept": "*/*"
+ },
+ "remoteAddress": "127.0.0.1",
+ "remotePort": 59834
+ },
+ "msg": "start",
+ "time": "2012-03-28T17:39:44.880Z",
+ "v": 0
+}
+</code></pre>
+
+<p>Here we logged the incoming request with <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">request.log.info({req: request}, 'start')</code>. The use of the "req" field triggers the <a href="https://github.com/trentm/node-bunyan/blob/master/lib/bunyan.js#L857-870">"req" serializer</a> <a href="https://github.com/trentm/hello-json-logging/blob/master/server.js#L24">registered at Logger creation</a>.</p>
+
+<p>Next the <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">req.log.debug</code> in our handler:</p>
+
+<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code>{ // (2)
+ "name": "helloapi",
+ "hostname": "banana.local",
+ "pid": 40442,
+ "route": "SayHello",
+ "req_id": "9496dfdd-4ec7-4b59-aae7-3fed57aed5ba",
+ "level": 20,
+ "msg": "caller is \"paul\"",
+ "time": "2012-03-28T17:39:44.883Z",
+ "v": 0
+}
+</code></pre>
+
+<p>and the log of response in the "after" event:</p>
+
+<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code>{ // (3)
+ "name": "helloapi",
+ "hostname": "banana.local",
+ "pid": 40442,
+ "route": "SayHello",
+ "req_id": "9496dfdd-4ec7-4b59-aae7-3fed57aed5ba",
+ "level": 30,
+ "res": {
+ "statusCode": 200,
+ "headers": {
+ "access-control-allow-origin": "*",
+ "access-control-allow-headers": "Accept, Accept-Version, Content-Length, Content-MD5, Content-Type, Date, X-Api-Version",
+ "access-control-expose-headers": "X-Api-Version, X-Request-Id, X-Response-Time",
+ "server": "Hello API",
+ "x-request-id": "9496dfdd-4ec7-4b59-aae7-3fed57aed5ba",
+ "access-control-allow-methods": "GET",
+ "connection": "close",
+ "content-length": 16,
+ "content-md5": "Xmn3QcFXaIaKw9RPUARGBA==",
+ "content-type": "application/json",
+ "date": "Wed, 28 Mar 2012 17:39:44 GMT",
+ "x-response-time": 5
+ }
+ },
+ "msg": "finished",
+ "time": "2012-03-28T17:39:44.886Z",
+ "v": 0
+}
+</code></pre>
+
+<p>Two useful details of note here:</p>
+
+<ol>
+<li><p>The last two log messages include <strong>a "req_id" field</strong> (added to the <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">req.log</code> logger by restify). Note that this is the same UUID as the "X-Request-Id" header in the <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">curl</code> response. This means that if you use <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">req.log</code> for logging in your API handlers you will get an easy way to collate all logging for particular requests.</p>
+
+<p>If your's is an SOA system with many services, a best practice is to carry that X-Request-Id/req_id through your system to enable collating handling of a single top-level request.</p></li>
+<li><p>The last two log messages include <strong>a "route" field</strong>. This tells you to which handler restify routed the request. While possibly useful for debugging, this can be very helpful for log-based monitoring of endpoints on a server.</p></li>
+</ol>
+
+<p>Recall that we also setup all logging to go the "hello.log" file. This was set at the TRACE level. Restify will log more detail of its operation at the trace level. See <a href="https://gist.github.com/1761772">my "hello.log"</a> for an example. The <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">bunyan</code> tool does a decent job of <a href="https://gist.github.com/1761772#file_2.+cat+hello.log+pipe+bunyan">nicely formatting</a> multiline messages and "req"/"res" keys (with color, not shown in the gist).</p>
+
+<p><em>This</em> is logging you can use effectively.</p>
+
+<h1 style="margin:48px 0 24px;" id="other-tools">Other Tools</h1>
+
+<p>Bunyan is just one of many options for logging in node.js-land. Others (that I know of) supporting JSON logging are <a href="https://github.com/flatiron/winston#readme">winston</a> and <a href="https://github.com/pquerna/node-logmagic/">logmagic</a>. Paul Querna has <a href="http://journal.paul.querna.org/articles/2011/12/26/log-for-machines-in-json/">an excellent post on using JSON for logging</a>, which shows logmagic usage and also touches on topics like the GELF logging format, log transporting, indexing and searching.</p>
+
+<h1 style="margin:48px 0 24px;" id="final-thoughts">Final Thoughts</h1>
+
+<p>Parsing challenges won't ever completely go away, but it can for your logs if you use JSON. Collating log records across logs from multiple nodes is facilitated by a common "time" field. Correlating logging across multiple services is enabled by carrying a common "req_id" (or equivalent) through all such logs.</p>
+
+<p>Separate log files for a single service is an anti-pattern. The typical Apache example of separate access and error logs is legacy, not an example to follow. A JSON log provides the structure necessary for tooling to easily filter for log records of a particular type.</p>
+
+<p>JSON logs bring possibilities. Feeding to tools like Splunk becomes easy. Ad hoc fields allow for a lightly spec'd comm channel from apps to other services: records with a "metric" could feed to <a href="http://codeascraft.etsy.com/2011/02/15/measure-anything-measure-everything/">statsd</a>, records with a "loggly: true" could feed to loggly.com.</p>
+
+<p>Here I've described a very simple example of restify and bunyan usage for node.js-based API services with easy JSON logging. Restify provides a powerful framework for robust API services. Bunyan provides a light API for nice JSON logging and the beginnings of tooling to help consume Bunyan JSON logs.</p>
+
<p><strong>Update (29-Mar-2012):</strong> Fix styles somewhat for RSS readers.</p>
<p style="float:right;text-align:center;margin:5px;"><a href="http://www.flickr.com/photos/luc_viatour/4247957432/"><img class="size-medium wp-image-652" style="border:1px #000000 solid;" title="Web" src="http://dtrace.org/blogs/dap/files/2012/02/web-300x300.jpg" alt="" width="250" height="250" /></a><br>
Photo by Luc Viatour (flickr)</p>
-<p>Managing dependencies is a fundamental problem in building complex software. The terrific success of github and <a href="http://npmjs.org/">npm</a> have made code reuse especially easy in the Node world, where packages don't exist in isolation but rather as nodes in a large graph. The software is constantly changing (releasing new versions), and each package has its own constraints about what other packages it requires to run (dependencies). npm keeps track of these constraints, and authors express what kind of changes are compatible using <a href="http://npmjs.org/doc/semver.html">semantic versioning</a>, allowing authors to specify that their package will work with even future versions of its dependencies as long as the semantic versions are assigned properly.\r
-\r
-</p>\r
-<p>This does mean that when you "npm install" a package with dependencies, there's no guarantee that you'll get the same set of code now that you would have gotten an hour ago, or that you would get if you were to run it again an hour later. You may get a bunch of bug fixes now that weren't available an hour ago. This is great during development, where you want to keep up with changes upstream. It's not necessarily what you want for deployment, though, where you want to validate whatever bits you're actually shipping.\r
-\r
-</p>\r
-<p>Put differently, <strong>it's understood that all software changes incur some risk, and it's critical to be able to manage this risk on your own terms</strong>. Taking that risk in development is good because by definition that's when you're incorporating and testing software changes. On the other hand, if you're shipping production software, you probably don't want to take this risk when cutting a release candidate (i.e. build time) or when you actually ship (i.e. deploy time) because you want to validate whatever you ship.\r
-\r
-</p>\r
-<p>You can address a simple case of this problem by only depending on specific versions of packages, allowing no semver flexibility at all, but this falls apart when you depend on packages that don't also adopt the same principle. Many of us at Joyent started wondering: can we generalize this approach?\r
-\r
-</p>\r
-<h2>Shrinkwrapping packages</h2>\r
-<p>That brings us to <a href="http://npmjs.org/doc/shrinkwrap.html">npm shrinkwrap</a><a href="#note1-note" name="note1-top">[1]</a>:\r
-\r
-</p>\r
-<pre><code>NAME\r
- npm-shrinkwrap -- Lock down dependency versions\r
-\r
-SYNOPSIS\r
- npm shrinkwrap\r
-\r
-DESCRIPTION\r
- This command locks down the versions of a package's dependencies so\r
- that you can control exactly which versions of each dependency will\r
- be used when your package is installed.</code></pre>\r
-<p>Let's consider package A:\r
-\r
-</p>\r
-<pre><code>{\r
- "name": "A",\r
- "version": "0.1.0",\r
- "dependencies": {\r
- "B": "<0.1.0"\r
- }\r
-}</code></pre>\r
-<p>package B:\r
-\r
-</p>\r
-<pre><code>{\r
- "name": "B",\r
- "version": "0.0.1",\r
- "dependencies": {\r
- "C": "<0.1.0"\r
- }\r
-}</code></pre>\r
-<p>and package C:\r
-\r
-</p>\r
-<pre><code>{\r
- "name": "C,\r
- "version": "0.0.1"\r
-}</code></pre>\r
-<p>If these are the only versions of A, B, and C available in the registry, then a normal "npm install A" will install:\r
-\r
-</p>\r
-<pre><code>A@0.1.0\r
-└─┬ B@0.0.1\r
- └── C@0.0.1</code></pre>\r
-<p>Then if B@0.0.2 is published, then a fresh "npm install A" will install:\r
-\r
-</p>\r
-<pre><code>A@0.1.0\r
-└─┬ B@0.0.2\r
- └── C@0.0.1</code></pre>\r
-<p>assuming the new version did not modify B's dependencies. Of course, the new version of B could include a new version of C and any number of new dependencies. As we said before, if A's author doesn't want that, she could specify a dependency on B@0.0.1. But if A's author and B's author are not the same person, there's no way for A's author to say that she does not want to pull in newly published versions of C when B hasn't changed at all.\r
-\r
-</p>\r
-<p>In this case, A's author can use\r
-\r
-</p>\r
-<pre><code># npm shrinkwrap</code></pre>\r
-<p>This generates npm-shrinkwrap.json, which will look something like this:\r
-\r
-</p>\r
-<pre><code>{\r
- "name": "A",\r
- "dependencies": {\r
- "B": {\r
- "version": "0.0.1",\r
- "dependencies": {\r
- "C": { "version": "0.1.0" }\r
- }\r
- }\r
- }\r
-}</code></pre>\r
-<p>The shrinkwrap command has locked down the dependencies based on what's currently installed in node_modules. <strong>When "npm install" installs a package with a npm-shrinkwrap.json file in the package root, the shrinkwrap file (rather than package.json files) completely drives the installation of that package and all of its dependencies (recursively).</strong> So now the author publishes A@0.1.0, and subsequent installs of this package will use B@0.0.1 and C@0.1.0, regardless the dependencies and versions listed in A's, B's, and C's package.json files. If the authors of B and C publish new versions, they won't be used to install A because the shrinkwrap refers to older versions. Even if you generate a new shrinkwrap, it will still reference the older versions, since "npm shrinkwrap" uses what's installed locally rather than what's available in the registry. \r
-\r
-</p>\r
-<h4>Using shrinkwrapped packages</h4>\r
-<p>Using a shrinkwrapped package is no different than using any other package: you can "npm install" it by hand, or add a dependency to your package.json file and "npm install" it.\r
-\r
-</p>\r
-<h4>Building shrinkwrapped packages</h4>\r
-<p>To shrinkwrap an existing package:\r
-\r
-</p>\r
-<ol>\r
-<li>Run "npm install" in the package root to install the current versions of all dependencies.</li>\r
-<li>Validate that the package works as expected with these versions.</li>\r
-<li>Run "npm shrinkwrap", add npm-shrinkwrap.json to git, and publish your package.</li>\r
-</ol>\r
-<p>To add or update a dependency in a shrinkwrapped package:\r
-\r
-</p>\r
-<ol>\r
-<li>Run "npm install" in the package root to install the current versions of all dependencies.</li>\r
-<li>Add or update dependencies. "npm install" each new or updated package individually and then update package.json.</li>\r
-<li>Validate that the package works as expected with the new dependencies.</li>\r
-<li>Run "npm shrinkwrap", commit the new npm-shrinkwrap.json, and publish your package.</li>\r
-</ol>\r
-<p>You can still use <a href="http://npmjs.org/doc/outdated.html">npm outdated(1)</a> to view which dependencies have newer versions available.\r
-\r
-</p>\r
-<p>For more details, check out the full docs on <a href="http://npmjs.org/doc/shrinkwrap.html">npm shrinkwrap</a>, from which much of the above is taken.\r
-\r
-</p>\r
-<h2>Why not just check <code>node_modules</code> into git?</h2>\r
-<p>One previously <a href="http://www.mikealrogers.com/posts/nodemodules-in-git.html">proposed solution</a> is to "npm install" your dependencies during development and commit the results into source control. Then you deploy your app from a specific git SHA knowing you've got exactly the same bits that you tested in development. This does address the problem, but it has its own issues: for one, binaries are tricky because you need to "npm install" them to get their sources, but this builds the [system-dependent] binary too. You can avoid checking in the binaries and use "npm rebuild" at build time, but we've had a lot of difficulty trying to do this.<a href="#note2-note" name="note2-top">[2]</a> At best, this is second-class treatment for binary modules, which are critical for many important types of Node applications.<a href="#note3-note" name="note3-top">[3]</a>\r
-\r
-</p>\r
-<p>Besides the issues with binary modules, this approach just felt wrong to many of us. There's a reason we don't check binaries into source control, and it's not just because they're platform-dependent. (After all, we could build and check in binaries for all supported platforms and operating systems.) It's because that approach is error-prone and redundant: error-prone because it introduces a new human failure mode where someone checks in a source change but doesn't regenerate all the binaries, and redundant because the binaries can always be built from the sources alone. An important principle of software version control is that you don't check in files derived directly from other files by a simple transformation.<a href="#note4-note" name="note4-top">[4]</a> Instead, you check in the original sources and automate the transformations via the build process.\r
-\r
-</p>\r
-<p>Dependencies are just like binaries in this regard: they're files derived from a simple transformation of something else that is (or could easily be) already available: the name and version of the dependency. Checking them in has all the same problems as checking in binaries: people could update package.json without updating the checked-in module (or vice versa). Besides that, adding new dependencies has to be done by hand, introducing more opportunities for error (checking in the wrong files, not checking in certain files, inadvertently changing files, and so on). Our feeling was: why check in this whole dependency tree (and create a mess for binary add-ons) when we could just check in the package name and version and have the build process do the rest?\r
-\r
-</p>\r
-<p>Finally, the approach of checking in node_modules doesn't really scale for us. We've got at least a dozen repos that will use restify, and it doesn't make sense to check that in everywhere when we could instead just specify which version each one is using. There's another principle at work here, which is <strong>separation of concerns</strong>: each repo specifies <em>what</em> it needs, while the build process figures out <em>where to get it</em>.\r
-\r
-</p>\r
-<h2>What if an author republishes an existing version of a package?</h2>\r
-<p>We're not suggesting deploying a shrinkwrapped package directly and running "npm install" to install from shrinkwrap in production. We already have a build process to deal with binary modules and other automateable tasks. That's where we do the "npm install". We tar up the result and distribute the tarball. Since we test each build before shipping, we won't deploy something we didn't test.\r
-\r
-</p>\r
-<p>It's still possible to pick up newly published versions of existing packages at build time. We assume force publish is not that common in the first place, let alone force publish that breaks compatibility. If you're worried about this, you can use git SHAs in the shrinkwrap or even consider maintaining a mirror of the part of the npm registry that you use and require human confirmation before mirroring unpublishes.\r
-\r
-</p>\r
-<h2>Final thoughts</h2>\r
-<p>Of course, the details of each use case matter a lot, and the world doesn't have to pick just one solution. If you like checking in node_modules, you should keep doing that. We've chosen the shrinkwrap route because that works better for us.\r
-\r
-</p>\r
-<p>It's not exactly news that Joyent is heavy on Node. Node is the heart of our SmartDataCenter (SDC) product, whose public-facing web portal, public API, Cloud Analytics, provisioning, billing, heartbeating, and other services are all implemented in Node. That's why it's so important to us to have robust components (like <a href="https://github.com/trentm/node-bunyan">logging</a> and <a href="http://mcavage.github.com/node-restify/">REST</a>) and tools for <a href="http://dtrace.org/blogs/dap/2012/01/13/playing-with-nodev8-postmortem-debugging/">understanding production failures post mortem</a>, <a href="http://dtrace.org/blogs/dap/2012/01/05/where-does-your-node-program-spend-its-time/">profile Node apps in production</a>, and now managing Node dependencies. Again, we're interested to hear feedback from others using these tools.\r
-\r
-</p>\r
-<hr />\r
-Dave Pacheco blogs at <a href="http://dtrace.org/blogs/dap/">dtrace.org</a>.\r
-\r
-<p><a href="#note1-top" name="note1-note">[1]</a> Much of this section is taken directly from the "npm shrinkwrap" documentation.\r
-\r
-</p>\r
-<p><a href="#note2-top" name="note2-note">[2]</a> We've had a lot of trouble with checking in node_modules with binary dependencies. The first problem is figuring out exactly which files <em>not</em> to check in (<em>.o, </em>.node, <em>.dynlib, </em>.so, *.a, ...). When <a href="https://twitter.com/#!/mcavage">Mark</a> went to apply this to one of our internal services, the "npm rebuild" step blew away half of the dependency tree because it ran "make clean", which in dependency <a href="http://ldapjs.org/">ldapjs</a> brings the repo to a clean slate by blowing away its dependencies. Later, a new (but highly experienced) engineer on our team was tasked with fixing a bug in our Node-based DHCP server. To fix the bug, we went with a new dependency. He tried checking in node_modules, which added 190,000 lines of code (to this repo that was previously a few hundred LOC). And despite doing everything he could think of to do this correctly and test it properly, the change broke the build because of the binary modules. So having tried this approach a few times now, it appears quite difficult to get right, and as I pointed out above, the lack of actual documentation and real world examples suggests others either aren't using binary modules (which we know isn't true) or haven't had much better luck with this approach.\r
-\r
-</p>\r
-<p><a href="#note3-top" name="note3-note">[3]</a> Like a good Node-based distributed system, our architecture uses lots of small HTTP servers. Each of these serves a REST API using <a href="http://mcavage.github.com/node-restify/">restify</a>. restify uses the binary module <a href="https://github.com/chrisa/node-dtrace-provider">node-dtrace-provider</a>, which gives each of our services <a href="http://mcavage.github.com/node-restify/#DTrace">deep DTrace-based observability for free</a>. So literally almost all of our components are or will soon be depending on a binary add-on. Additionally, the foundation of <a href="http://dtrace.org/blogs/dap/2011/03/01/welcome-to-cloud-analytics/">Cloud Analytics</a> are a pair of binary modules that extract data from <a href="https://github.com/bcantrill/node-libdtrace">DTrace</a> and <a href="https://github.com/bcantrill/node-kstat">kstat</a>. So this isn't a corner case for us, and we don't believe we're exceptional in this regard. The popular <a href="https://github.com/pietern/hiredis-node">hiredis</a> package for interfacing with redis from Node is also a binary module.\r
-\r
-</p>\r
+<p>Managing dependencies is a fundamental problem in building complex software. The terrific success of github and <a href="http://npmjs.org/">npm</a> have made code reuse especially easy in the Node world, where packages don't exist in isolation but rather as nodes in a large graph. The software is constantly changing (releasing new versions), and each package has its own constraints about what other packages it requires to run (dependencies). npm keeps track of these constraints, and authors express what kind of changes are compatible using <a href="http://npmjs.org/doc/semver.html">semantic versioning</a>, allowing authors to specify that their package will work with even future versions of its dependencies as long as the semantic versions are assigned properly.
+
+</p>
+<p>This does mean that when you "npm install" a package with dependencies, there's no guarantee that you'll get the same set of code now that you would have gotten an hour ago, or that you would get if you were to run it again an hour later. You may get a bunch of bug fixes now that weren't available an hour ago. This is great during development, where you want to keep up with changes upstream. It's not necessarily what you want for deployment, though, where you want to validate whatever bits you're actually shipping.
+
+</p>
+<p>Put differently, <strong>it's understood that all software changes incur some risk, and it's critical to be able to manage this risk on your own terms</strong>. Taking that risk in development is good because by definition that's when you're incorporating and testing software changes. On the other hand, if you're shipping production software, you probably don't want to take this risk when cutting a release candidate (i.e. build time) or when you actually ship (i.e. deploy time) because you want to validate whatever you ship.
+
+</p>
+<p>You can address a simple case of this problem by only depending on specific versions of packages, allowing no semver flexibility at all, but this falls apart when you depend on packages that don't also adopt the same principle. Many of us at Joyent started wondering: can we generalize this approach?
+
+</p>
+<h2>Shrinkwrapping packages</h2>
+<p>That brings us to <a href="http://npmjs.org/doc/shrinkwrap.html">npm shrinkwrap</a><a href="#note1-note" name="note1-top">[1]</a>:
+
+</p>
+<pre><code>NAME
+ npm-shrinkwrap -- Lock down dependency versions
+
+SYNOPSIS
+ npm shrinkwrap
+
+DESCRIPTION
+ This command locks down the versions of a package's dependencies so
+ that you can control exactly which versions of each dependency will
+ be used when your package is installed.</code></pre>
+<p>Let's consider package A:
+
+</p>
+<pre><code>{
+ "name": "A",
+ "version": "0.1.0",
+ "dependencies": {
+ "B": "<0.1.0"
+ }
+}</code></pre>
+<p>package B:
+
+</p>
+<pre><code>{
+ "name": "B",
+ "version": "0.0.1",
+ "dependencies": {
+ "C": "<0.1.0"
+ }
+}</code></pre>
+<p>and package C:
+
+</p>
+<pre><code>{
+ "name": "C,
+ "version": "0.0.1"
+}</code></pre>
+<p>If these are the only versions of A, B, and C available in the registry, then a normal "npm install A" will install:
+
+</p>
+<pre><code>A@0.1.0
+└─┬ B@0.0.1
+ └── C@0.0.1</code></pre>
+<p>Then if B@0.0.2 is published, then a fresh "npm install A" will install:
+
+</p>
+<pre><code>A@0.1.0
+└─┬ B@0.0.2
+ └── C@0.0.1</code></pre>
+<p>assuming the new version did not modify B's dependencies. Of course, the new version of B could include a new version of C and any number of new dependencies. As we said before, if A's author doesn't want that, she could specify a dependency on B@0.0.1. But if A's author and B's author are not the same person, there's no way for A's author to say that she does not want to pull in newly published versions of C when B hasn't changed at all.
+
+</p>
+<p>In this case, A's author can use
+
+</p>
+<pre><code># npm shrinkwrap</code></pre>
+<p>This generates npm-shrinkwrap.json, which will look something like this:
+
+</p>
+<pre><code>{
+ "name": "A",
+ "dependencies": {
+ "B": {
+ "version": "0.0.1",
+ "dependencies": {
+ "C": { "version": "0.1.0" }
+ }
+ }
+ }
+}</code></pre>
+<p>The shrinkwrap command has locked down the dependencies based on what's currently installed in node_modules. <strong>When "npm install" installs a package with a npm-shrinkwrap.json file in the package root, the shrinkwrap file (rather than package.json files) completely drives the installation of that package and all of its dependencies (recursively).</strong> So now the author publishes A@0.1.0, and subsequent installs of this package will use B@0.0.1 and C@0.1.0, regardless the dependencies and versions listed in A's, B's, and C's package.json files. If the authors of B and C publish new versions, they won't be used to install A because the shrinkwrap refers to older versions. Even if you generate a new shrinkwrap, it will still reference the older versions, since "npm shrinkwrap" uses what's installed locally rather than what's available in the registry.
+
+</p>
+<h4>Using shrinkwrapped packages</h4>
+<p>Using a shrinkwrapped package is no different than using any other package: you can "npm install" it by hand, or add a dependency to your package.json file and "npm install" it.
+
+</p>
+<h4>Building shrinkwrapped packages</h4>
+<p>To shrinkwrap an existing package:
+
+</p>
+<ol>
+<li>Run "npm install" in the package root to install the current versions of all dependencies.</li>
+<li>Validate that the package works as expected with these versions.</li>
+<li>Run "npm shrinkwrap", add npm-shrinkwrap.json to git, and publish your package.</li>
+</ol>
+<p>To add or update a dependency in a shrinkwrapped package:
+
+</p>
+<ol>
+<li>Run "npm install" in the package root to install the current versions of all dependencies.</li>
+<li>Add or update dependencies. "npm install" each new or updated package individually and then update package.json.</li>
+<li>Validate that the package works as expected with the new dependencies.</li>
+<li>Run "npm shrinkwrap", commit the new npm-shrinkwrap.json, and publish your package.</li>
+</ol>
+<p>You can still use <a href="http://npmjs.org/doc/outdated.html">npm outdated(1)</a> to view which dependencies have newer versions available.
+
+</p>
+<p>For more details, check out the full docs on <a href="http://npmjs.org/doc/shrinkwrap.html">npm shrinkwrap</a>, from which much of the above is taken.
+
+</p>
+<h2>Why not just check <code>node_modules</code> into git?</h2>
+<p>One previously <a href="http://www.mikealrogers.com/posts/nodemodules-in-git.html">proposed solution</a> is to "npm install" your dependencies during development and commit the results into source control. Then you deploy your app from a specific git SHA knowing you've got exactly the same bits that you tested in development. This does address the problem, but it has its own issues: for one, binaries are tricky because you need to "npm install" them to get their sources, but this builds the [system-dependent] binary too. You can avoid checking in the binaries and use "npm rebuild" at build time, but we've had a lot of difficulty trying to do this.<a href="#note2-note" name="note2-top">[2]</a> At best, this is second-class treatment for binary modules, which are critical for many important types of Node applications.<a href="#note3-note" name="note3-top">[3]</a>
+
+</p>
+<p>Besides the issues with binary modules, this approach just felt wrong to many of us. There's a reason we don't check binaries into source control, and it's not just because they're platform-dependent. (After all, we could build and check in binaries for all supported platforms and operating systems.) It's because that approach is error-prone and redundant: error-prone because it introduces a new human failure mode where someone checks in a source change but doesn't regenerate all the binaries, and redundant because the binaries can always be built from the sources alone. An important principle of software version control is that you don't check in files derived directly from other files by a simple transformation.<a href="#note4-note" name="note4-top">[4]</a> Instead, you check in the original sources and automate the transformations via the build process.
+
+</p>
+<p>Dependencies are just like binaries in this regard: they're files derived from a simple transformation of something else that is (or could easily be) already available: the name and version of the dependency. Checking them in has all the same problems as checking in binaries: people could update package.json without updating the checked-in module (or vice versa). Besides that, adding new dependencies has to be done by hand, introducing more opportunities for error (checking in the wrong files, not checking in certain files, inadvertently changing files, and so on). Our feeling was: why check in this whole dependency tree (and create a mess for binary add-ons) when we could just check in the package name and version and have the build process do the rest?
+
+</p>
+<p>Finally, the approach of checking in node_modules doesn't really scale for us. We've got at least a dozen repos that will use restify, and it doesn't make sense to check that in everywhere when we could instead just specify which version each one is using. There's another principle at work here, which is <strong>separation of concerns</strong>: each repo specifies <em>what</em> it needs, while the build process figures out <em>where to get it</em>.
+
+</p>
+<h2>What if an author republishes an existing version of a package?</h2>
+<p>We're not suggesting deploying a shrinkwrapped package directly and running "npm install" to install from shrinkwrap in production. We already have a build process to deal with binary modules and other automateable tasks. That's where we do the "npm install". We tar up the result and distribute the tarball. Since we test each build before shipping, we won't deploy something we didn't test.
+
+</p>
+<p>It's still possible to pick up newly published versions of existing packages at build time. We assume force publish is not that common in the first place, let alone force publish that breaks compatibility. If you're worried about this, you can use git SHAs in the shrinkwrap or even consider maintaining a mirror of the part of the npm registry that you use and require human confirmation before mirroring unpublishes.
+
+</p>
+<h2>Final thoughts</h2>
+<p>Of course, the details of each use case matter a lot, and the world doesn't have to pick just one solution. If you like checking in node_modules, you should keep doing that. We've chosen the shrinkwrap route because that works better for us.
+
+</p>
+<p>It's not exactly news that Joyent is heavy on Node. Node is the heart of our SmartDataCenter (SDC) product, whose public-facing web portal, public API, Cloud Analytics, provisioning, billing, heartbeating, and other services are all implemented in Node. That's why it's so important to us to have robust components (like <a href="https://github.com/trentm/node-bunyan">logging</a> and <a href="http://mcavage.github.com/node-restify/">REST</a>) and tools for <a href="http://dtrace.org/blogs/dap/2012/01/13/playing-with-nodev8-postmortem-debugging/">understanding production failures post mortem</a>, <a href="http://dtrace.org/blogs/dap/2012/01/05/where-does-your-node-program-spend-its-time/">profile Node apps in production</a>, and now managing Node dependencies. Again, we're interested to hear feedback from others using these tools.
+
+</p>
+<hr />
+Dave Pacheco blogs at <a href="http://dtrace.org/blogs/dap/">dtrace.org</a>.
+
+<p><a href="#note1-top" name="note1-note">[1]</a> Much of this section is taken directly from the "npm shrinkwrap" documentation.
+
+</p>
+<p><a href="#note2-top" name="note2-note">[2]</a> We've had a lot of trouble with checking in node_modules with binary dependencies. The first problem is figuring out exactly which files <em>not</em> to check in (<em>.o, </em>.node, <em>.dynlib, </em>.so, *.a, ...). When <a href="https://twitter.com/#!/mcavage">Mark</a> went to apply this to one of our internal services, the "npm rebuild" step blew away half of the dependency tree because it ran "make clean", which in dependency <a href="http://ldapjs.org/">ldapjs</a> brings the repo to a clean slate by blowing away its dependencies. Later, a new (but highly experienced) engineer on our team was tasked with fixing a bug in our Node-based DHCP server. To fix the bug, we went with a new dependency. He tried checking in node_modules, which added 190,000 lines of code (to this repo that was previously a few hundred LOC). And despite doing everything he could think of to do this correctly and test it properly, the change broke the build because of the binary modules. So having tried this approach a few times now, it appears quite difficult to get right, and as I pointed out above, the lack of actual documentation and real world examples suggests others either aren't using binary modules (which we know isn't true) or haven't had much better luck with this approach.
+
+</p>
+<p><a href="#note3-top" name="note3-note">[3]</a> Like a good Node-based distributed system, our architecture uses lots of small HTTP servers. Each of these serves a REST API using <a href="http://mcavage.github.com/node-restify/">restify</a>. restify uses the binary module <a href="https://github.com/chrisa/node-dtrace-provider">node-dtrace-provider</a>, which gives each of our services <a href="http://mcavage.github.com/node-restify/#DTrace">deep DTrace-based observability for free</a>. So literally almost all of our components are or will soon be depending on a binary add-on. Additionally, the foundation of <a href="http://dtrace.org/blogs/dap/2011/03/01/welcome-to-cloud-analytics/">Cloud Analytics</a> are a pair of binary modules that extract data from <a href="https://github.com/bcantrill/node-libdtrace">DTrace</a> and <a href="https://github.com/bcantrill/node-kstat">kstat</a>. So this isn't a corner case for us, and we don't believe we're exceptional in this regard. The popular <a href="https://github.com/pietern/hiredis-node">hiredis</a> package for interfacing with redis from Node is also a binary module.
+
+</p>
<p><a href="#note4-top" name="note4-note">[4]</a> Note that I said this is an important principle for <em>software version control</em>, not using git in general. People use git for lots of things where checking in binaries and other derived files is probably fine. Also, I'm not interested in proselytizing; if you want to do this for software version control too, go ahead. But don't do it out of ignorance of existing successful software engineering practices.</p>
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>\r
-\r
-<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>\r
-\r
-<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>\r
-\r
-<p>Also, there was that activation/deactivation thing. That’s confusing.</p>\r
-\r
-<h2>Two paths</h2>\r
-\r
-<p>In npm 1.0, there are two ways to install things:</p>\r
-\r
-<ol> <li>globally —- 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’re supplied.</li> <li>locally —- 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’t installed at all.</li> </ol>\r
-\r
-<h2>Which to choose</h2>\r
-\r
-<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>\r
-\r
-<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>\r
-\r
-<p>In general, the rule of thumb is:</p>\r
-\r
-<ol> <li>If you’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’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>\r
-\r
-<h2>When you can't choose</h2>\r
-\r
-<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>\r
-\r
-<ol> <li>Install it in both places. Seriously, are you that short on disk space? It’s fine, really. They’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’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>\r
-\r
-<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>\r
-\r
-<p>You can probably think of other ways to do it by messing with environment variables. But I don’t recommend those ways. Go with the grain.</p>\r
-\r
-<h2 id="slight_exception_it8217s_not_always_the_cwd">Slight exception: It’s not always the cwd.</h2>\r
-\r
-<p>Let’s say you do something like this:</p>\r
-\r
-<pre style="background:#333!important;color:#ccc!important;overflow:auto!important;padding:2px!important;"><code>cd ~/projects/foo # go into my project\r
-npm install express # ./node_modules/express\r
-cd lib/utils # move around in there\r
-vim some-thing.js # edit some stuff, work work work\r
-npm install redis # ./lib/utils/node_modules/redis!? ew.</code></pre>\r
-\r
-<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>\r
-\r
-<h2>Test runners and stuff</h2>\r
-\r
-<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:\r
-\r
-<pre style="background:#333!important;color:#ccc!important;overflow:auto!important;padding:2px!important;"><code>{ "name" : "my-program"\r
-, "version" : "1.2.3"\r
-, "dependencies": { "express": "*", "coffee-script": "*" }\r
-, "devDependencies": { "vows": "*" }\r
-, "scripts":\r
- { "test": "vows test/*.js"\r
+<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’s confusing.</p>
+
+<h2>Two paths</h2>
+
+<p>In npm 1.0, there are two ways to install things:</p>
+
+<ol> <li>globally —- 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’re supplied.</li> <li>locally —- 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’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’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’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’s fine, really. They’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’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’t recommend those ways. Go with the grain.</p>
+
+<h2 id="slight_exception_it8217s_not_always_the_cwd">Slight exception: It’s not always the cwd.</h2>
+
+<p>Let’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>
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>\r
-\r
-<p>In npm 0.x, there was a command called <code>link</code>. With it, you could “link-install” a package so that changes would be reflected in real-time. This is especially handy when you’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>\r
-\r
-<p>Of course, compiled modules still have to be rebuilt. That’s not ideal, but it’s a problem that will take more powerful magic to solve.</p>\r
-\r
-<p>In npm 0.x, this was a pretty awful kludge. Back then, every package existed in some folder like:</p>\r
-\r
-<pre><code>prefix/lib/node/.npm/my-package/1.3.6/package\r
-</code></pre>\r
-\r
-<p>and the package’s version and name could be inferred from the path. Then, symbolic links were set up that looked like:</p>\r
-\r
-<pre><code>prefix/lib/node/my-package@1.3.6 -> ./.npm/my-package/1.3.6/package\r
-</code></pre>\r
-\r
-<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>\r
-\r
-<p>At first, this was just sort of something that we dealt with by saying, “Relink if you change the version.” However, as more and more edge cases arose, eventually the solution was to give link packages this fakey version of “9999.0.0-LINK-hash” 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>\r
-\r
-<h2 id="a_better_way">A better way</h2>\r
-\r
-<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>\r
-\r
-<ol>\r
-<li>globally install this package I’m working on so that I can run the command it creates and test its stuff as I work on it.</li>\r
-<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>\r
-</ol>\r
-\r
-<p>And, in both cases, changes should be immediately apparent and not require any re-linking.</p>\r
-\r
-<p><em>Also</em>, there’s a third use case that I didn’t really appreciate until I started writing more programs that had more dependencies:</p>\r
-\r
-<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>\r
-\r
-<p>Really, the second case above is a special-case of this third case.</p>\r
-\r
-<h2 id="link_devel_global">Link devel → global</h2>\r
-\r
-<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>\r
-\r
-<p>I do this as I’m developing node projects (including npm itself).</p>\r
-\r
-<pre><code>cd ~/dev/js/node-tap # go into the project dir\r
-npm link # create symlinks into {prefix}\r
-</code></pre>\r
-\r
-<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>\r
-\r
-<p>Of course, if you <a href="http://blog.nodejs.org/2011/04/04/development-environment/">set your paths differently</a>, then you’ll have different results. (That’s why I tend to talk in terms of <code>prefix</code> rather than <code>/usr/local</code>.)</p>\r
-\r
-<h2 id="link_global_local">Link global → local</h2>\r
-\r
-<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>\r
-\r
-<p>For example, let’s say that I wanted to write some tap tests for my node-glob package. I’d <em>first</em> do the steps above to link tap into the global install space, and <em>then</em> I’d do this:</p>\r
-\r
-<pre><code>cd ~/dev/js/node-glob # go to the project that uses the thing.\r
-npm link tap # link the global thing into my project.\r
-</code></pre>\r
-\r
-<p>Now when I make changes in <code>~/dev/js/node-tap</code>, they’ll be immediately reflected in <code>~/dev/js/node-glob/node_modules/tap</code>.</p>\r
-\r
-<h2 id="link_to_stuff_you_don8217t_build">Link to stuff you <em>don’t</em> build</h2>\r
-\r
-<p>Let’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>\r
-\r
-<pre><code>npm install express -g # install express globally\r
-cd ~/dev/js/my-blog # development folder one\r
-npm link express # link the global express into ./node_modules\r
-cd ~/dev/js/photo-site # other project folder\r
-npm link express # link express into here, as well\r
-\r
- # time passes\r
- # TJ releases some new stuff.\r
- # you want this new stuff.\r
-\r
-npm update express -g # update the global install.\r
- # this also updates my project folders.\r
-</code></pre>\r
-\r
-<h2 id="caveat_not_for_real_servers">Caveat: Not For Real Servers</h2>\r
-\r
-<p>npm link is a development tool. It’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>\r
-\r
-<h2 id="caveat_2_sorry_windows">Caveat 2: Sorry, Windows!</h2>\r
-\r
-<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>\r
-\r
-<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>\r
-\r
-<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>\r
-\r
-\r
-<h2 id="aside_credit_where_credit8217s_due">Aside: Credit where Credit’s Due</h2>\r
-\r
-<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’d mentioned wanting to build. (That is, to convince me to use CouchDB for it.)</p>\r
-\r
-<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>\r
-\r
-<p>While I was there, he said, “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?”</p>\r
-\r
-<p>I was like, “Well, I don’t know… I mean, there’s these edge cases, and it doesn’t really fit with the existing folder structure very well…”</p>\r
-\r
-<p>“Dude. Either you do it, or I’m going to have to do it, and then there’ll be <em>another</em> package manager in node, instead of writing a registry for npm, and it won’t be as good anyway. Don’t be python.”</p>\r
-\r
+<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 “link-install” a package so that changes would be reflected in real-time. This is especially handy when you’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’s not ideal, but it’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’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 -> ./.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, “Relink if you change the version.” However, as more and more edge cases arose, eventually the solution was to give link packages this fakey version of “9999.0.0-LINK-hash” 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’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’s a third use case that I didn’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 → 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’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’ll have different results. (That’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 → 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’s say that I wanted to write some tap tests for my node-glob package. I’d <em>first</em> do the steps above to link tap into the global install space, and <em>then</em> I’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’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’t</em> build</h2>
+
+<p>Let’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’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’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’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, “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?”</p>
+
+<p>I was like, “Well, I don’t know… I mean, there’s these edge cases, and it doesn’t really fit with the existing folder structure very well…”</p>
+
+<p>“Dude. Either you do it, or I’m going to have to do it, and then there’ll be <em>another</em> package manager in node, instead of writing a registry for npm, and it won’t be as good anyway. Don’t be python.”</p>
+
<p>The rest is history.</p>
category: npm
slug: npm-1-0-released
-<p>npm 1.0 has been released. Here are the highlights:</p>\r
-\r
-<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 “activation” 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 “search” command. One line per package, rather than one line per version.</li> <li>Renovated “completion” approach</li> <li>More help topics</li> <li>Simplified folder structure</li> </ul>\r
-\r
-<p>The focus is on npm being a development tool, rather than an apt-wannabe.</p>\r
-\r
-<h2 id="installing_it">Installing it</h2>\r
-\r
-<p>To get the new version, run this command:</p>\r
-\r
-<pre style="background:#333;color:#ccc;overflow:auto;padding:2px;"><code>curl http://npmjs.org/install.sh | sh </code></pre>\r
-\r
-<p>This will prompt to ask you if it’s ok to remove all the old 0.x cruft. If you want to not be asked, then do this:</p>\r
-\r
-<pre style="background:#333;color:#ccc;overflow:auto;padding:2px;"><code>curl http://npmjs.org/install.sh | clean=yes sh </code></pre>\r
-\r
-<p>Or, if you want to not do the cleanup, and leave the old stuff behind, then do this:</p>\r
-\r
-<pre style="background:#333;color:#ccc;overflow:auto;padding:2px;"><code>curl http://npmjs.org/install.sh | clean=no sh </code></pre>\r
-\r
-<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>\r
-\r
-<h2 id="code_freeze">Code Freeze</h2>\r
-\r
-<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’s time to let the client itself settle. Also, I want to focus attention on some other problems for a little while.</p>\r
-\r
-<p>Of course, <a href="https://github.com/isaacs/npm/issues">bug reports</a> are always welcome.</p>\r
-\r
+<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 “activation” 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 “search” command. One line per package, rather than one line per version.</li> <li>Renovated “completion” 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’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’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>
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>\r
-\r
-<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>\r
-\r
-<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>\r
-\r
-<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>\r
-\r
-<p>Here’s an example of the output:</p>\r
-\r
-<pre style="background:#333;color:#ccc;overflow:auto;padding:2px;"><code>$ npm ls\r
-npm@1.0.0 /Users/isaacs/dev-src/js/npm\r
-├── semver@1.0.1 \r
-├─┬ ronn@0.3.5 \r
-│ └── opts@1.2.1 \r
-└─┬ express@2.0.0rc3 <span style="background:#000;color:#0f0;">extraneous</span> \r
- ├─┬ connect@1.1.0 \r
- │ ├── qs@0.0.7 \r
- │ └── mime@1.2.1 \r
- ├── mime@1.2.1 \r
- └── qs@0.0.7\r
-</code></pre>\r
-\r
-<p>This is after I’ve done <code>npm install semver ronn express</code> in the npm source directory. Since express isn’t actually a dependency of npm, it shows up with that “extraneous” marker.</p>\r
-\r
-<p>Let’s see what happens when we create a broken situation:</p>\r
-\r
-<pre style="background:#333;color:#ccc;overflow:auto;padding:2px;"><code>$ rm -rf ./node_modules/express/node_modules/connect\r
-$ npm ls\r
-npm@1.0.0 /Users/isaacs/dev-src/js/npm\r
-├── semver@1.0.1 \r
-├─┬ ronn@0.3.5 \r
-│ └── opts@1.2.1 \r
-└─┬ express@2.0.0rc3 <span style="background:#000;color:#0f0;">extraneous</span> \r
- ├── <span style="background:#000;color:#f00;">UNMET DEPENDENCY</span> connect >= 1.1.0 < 2.0.0\r
- ├── mime@1.2.1 \r
- └── qs@0.0.7\r
-</code></pre>\r
-\r
-<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>\r
-\r
-<pre style="background:#333;color:#ccc;overflow:auto;padding:2px;"><code>$ npm ls -p\r
-/Users/isaacs/dev-src/js/npm\r
-/Users/isaacs/dev-src/js/npm/node_modules/semver\r
-/Users/isaacs/dev-src/js/npm/node_modules/ronn\r
-/Users/isaacs/dev-src/js/npm/node_modules/ronn/node_modules/opts\r
-/Users/isaacs/dev-src/js/npm/node_modules/express\r
-/Users/isaacs/dev-src/js/npm/node_modules/express/node_modules/connect\r
-/Users/isaacs/dev-src/js/npm/node_modules/express/node_modules/connect/node_modules/qs\r
-/Users/isaacs/dev-src/js/npm/node_modules/express/node_modules/connect/node_modules/mime\r
-/Users/isaacs/dev-src/js/npm/node_modules/express/node_modules/mime\r
-/Users/isaacs/dev-src/js/npm/node_modules/express/node_modules/qs\r
-</code></pre>\r
-\r
-<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>\r
-\r
-<pre style="background:#333;color:#ccc;overflow:auto;padding:2px;"><code>$ npm ls -l\r
-npm@1.0.0 \r
-│ /Users/isaacs/dev-src/js/npm\r
-│ A package manager for node\r
-│ git://github.com/isaacs/npm.git\r
-│ http://npmjs.org/\r
-├── semver@1.0.1 \r
-│ ./node_modules/semver\r
-│ The semantic version parser used by npm.\r
-│ git://github.com/isaacs/node-semver.git\r
-├─┬ ronn@0.3.5 \r
-│ │ ./node_modules/ronn\r
-│ │ markdown to roff and html converter\r
-│ └── opts@1.2.1 \r
-│ ./node_modules/ronn/node_modules/opts\r
-│ Command line argument parser written in the style of commonjs. To be used with node.js\r
-└─┬ express@2.0.0rc3 <span style="background:#000;color:#0f0;">extraneous</span> \r
- │ ./node_modules/express\r
- │ Sinatra inspired web development framework\r
- ├─┬ connect@1.1.0 \r
- │ │ ./node_modules/express/node_modules/connect\r
- │ │ High performance middleware framework\r
- │ │ git://github.com/senchalabs/connect.git\r
- │ ├── qs@0.0.7 \r
- │ │ ./node_modules/express/node_modules/connect/node_modules/qs\r
- │ │ querystring parser\r
- │ └── mime@1.2.1 \r
- │ ./node_modules/express/node_modules/connect/node_modules/mime\r
- │ A comprehensive library for mime-type mapping\r
- ├── mime@1.2.1 \r
- │ ./node_modules/express/node_modules/mime\r
- │ A comprehensive library for mime-type mapping\r
- └── qs@0.0.7 \r
- ./node_modules/express/node_modules/qs\r
- querystring parser\r
-\r
-$ npm ls -lp\r
-/Users/isaacs/dev-src/js/npm:npm@1.0.0::::\r
-/Users/isaacs/dev-src/js/npm/node_modules/semver:semver@1.0.1::::\r
-/Users/isaacs/dev-src/js/npm/node_modules/ronn:ronn@0.3.5::::\r
-/Users/isaacs/dev-src/js/npm/node_modules/ronn/node_modules/opts:opts@1.2.1::::\r
-/Users/isaacs/dev-src/js/npm/node_modules/express:express@2.0.0rc3:EXTRANEOUS:::\r
-/Users/isaacs/dev-src/js/npm/node_modules/express/node_modules/connect:connect@1.1.0::::\r
-/Users/isaacs/dev-src/js/npm/node_modules/express/node_modules/connect/node_modules/qs:qs@0.0.7::::\r
-/Users/isaacs/dev-src/js/npm/node_modules/express/node_modules/connect/node_modules/mime:mime@1.2.1::::\r
-/Users/isaacs/dev-src/js/npm/node_modules/express/node_modules/mime:mime@1.2.1::::\r
-/Users/isaacs/dev-src/js/npm/node_modules/express/node_modules/qs:qs@0.0.7::::\r
-</code></pre>\r
-\r
-<p>And, if you want to get at the globally-installed modules, you can use ls with the global flag:</p>\r
-\r
-<pre style="background:#333;color:#ccc;overflow:auto;padding:2px;"><code>$ npm ls -g\r
-/usr/local\r
-├─┬ A@1.2.3 -> /Users/isaacs/dev-src/js/A\r
-│ ├── B@1.2.3 -> /Users/isaacs/dev-src/js/B\r
-│ └─┬ npm@0.3.15 \r
-│ └── semver@1.0.1 \r
-├─┬ B@1.2.3 -> /Users/isaacs/dev-src/js/B\r
-│ └── A@1.2.3 -> /Users/isaacs/dev-src/js/A\r
-├── glob@2.0.5 \r
-├─┬ npm@1.0.0 -> /Users/isaacs/dev-src/js/npm\r
-│ ├── semver@1.0.1 \r
-│ └─┬ ronn@0.3.5 \r
-│ └── opts@1.2.1 \r
-└── supervisor@0.1.2 -> /Users/isaacs/dev-src/js/node-supervisor\r
-\r
-$ npm ls -gpl\r
-/usr/local:::::\r
-/usr/local/lib/node_modules/A:A@1.2.3::::/Users/isaacs/dev-src/js/A\r
-/usr/local/lib/node_modules/A/node_modules/npm:npm@0.3.15::::/Users/isaacs/dev-src/js/A/node_modules/npm\r
-/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\r
-/usr/local/lib/node_modules/B:B@1.2.3::::/Users/isaacs/dev-src/js/B\r
-/usr/local/lib/node_modules/glob:glob@2.0.5::::\r
-/usr/local/lib/node_modules/npm:npm@1.0.0::::/Users/isaacs/dev-src/js/npm\r
-/usr/local/lib/node_modules/npm/node_modules/semver:semver@1.0.1::::/Users/isaacs/dev-src/js/npm/node_modules/semver\r
-/usr/local/lib/node_modules/npm/node_modules/ronn:ronn@0.3.5::::/Users/isaacs/dev-src/js/npm/node_modules/ronn\r
-/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\r
-/usr/local/lib/node_modules/supervisor:supervisor@0.1.2::::/Users/isaacs/dev-src/js/node-supervisor\r
-</code></pre>\r
-\r
+<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’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’ve done <code>npm install semver ronn express</code> in the npm source directory. Since express isn’t actually a dependency of npm, it shows up with that “extraneous” marker.</p>
+
+<p>Let’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 >= 1.1.0 < 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 -> /Users/isaacs/dev-src/js/A
+│ ├── B@1.2.3 -> /Users/isaacs/dev-src/js/B
+│ └─┬ npm@0.3.15
+│ └── semver@1.0.1
+├─┬ B@1.2.3 -> /Users/isaacs/dev-src/js/B
+│ └── A@1.2.3 -> /Users/isaacs/dev-src/js/A
+├── glob@2.0.5
+├─┬ npm@1.0.0 -> /Users/isaacs/dev-src/js/npm
+│ ├── semver@1.0.1
+│ └─┬ ronn@0.3.5
+│ └── opts@1.2.1
+└── supervisor@0.1.2 -> /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>-></code> flags are indications that the package is link-installed, which will be covered in the next installment.</p>
category: release
slug: node-v0-4-10
-2011.07.19, Version 0.4.10 (stable)\r
-<ul><li>#394 Fix Buffer drops last null character in UTF-8\r
-<li>#829 Backport r8577 from V8 (Ben Noordhuis)\r
-<li>#877 Don't wait for HTTP Agent socket pool to establish connections.\r
-<li>#915 Find kqueue on FreeBSD correctly (Brett Kiefer) \r
-<li>#1085 HTTP: Fix race in abort/dispatch code (Stefan Rusu)\r
-<li>#1274 debugger improvement (Yoshihiro Kikuchi)\r
-<li>#1291 Properly respond to HEAD during end(body) hot path (Reid Burke)\r
-<li>#1304 TLS: Fix race in abort/connection code (Stefan Rusu)\r
-<li>#1360 Allow _ in url hostnames.\r
-<li>Revert 37d529f8 - unbreaks debugger command parsing.\r
-<li>Bring back global execScript\r
-<li>Doc improvements</ul>\r
-\r
-Download: <a href="http://nodejs.org/dist/node-v0.4.10.tar.gz">http://nodejs.org/dist/node-v0.4.10.tar.gz</a>\r
-Website: <a href="http://nodejs.org/docs/v0.4.10">http://nodejs.org/docs/v0.4.10</a>\r
+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>
category: release
slug: node-v0-4-11
-2011.08.17, Version 0.4.11 (stable)\r
-<ul><li><a href="http://github.com/joyent/node/issues/738">#738</a> Fix crypto encryption/decryption with Base64. (SAWADA Tadashi)\r
-\r
-<li><a href="http://github.com/joyent/node/issues/1202">#1202</a> net.createConnection defer DNS lookup error events to next tick (Ben Noordhuis)\r
-\r
-<li><a href="http://github.com/joyent/node/issues/1374">#1374</a> fix setting ServerResponse.statusCode in writeHead (Trent Mick)\r
-\r
-<li><a href="http://github.com/joyent/node/issues/1417">#1417</a> Fix http.ClientRequest crashes if end() was called twice\r
-\r
-<li><a href="http://github.com/joyent/node/issues/1497">#1497</a> querystring: Replace 'in' test with 'hasOwnProperty' (isaacs)\r
-\r
-<li><a href="http://github.com/joyent/node/issues/1546">#1546</a> http perf improvement\r
-\r
-<li>fix memleak in libeio (Tom Hughes)\r
-\r
-<li>cmake improvements (Tom Hughes)\r
-\r
-<li>node_net.cc: fix incorrect sizeof() (Tom Hughes)\r
-\r
-<li>Windows/cygwin: no more GetConsoleTitleW errors on XP (Bert Belder)\r
-\r
-<li>Doc improvements (koichik, Logan Smyth, Ben Noordhuis, Arnout Kazemier)</ul>\r
-\r
-\r
-\r
-\r
-Download: <a href="http://nodejs.org/dist/node-v0.4.11.tar.gz">http://nodejs.org/dist/node-v0.4.11.tar.gz</a>\r
-\r
-Website: <a href="http://nodejs.org/docs/v0.4.11/">http://nodejs.org/docs/v0.4.11/</a>\r
-\r
+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>
category: release
slug: node-v0-4-12
-2011.09.15, Version 0.4.12 (stable)\r
-\r
-<ul>\r
-<li>Improve docs\r
-<li>#1563 overflow in ChildProcess custom_fd.\r
-<li>#1569, parse error on multi-line HTTP headers. (Ben Noordhuis)\r
-<li>#1586 net: Socket write encoding case sensitivity (koichik)\r
-<li>#1610 Remove DigiNotar CA from trusted list (isaacs)\r
-<li>#1624 buffer: Avoid overrun with 'binary' encoding. (koichik)\r
-<li>#1633 buffer: write() should always set _charsWritten. (koichik)\r
-<li>#1707 hasOwnProperty usage security hole in querystring (isaacs)\r
-<li>#1719 Drain OpenSSL error queue\r
-<li>Fix error reporting in net.Server.listen</ul>\r
-\r
-\r
-\r
-Download: <a href="http://nodejs.org/dist/node-v0.4.12.tar.gz">http://nodejs.org/dist/node-v0.4.12.tar.gz</a>\r
-\r
-Website: <a href="http://nodejs.org/docs/v0.4.12/">http://nodejs.org/docs/v0.4.12/</a>\r
-\r
+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>
category: release
slug: node-v0-4-3
-2011.03.18, Version 0.4.3 (stable)\r
-<ul>\r
-<li> Don't decrease server connection counter again if destroy() is called more than once GH-431 (Andreas Reich, Anders Conbere)\r
-<li> Documentation improvements (koichik)\r
-<li> Fix bug with setMaxListeners GH-682\r
-<li> Start up memory footprint improvement. (Tom Hughes)\r
-<li> Solaris improvements.\r
-<li> Buffer::Length(Buffer*) should not invoke itself recursively GH-759 (Ben Noordhuis)\r
-<li> TLS: Advertise support for client certs GH-774 (Theo Schlossnagle)\r
-<li> HTTP Agent bugs: GH-787, GH-784, GH-803.\r
-<li> Don't call GetMemoryUsage every 5 seconds.\r
-<li> Upgrade V8 to 3.1.8.3\r
-</ul>\r
-\r
-\r
-\r
-Download: http://nodejs.org/dist/node-v0.4.3.tar.gz\r
-\r
-Website: http://nodejs.org/docs/v0.4.3/\r
-\r
-Documentation: http://nodejs.org/docs/v0.4.3/api\r
-\r
-<a href="https://groups.google.com/d/topic/nodejs/JrYQCQtf6lM/discussion">Announcement</a>\r
-\r
+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>
category: release
slug: node-v0-4-4
-2011.03.26, Version 0.4.4 (stable)\r
-<ul>\r
-<li> CryptoStream.end shouldn't throw if not writable GH-820\r
-<li> Drop out if connection destroyed before connect() GH-819\r
-<li> expose https.Agent\r
-<li> Correctly setsid in tty.open GH-815\r
-<li> Bug fix for failed buffer construction\r
-<li> Added support for removing .once listeners (GH-806)\r
-<li> Upgrade V8 to 3.1.8.5</ul>\r
-\r
-\r
-\r
-Download: <a href="http://nodejs.org/dist/node-v0.4.4.tar.gz">http://nodejs.org/dist/node-v0.4.4.tar.gz</a>\r
-\r
-Website: <a href="http://nodejs.org/docs/v0.4.4/">http://nodejs.org/docs/v0.4.4</a>\r
-\r
-Documentation: <a href="http://nodejs.org/docs/v0.4.4/api/">http://nodejs.org/docs/v0.4.4/api</a>\r
-\r
+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>
category: release
slug: node-v0-4-5
-2011.04.01, Version 0.4.5 (stable)\r
-<ul>\r
-<li> Fix listener leak in stream.pipe() (Mikeal Rogers)\r
-<li> Retain buffers in fs.read/write() GH-814 (Jorge Chamorro Bieling)\r
-<li> TLS performance improvements\r
-<li> SlowBuffer.prototype.slice bug GH-843\r
-<li> process.stderr.write should return true\r
-<li> Immediate pause/resume race condition GH-535 (isaacs)\r
-<li> Set default host header properly GH-721 (isaacs)\r
-<li> Upgrade V8 to 3.1.8.8</ul>\r
-\r
-\r
-\r
-Download: <a href="http://nodejs.org/dist/node-v0.4.5.tar.gz">http://nodejs.org/dist/node-v0.4.5.tar.gz</a>\r
-\r
-Website: <a href="http://nodejs.org/docs/v0.4.5">http://nodejs.org/docs/v0.4.5</a>\r
-\r
-Documentation: <a href="http://nodejs.org/docs/v0.4.5/api">http://nodejs.org/docs/v0.4.5/api</a>\r
-\r
-\r
+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>
category: release
slug: node-v0-4-6
-2011.04.13, Version 0.4.6 (stable)\r
-<ul><li> Don't error on ENOTCONN from shutdown() #670\r
-<li> Auto completion of built-in debugger suggests prefix match rather than partial match. (koichik)\r
-<li> circular reference in vm modules. #822 (Jakub Lekstan)\r
-<li> http response.readable should be false after 'end' #867 (Abe Fettig)\r
-<li> Implemenet os.cpus() and os.uptime() on Solaris (Scott McWhirter)\r
-<li> fs.ReadStream: Allow omission of end option for range reads #801 (Felix Geisendörfer)\r
-<li> Buffer.write() with UCS-2 should not be write partial char #916 (koichik)\r
-<Li> Pass secureProtocol through on tls.Server creation (Theo Schlossnagle)\r
-<li> TLS use RC4-SHA by default\r
-<li> Don't strangely drop out of event loop on HTTPS client uploads #892\r
-<li> Doc improvements\r
-<li> Upgrade v8 to 3.1.8.10</ul>\r
-\r
-Download: <a href="http://nodejs.org/dist/node-v0.4.6.tar.gz">http://nodejs.org/dist/node-v0.4.6.tar.gz</a>\r
-\r
-Website: <a href="http://nodejs.org/docs/v0.4.6/">http://nodejs.org/docs/v0.4.6/</a>\r
-\r
+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>
category: release
slug: node-v0-4-7
-2011.04.22, Version 0.4.7 (stable)\r
-<ul><li> Don't emit error on ECONNRESET from read() #670\r
-<li> Fix: Multiple pipes to the same stream were broken #929 (Felix Geisendörfer)\r
-<li> URL parsing/formatting corrections #954 (isaacs)\r
-<li> make it possible to do repl.start('', stream) (Wade Simmons)\r
-<li> Add os.loadavg for SunOS (Robert Mustacchi)\r
-<li> Fix timeouts with floating point numbers #897 (Jorge Chamorro Bieling)\r
-<li> Improve docs.</ul>\r
-\r
-\r
-Download: <a href="http://nodejs.org/dist/node-v0.4.7.tar.gz">http://nodejs.org/dist/node-v0.4.7.tar.gz</a>\r
-\r
-Website: <a href="http://nodejs.org/docs/v0.4.7/">http://nodejs.org/docs/v0.4.7/</a>\r
-\r
+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>
category: release
slug: node-v0-4-8
-2011.05.20, Version 0.4.8 (stable)\r
-\r
-* #974 Properly report traceless errors (isaacs)\r
-\r
-* #983 Better JSON.parse error detection in REPL (isaacs)\r
-\r
-* #836 Agent socket errors bubble up to req only if req exists\r
-\r
-* #1041 Fix event listener leak check timing (koichik)\r
-\r
-* #1038 Fix dns.resolve() with 'PTR' throws Error: Unknown type "PTR"\r
- (koichik)\r
-\r
-* #1073 Share SSL context between server connections (Fedor Indutny)\r
-\r
-* Disable compression with OpenSSL. Improves memory perf.\r
-\r
-* Implement os.totalmem() and os.freemem() for SunOS (Alexandre Marangone)\r
-\r
-* Fix a special characters in URL regression (isaacs)\r
-\r
-* Fix idle timeouts in HTTPS (Felix Geisendörfer)\r
-\r
-* SlowBuffer.write() with 'ucs2' throws ReferenceError. (koichik)\r
-\r
-* http.ServerRequest 'close' sometimes gets an error argument\r
- (Felix Geisendörfer)\r
-\r
-* Doc improvements\r
-\r
-* cleartextstream.destroy() should close(2) the socket. Previously was being\r
- mapped to a shutdown(2) syscall.\r
-\r
-* No longer compile out asserts and debug statements in normal build.\r
-\r
-* Debugger improvements.\r
-\r
-* Upgrade V8 to 3.1.8.16.\r
-\r
-\r
-\r
-\r
-Website: <a href="http://nodejs.org/docs/v0.4.8/">http://nodejs.org/docs/v0.4.8/</a>\r
-\r
-Download: <a href="http://nodejs.org/dist/node-v0.4.8.tar.gz">http://nodejs.org/dist/node-v0.4.8.tar.gz</a>\r
-\r
+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>
category: release
slug: node-v0-4-9
-2011.06.29, Version 0.4.9 (stable)<ul>\r
-<li> Improve documentation\r
-<li> #1095 error handling bug in stream.pipe() (Felix Geisendörfer)\r
-<li> #1097 Fix a few leaks in node_crypto.cc (Ben Noordhuis)\r
-<li> #562 #1078 Parse file:// urls properly (Ryan Petrello)\r
-<li> #880 Option to disable SSLv2 (Jérémy Lal)\r
-<li> #1087 Disabling SSL compression disabled with early OpenSSLs.\r
-<li> #1144 debugger: don't allow users to input non-valid commands (Siddharth Mahendraker)\r
-<li> Perf improvement for util.inherits\r
-<li> #1166 Support for signature verification with RSA/DSA public keys (Mark Cavage)\r
-<li> #1177 Remove node_modules lookup optimization to better support nested project structures (Mathias Buus)\r
-<li> #1203 Add missing scope.Close to fs.sendfileSync\r
-<li> #1187 Support multiple 'link' headers\r
-<li> #1196 Fix -e/--eval can't load module from node_modules (Koichi Kobayashi)\r
-<li> Upgrade V8 to 3.1.8.25, upgrade http-parser.</ul>\r
-\r
-\r
-Download: <a href="http://nodejs.org/dist/node-v0.4.9.tar.gz">http://nodejs.org/dist/node-v0.4.9.tar.gz</a>\r
-\r
-Website: <a href="http://nodejs.org/docs/v0.4.9">http://nodejs.org/docs/v0.4.9</a>\r
-\r
+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>
category: release
slug: node-v0-5-0-unstable
-2011.07.05, Version 0.5.0 (unstable)\r
-\r
-<li> New non-default libuv backend to support IOCP on Windows. Use <code>--use-uv</code> to enable.\r
-<li> deprecate http.cat\r
-<li> docs improved.\r
-<li> add child_process.fork\r
-<li> add fs.utimes() and fs.futimes() support (Ben Noordhuis)\r
-<li> add process.uptime() (Tom Huges)\r
-<li> add path.relative (Tony Huang)\r
-<li> add os.getNetworkInterfaces()\r
-<li> add remoteAddress and remotePort for client TCP connections (Brian White)\r
-<li> add secureOptions flag, setting ciphers, SSL_OP_CRYPTOPRO_TLSEXT_BUG to TLS (Theo Schlossnagle)\r
-<li> add process.arch (Nathan Rajlich)\r
-<li> add reading/writing of floats and doubles from/to buffers (Brian White)\r
-<li> Allow script to be read from stdin\r
-<li> #477 add Buffer::fill method to do memset (Konstantin Käfer)\r
-<li> #573 Diffie-Hellman support to crypto module (Håvard Stranden)\r
-<li> #695 add 'hex' encoding to buffer (isaacs)\r
-<li> #851 Update how REPLServer uses contexts (Ben Weaver)\r
-<li> #853 add fs.lchow, fs.lchmod, fs.fchmod, fs.fchown (isaacs)\r
-<li> #889 Allow to remove all EventEmitter listeners at once (Felix Geisendörfer)\r
-<li> #926 OpenSSL NPN support (Fedor Indutny)\r
-<li> #955 Change ^C handling in REPL (isaacs)\r
-<li> #979 add support for Unix Domain Sockets to HTTP (Mark Cavage)\r
-<li> #1173 #1170 add AMD, asynchronous module definition (isaacs)\r
-<li> DTrace probes: support X-Forwarded-For (Dave Pacheco) </ul>\r
-Download: <a href="http://nodejs.org/dist/node-v0.5.0.tar.gz">http://nodejs.org/dist/node-v0.5.0.tar.gz</a>\r
-\r
-Website: <a href="http://nodejs.org/docs/v0.5.0/">http://nodejs.org/docs/v0.5.0/</a>\r
-\r
+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>
category: release
slug: node-v0-5-1
-2011.07.14, Version 0.5.1 (unstable)\r
-<ul><li> #1233 Fix os.totalmem on FreeBSD amd64 (Artem Zaytsev)\r
-<li> #1149 IDNA and Punycode support in url.parse (Jeremy Selier, Ben Noordhuis, isaacs)\r
-<li> Export $CC and $CXX to uv and V8's build systems\r
-<li> Include pthread-win32 static libraries in build (Igor Zinkovsky)\r
-<li> #1199, #1094 Fix fs can't handle large file on 64bit platform (koichik)\r
-<li> #1281 Make require a public member of module (isaacs)\r
-<li> #1303 Stream.pipe returns the destination (Elijah Insua)\r
-<li> #1229 Addons should not -DEV_MULTIPLICITY=0 (Brian White)\r
-<li> libuv backend improvements\r
-<li> Upgrade V8 to 3.4.10</ul>\r
-\r
-\r
-\r
-\r
-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>\r
-\r
-Windows Build: <a href="http://nodejs.org/dist/v0.5.1/node.exe">http://nodejs.org/dist/v0.5.1/node.exe</a>\r
-\r
-Documentation: <a href="http://nodejs.org/dist/v0.5.1/docs/api/">http://nodejs.org/dist/v0.5.1/docs/api/</a>\r
-\r
+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>
category: release
slug: node-v0-5-10
-2011.10.21, Version 0.5.10 (unstable)\r
-<ul><li>Remove cmake build system, support for Cygwin, legacy code base, process.ENV, process.ARGV, process.memoryUsage().vsize, os.openOSHandle</li>\r
-<li>Documentation improvments (Igor Zinkovsky, Bert Belder, Ilya Dmitrichenko, koichik, Maciej Małecki, Guglielmo Ferri, isaacs)</li>\r
-<li>Performance improvements (Daniel Ennis, Bert Belder, Ben Noordhuis) </li>\r
-<li>Long process.title support (Ben Noordhuis)</li>\r
-<li>net: register net.Server callback only once (Simen Brekken)</li>\r
-<li>net: fix connect queue bugs (Ben Noordhuis)</li>\r
-<li>debugger: fix backtrace err handling (Fedor Indutny)</li>\r
-<li>Use getaddrinfo instead of c-ares for dns.lookup</li>\r
-<li>Emit 'end' from crypto streams on close</li>\r
-<li>repl: print out `undefined` (Nathan Rajlich)</li>\r
-<li>#1902 buffer: use NO_NULL_TERMINATION flag (koichik)</li>\r
-<li>#1907 http: Added support for HTTP PATCH verb (Thomas Parslow)</li>\r
-<li>#1644 add GetCPUInfo on windows (Karl Skomski)</li>\r
-<li>#1484, #1834, #1482, #771 Don't use a separate context for the repl. (isaacs)</li>\r
-<li>#1882 zlib Update 'availOutBefore' value, and test (isaacs)</li>\r
-<li>#1888 child_process.fork: don't modify args (koichik)</li>\r
-<li>#1516 tls: requestCert unusable with Firefox and Chrome (koichik)</li>\r
-<li>#1467 tls: The TLS API is inconsistent with the TCP API (koichik)</li>\r
-<li>#1894 net: fix error handling in listen() (koichik)</li>\r
-<li>#1860 console.error now goes through uv_tty_t</li>\r
-<li>Upgrade V8 to 3.7.0</li>\r
-<li>Upgrade GYP to r1081</li></ul>\r
-\r
-\r
-\r
-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>\r
-\r
-Windows Executable: <a href="http://nodejs.org/dist/v0.5.10/node.exe">http://nodejs.org/dist/v0.5.10/node.exe</a>\r
-\r
-Website: <a href="http://nodejs.org/docs/v0.5.10/">http://nodejs.org/docs/v0.5.10/</a>\r
-\r
+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>
category: release
slug: node-v0-5-2
-2011.07.22, Version 0.5.2 (unstable)\r
-<ul><li>libuv improvements; named pipe support\r
-<li>#1242 check for SSL_COMP_get_compression_methods() (Ben Noordhuis)\r
-<li>#1348 remove require.paths (isaacs)\r
-<li>#1349 Delimit NODE_PATH with ; on Windows (isaacs)\r
-<li>#1335 Remove EventEmitter from C++\r
-<li>#1357 Load json files with require() (isaacs)\r
-<li>#1374 fix setting ServerResponse.statusCode in writeHead (Trent Mick)\r
-<li>Fixed: GC was being run too often.\r
-<li>Upgrade V8 to 3.4.14\r
-<li>doc improvements</ul>\r
-\r
-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>\r
-\r
-Windows Executable: <a href="http://nodejs.org/dist/v0.5.2/node.exe">http://nodejs.org/dist/v0.5.2/node.exe</a>\r
-\r
-Website: <a href="http://nodejs.org/dist/v0.5.2/docs/">http://nodejs.org/dist/v0.5.2/docs/</a>\r
-\r
+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>
category: release
slug: node-v0-5-3
-2011.08.01, Version 0.5.3 (unstable)\r
-\r
-<ul><li>Fix crypto encryption/decryption with Base64. (SAWADA Tadashi)\r
-\r
-<li>#243 Add an optional length argument to Buffer.write() (koichik)\r
-\r
-<li>#657 convert nonbuffer data to string in fs.writeFile/Sync (Daniel Pihlström)\r
-\r
-<li>Add process.features, remove process.useUV (Ben Noordhuis)\r
-\r
-<li>#324 Fix crypto hmac to accept binary keys + add test cases from rfc 2202 and 4231 (Stefan Bühler)\r
-\r
-<li>Add Socket::bytesRead, Socket::bytesWritten (Alexander Uvarov)\r
-\r
-<li>#572 Don't print result of --eval in CLI (Ben Noordhuis)\r
-\r
-<li>#1223 Fix http.ClientRequest crashes if end() was called twice (koichik)\r
-\r
-<li>#1383 Emit 'close' after all connections have closed (Felix Geisendörfer)\r
-\r
-<li>Add sprintf-like util.format() function (Ben Noordhuis)\r
-\r
-<li>Add support for TLS SNI (Fedor Indutny)\r
-\r
-<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)\r
-\r
-<li>Revert AMD compatibility. (isaacs)\r
-\r
-<li>Windows: improvements, child_process support.\r
-\r
-<li>Remove pkg-config file.\r
-\r
-<li>Fix startup time regressions.\r
-\r
-<li>doc improvements</ul>\r
-\r
-\r
-\r
-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>\r
-\r
-Windows Executable: <a href="http://nodejs.org/dist/v0.5.3/node.exe">http://nodejs.org/dist/v0.5.3/node.exe</a>\r
-\r
-Website: <a href="http://nodejs.org/dist/v0.5.3/docs">http://nodejs.org/dist/v0.5.3/docs</a>\r
-\r
+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>
category: release
slug: node-v0-5-4
-2011.08.12, Version 0.5.4 (unstable)\r
-\r
-<ul><li>libuv/Windows compatibility improvements\r
-\r
-<li>Build on Microsoft Visual Studio via GYP. Use generate-projects.bat in the to build sln files. (Peter Bright, Igor Zinkovsky)\r
-\r
-<li>Make Mikeal's HTTP agent client the default. Use old HTTP client with <code>--use-http1</code>\r
-\r
-<li>Fixes https host header default port handling. (Mikeal Rogers)\r
-\r
-<li>#1440 strip byte order marker when loading *.js and *.json files (Ben Noordhuis)\r
-\r
-<li>#1434 Improve util.format() compatibility with browser. (Koichi Kobayashi)\r
-\r
-<li>Provide unchecked uint entry points for integer Buffer.read/writeInt methods. (Robert Mustacchi)\r
-\r
-<li>CMake improvements (Tom Huges)\r
-\r
-<li>Upgrade V8 to 3.5.4.</ul>\r
-\r
-\r
-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>\r
-\r
-Windows Executable: <a href="http://nodejs.org/dist/v0.5.4/node.exe">http://nodejs.org/dist/v0.5.4/node.exe</a>\r
-\r
-Website: <a href="http://nodejs.org/dist/v0.5.4/docs">http://nodejs.org/dist/v0.5.4/docs</a>\r
-\r
+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>
category: release
slug: node-v0-5-5
-<p>2011.08.26, Version 0.5.5 (unstable)</p>\r
-<ul>\r
-<li>typed arrays, implementation from Plesk\r
-<li>fix IP multicast on SunOS\r
-<li>fix DNS lookup order: IPv4 first, IPv6 second (--use-uv only)\r
-<li>remove support for UNIX datagram sockets (--use-uv only)\r
-<li>UDP support for Windows (Bert Belder)\r
-<li>#1572 improve tab completion for objects in the REPL (Nathan Rajlich)\r
-<li>#1563 fix buffer overflow in child_process module (reported by Dean McNamee)\r
-<li>#1546 fix performance regression in http module (reported by Brian Geffon)\r
-<li>#1491 add PBKDF2 crypto support (Glen Low)\r
-<li>#1447 remove deprecated http.cat() function (Mikeal Rogers)\r
-<li>#1140 fix incorrect dispatch of vm.runInContext's filename argument<br />\r
- (Antranig Basman)</p>\r
-<li>#1140 document vm.runInContext() and vm.createContext() (Antranig Basman)\r
-<li>#1428 fix os.freemem() on 64 bits freebsd (Artem Zaytsev)\r
-<li>#1164 make all DNS lookups async, fixes uncatchable exceptions<br />\r
- (Koichi Kobayashi)</p>\r
-<li>fix incorrect ssl shutdown check (Tom Hughes)\r
-<li>various cmake fixes (Tom Hughes)\r
-<li>improved documentation (Koichi Kobayashi, Logan Smyth, Fedor Indutny,<br />\r
- Mikeal Rogers, Maciej Małecki, Antranig Basman, Mickaël Delahaye)</p>\r
-<li>upgrade libuv to commit 835782a\r
-<li>upgrade V8 to 3.5.8\r
-</ul>\r
-<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>\r
-<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>\r
-<p>Website: <a href="http://nodejs.org/docs/v0.5.5/">http://nodejs.org/docs/v0.5.5/</a></p>\r
-<p>Documentation: <a href="http://nodejs.org/docs/v0.5.5/api/">http://nodejs.org/docs/v0.5.5/api/</a></p>\r
-<br /><br />\r
-\r
+<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>.
category: release
slug: node-v0-5-6
-2011.09.08, Version 0.5.6 (unstable)\r
-<ul>\r
- <li>#345, #1635, #1648 Documentation improvements (Thomas Shinnick, Abimanyu Raja, AJ ONeal, Koichi Kobayashi, Michael Jackson, Logan Smyth, Ben Noordhuis)</li>\r
- <li>#650 Improve path parsing on windows (Bert Belder)</li>\r
- <li>#752 Remove headers sent check in OutgoingMessage.getHeader() (Peter Lyons)</li>\r
- <li>#1236, #1438, #1506, #1513, #1621, #1640, #1647 Libuv-related bugs fixed (Jorge Chamorro Bieling, Peter Bright, Luis Lavena, Igor Zinkovsky)</li>\r
- <li>#1296, #1612 crypto: Fix BIO's usage. (Koichi Kobayashi)</li>\r
- <li>#1345 Correctly set socket.remoteAddress with libuv backend (Bert Belder)</li>\r
- <li>#1429 Don't clobber quick edit mode on windows (Peter Bright)</li>\r
- <li>#1503 Make libuv backend default on unix, override with `node --use-legacy`</li>\r
- <li>#1565 Fix fs.stat for paths ending with \ on windows (Igor Zinkovsky)</li>\r
- <li>#1568 Fix x509 certificate subject parsing (Koichi Kobayashi)</li>\r
- <li>#1586 Make socket write encoding case-insensitive (Koichi Kobayashi)</li>\r
- <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>\r
- <li>#1592 Don't load-time link against CreateSymbolicLink on windows (Peter Bright)</li>\r
- <li>#1601 Improve API consistency when dealing with the socket underlying a HTTP client request (Mikeal Rogers)</li>\r
- <li>#1610 Remove DigiNotar CA from trusted list (Isaac Schlueter)</li>\r
- <li>#1617 Added some win32 os functions (Karl Skomski)</li>\r
- <li>#1624 avoid buffer overrun with 'binary' encoding (Koichi Kobayashi)</li>\r
- <li>#1633 make Buffer.write() always set _charsWritten (Koichi Kobayashi)</li>\r
- <li>#1644 Windows: set executables to be console programs (Peter Bright)</li>\r
- <li>#1651 improve inspection for sparse array (Koichi Kobayashi)</li>\r
- <li>#1672 set .code='ECONNRESET' on socket hang up errors (Ben Noordhuis)</li>\r
- <li>Add test case for foaf+ssl client certificate (Niclas Hoyer)</li>\r
- <li>Added RPATH environment variable to override run-time library paths (Ashok Mudukutore)</li>\r
- <li>Added TLS client-side session resumption support (Sean Cunningham)</li>\r
- <li>Added additional properties to getPeerCertificate (Nathan Rixham, Niclas Hoyer)</li>\r
- <li>Don't eval repl command twice when an error is thrown (Nathan Rajlich)</li>\r
- <li>Improve util.isDate() (Nathan Rajlich)</li>\r
- <li>Improvements in libuv backend and bindings, upgrade libuv to bd6066cb349a9b3a1b0d87b146ddaee06db31d10</li>\r
- <li>Show warning when using lib/sys.js (Maciej Malecki)</li>\r
- <li>Support plus sign in url protocol (Maciej Malecki)</li>\r
- <li>Upgrade V8 to 3.6.2</li>\r
-</ul>\r
-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>\r
-\r
-Windows Executable: <a href="http://nodejs.org/dist/v0.5.6/node.exe">http://nodejs.org/dist/v0.5.6/node.exe</a>\r
-\r
-Website: <a href="http://nodejs.org/docs/v0.5.6/">http://nodejs.org/docs/v0.5.6/</a>\r
-\r
+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>
category: release
slug: node-v0-5-7-unstable
-2011.09.16, Version 0.5.7 (unstable)\r
-<ul>\r
-<li>Upgrade V8 to 3.6.4\r
-<li>Improve Windows compatibility\r
-<li>Documentation improvements\r
-<li>Debugger and REPL improvements (Fedor Indutny)\r
-<li>Add legacy API support: net.Stream(fd), process.stdout.writable, process.stdout.fd\r
-<li>Fix mkdir EEXIST handling (isaacs)\r
-<li>Use net_uv instead of net_legacy for stdio\r
-<li>Do not load readline from util.inspect\r
-<li>#1673 Fix bug related to V8 context with accessors (Fedor Indutny)\r
-<li>#1634 util: Fix inspection for Error (koichik)\r
-<li>#1645 fs: Add positioned file writing feature to fs.WriteStream (Thomas Shinnick)\r
-<li>#1637 fs: Unguarded fs.watchFile cache statWatchers checking fixed (Thomas Shinnick)\r
-<li>#1695 Forward customFds to ChildProcess.spawn\r
-<li>#1707 Fix hasOwnProperty security problem in querystring (isaacs)\r
-<li>#1719 Drain OpenSSL error queue</ul>\r
-\r
-\r
-\r
-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>\r
-\r
-Windows Executable: <a href="http://nodejs.org/dist/v0.5.7/node.exe">http://nodejs.org/dist/v0.5.7/node.exe</a>\r
-\r
-Website: <a href="http://nodejs.org/docs/v0.5.7/">http://nodejs.org/docs/v0.5.7/</a>\r
-\r
+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>
category: release
slug: node-v0-5-8
-2011.09.30, Version 0.5.8 (unstable)<ul><li>zlib bindings (isaacs)\r
-<li>Windows supports TTY ANSI escape codes (Bert Belder)\r
-<li>Debugger improvements (Fedor Indutny)\r
-<li>crypto: look up SSL errors with ERR_print_errors() (Ben Noordhuis)\r
-<li>dns callbacks go through MakeCallback now\r
-<li>Raise an error when a malformed package.json file is found. (Ben Leslie)\r
-<li>buffers: handle bad length argument in constructor (Ben Noordhuis)\r
-<li>#1726, unref process.stdout\r
-<li>Doc improvements (Ben Noordhuis, Fedor Indutny, koichik)\r
-<li>Upgrade libuv to fe18438</ul>\r
-\r
-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>\r
-\r
-Windows Executable: <a href="http://nodejs.org/dist/v0.5.8/node.exe">http://nodejs.org/dist/v0.5.8/node.exe</a>\r
-\r
-Website: <a href="http://nodejs.org/docs/v0.5.8/">http://nodejs.org/docs/v0.5.8/</a>\r
-\r
+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>
category: release
slug: node-v0-5-9
-2011.10.10, Version 0.5.9 (unstable)\r
-<ul><li>fs.watch interface backed by kqueue, inotify, and ReadDirectoryChangesW (Igor Zinkovsky, Ben Noordhuis)</li>\r
-<li>add dns.resolveTxt (Christian Tellnes)</li>\r
-<li>Remove legacy http library (Ben Noordhuis)</li>\r
-<li>child_process.fork returns and works on Windows. Allows passing handles. (Igor Zinkovsky, Bert Belder)</li>\r
-<li>#1774 Lint and clean up for --harmony_block_scoping (Tyler Larson, Colton Baker)</li>\r
-<li>#1813 Fix ctrl+c on Windows (Bert Belder)</li>\r
-<li>#1844 unbreak --use-legacy (Ben Noordhuis)</li>\r
-<li>process.stderr now goes through libuv. Both process.stdout and process.stderr are blocking when referencing a TTY.</li>\r
-<li>net_uv performance improvements (Ben Noordhuis, Bert Belder)</li></ul>\r
-\r
-\r
-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>\r
-\r
-Windows Executable: <a href="http://nodejs.org/dist/v0.5.9/node.exe">http://nodejs.org/dist/v0.5.9/node.exe</a>\r
-\r
-Website: <a href="http://nodejs.org/docs/v0.5.9/">http://nodejs.org/docs/v0.5.9/</a>\r
-\r
+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>
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.\r
-\r
-The major differences between v0.4 and v0.6 are<ul>\r
-<li>Native Windows support using I/O Completion Ports for sockets.\r
-<li>Integrated load balancing over multiple processes. <a href="http://nodejs.org/docs/v0.6.0/api/cluster.html">docs</a>\r
-<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>\r
-<li>Improved command line debugger <a href="http://nodejs.org/docs/v0.6.0/api/debugger.html">docs</a>\r
-<li>Built-in binding to zlib for compression <a href="http://nodejs.org/docs/v0.6.0/api/zlib.html">docs</a>\r
-<li>Upgrade v8 from 3.1 to 3.6</ul>\r
-\r
-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:\r
-\r
-<table><tr> <th></th> <th>v0.4.12 (linux)</th><th>v0.6.0 (linux)</th></tr>\r
-<tr> <td>http_simple.js /bytes/1024</td> <td>5461 r/s</td> <td>6263 r/s</td> </tr>\r
-<tr> <td>io.js read </td> <td>19.75 mB/s</td> <td>26.63 mB/s</td> </tr>\r
-<tr> <td>io.js write </td> <td>21.60 mB/s</td> <td>17.40 mB/s</td> </tr>\r
-<tr> <td>startup.js </td> <td>74.7 ms</td> <td>49.6 ms</td> </tr></table>\r
-\r
-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.\r
-\r
-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:\r
-\r
-<table><tr><th></th><th>v0.4.12 (windows)</th><th>v0.6.0 (windows)</th></tr>\r
-<tr> <td>http_simple.js /bytes/1024</td> <td>3858 r/s</td> <td>5823 r/s</td> </tr>\r
-<tr> <td>io.js read </td> <td>12.41 mB/s</td> <td>26.51 mB/s</td> </tr>\r
-<tr> <td>io.js write </td> <td>12.61 mB/s</td> <td>33.58 mB/s</td> </tr>\r
-<tr> <td>startup.js </td> <td>152.81 ms</td> <td>52.04 ms</td> </tr></table>\r
-\r
-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.\r
-\r
-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. \r
-\r
-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.\r
-\r
-Thank you to everyone who contributed code, tests, docs, or sent in bug reports.\r
-\r
-Here are the changes between v0.5.12 and v0.6.0:\r
-\r
-2011.11.04, Version 0.6.0 (stable)\r
-<ul><li>print undefined on undefined values in REPL (Nathan Rajlich)</li>\r
-<li>doc improvements (koichik, seebees, bnoordhuis, Maciej Małecki, Jacob Kragh)</li>\r
-<li>support native addon loading in windows (Bert Belder)</li>\r
-<li>rename getNetworkInterfaces() to networkInterfaces() (bnoordhuis)</li>\r
-<li>add pending accepts knob for windows (igorzi)</li>\r
-<li>http.request(url.parse(x)) (seebees)</li>\r
-<li>#1929 zlib Respond to 'resume' events properly (isaacs)</li>\r
-<li>stream.pipe: Remove resume and pause events</li>\r
-<li>test fixes for windows (igorzi)</li>\r
-<li>build system improvements (bnoordhuis)</li>\r
-<li>#1936 tls: does not emit 'end' from EncryptedStream (koichik)</li>\r
-<li>#758 tls: add address(), remoteAddress/remotePort</li>\r
-<li>#1399 http: emit Error object after .abort() (bnoordhuis)</li>\r
-<li>#1999 fs: make mkdir() default to 0777 permissions (bnoordhuis)</li>\r
-<li>#2001 fix pipe error codes</li>\r
-<li>#2002 Socket.write should reset timeout timer</li>\r
-<li>stdout and stderr are blocking when associated with file too.</li>\r
-<li>remote debugger support on windows (Bert Belder)</li>\r
-<li>convenience methods for zlib (Matt Robenolt)</li>\r
-<li>process.kill support on windows (igorzi)</li>\r
-<li>process.uptime() support on windows (igorzi)</li>\r
-<li>Return IPv4 addresses before IPv6 addresses from getaddrinfo</li>\r
-<li>util.inspect improvements (Nathan Rajlich)</li>\r
-<li>cluster module api changes</li>\r
-<li>Downgrade V8 to 3.6.6.6</li></ul>\r
-\r
-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>\r
-\r
-Windows Executable: <a href="http://nodejs.org/dist/v0.6.0/node.exe">http://nodejs.org/dist/v0.6.0/node.exe</a>\r
-\r
-Website: <a href="http://nodejs.org/docs/v0.6.0/">http://nodejs.org/docs/v0.6.0/</a>\r
-\r
+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>
category: release
slug: node-v0-6-1
-2011.11.11, Version 0.6.1 (stable)\r
-<ul><li>doc improvements (Eric Lovett, Ben Noordhuis, Scott Anderson, Yoji SHIDARA)</li>\r
-<li>crypto: make thread-safe (Ben Noordhuis)</li>\r
-<li>fix process.kill error object</li>\r
-<li>debugger: correctly handle source with multi-byte characters (Shigeki Ohtsu)</li>\r
-<li>make stdout and stderr non-destroyable (Igor Zinkovsky)</li>\r
-<li>fs: don't close uninitialized fs.watch handle (Ben Noordhuis)</li>\r
-<li>#2026 fix man page install on BSDs (Ben Noordhuis)</li>\r
-<li>#2040 fix unrecognized errno assert in uv_err_name</li>\r
-<li>#2043 fs: mkdir() should call callback if mode is omitted</li>\r
-<li>#2045 fs: fix fs.realpath on windows to return on error (Benjamin Pasero)</li>\r
-<li>#2047 minor cluster improvements</li>\r
-<li>#2052 readline get window columns correctly</li>\r
-<li>Upgrade V8 to 3.6.6.7</li></ul>\r
-\r
-\r
-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>\r
-\r
-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>\r
-\r
-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>\r
-\r
-Website: <a href="http://nodejs.org/docs/v0.6.1/">http://nodejs.org/docs/v0.6.1/</a>\r
-\r
+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>
category: release
slug: node-v0-6-10
-<p>2012.02.02, Version 0.6.10 (stable)</p>\r
-\r
-<ul>\r
-<li><p>Update V8 to 3.6.6.20</p></li>\r
-<li><p>Add npm msysgit bash shim to msi installer (isaacs)</p></li>\r
-<li><p>buffers: fix intermittent out of bounds error (Ben Noordhuis)</p></li>\r
-<li><p>buffers: honor length argument in base64 decoder (Ben Noordhuis)</p></li>\r
-<li><p>windows: Fix path.exists regression (Bert Belder)</p></li>\r
-<li><p>Make QueryString.parse run faster (Philip Tellis)</p></li>\r
-<li><p>http: avoid freeing http-parser objects too early (koichik)</p></li>\r
-<li><p>timers: add v0.4 compatibility hack (Ben Noordhuis)</p></li>\r
-<li><p>Proper EPERM error code support (Igor Zinkovsky, Brandon Philips)</p></li>\r
-<li><p>dgram: Implement udp multicast methods on windows (Bert Belder)</p></li>\r
-</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>\r
-\r
-<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>\r
-\r
-<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>\r
-\r
-<p>Website: <a href="http://nodejs.org/docs/v0.6.10/">http://nodejs.org/docs/v0.6.10/</a></p>\r
-\r
+<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>
category: release
slug: node-v0-6-2
-<p>2011.11.18, Version 0.6.2 (stable)</p>\r
-<ul>\r
-<li>doc improvements (Artur Adib, Trevor Burnham, Ryan Emery, Trent Mick)</li>\r
-<li>timers: remember extra setTimeout() arguments when timeout==0</li>\r
-<li>punycode: use Mathias Bynens's punycode library, it's more compliant</li>\r
-<li>repl: improved tab completion (Ryan Emery)</li>\r
-<li>buffer: fix range checks in .writeInt() functions (Lukasz Walukiewicz)</li>\r
-<li>tls: make cipher list configurable</li>\r
-<li>addons: make Buffer and ObjectWrap visible to Windows add-ons (Bert Belder)</li>\r
-<li>crypto: add PKCS#1 a.k.a RSA public key verification support</li>\r
-<li>windows: fix stdout writes when redirected to nul</li>\r
-<li>sunos: fix build on Solaris and Illumos</li>\r
-<li>Upgrade V8 to 3.6.6.8</li>\r
-</ul>\r
-<p>Source Code: <a href="http://nodejs.org/dist/v0.6.2/node-v0.6.2.tar.gz">http://nodejs.org/dist/v0.6.2/node-v0.6.2.tar.gz</a></p>\r
-<p>Windows Installer: <a href="http://nodejs.org/dist/v0.6.2/node-v0.6.2.msi">http://nodejs.org/dist/v0.6.2/node-v0.6.2.msi</a></p>\r
-<p>Macintosh Installer: <a href="http://nodejs.org/dist/v0.6.2/node-v0.6.2.pkg">http://nodejs.org/dist/v0.6.2/node-v0.6.2.pkg</a></p>\r
-<p>Website: <a href="http://nodejs.org/docs/v0.6.2/">http://nodejs.org/docs/v0.6.2/</a></p>\r
+<p>2011.11.18, Version 0.6.2 (stable)</p>
+<ul>
+<li>doc improvements (Artur Adib, Trevor Burnham, Ryan Emery, Trent Mick)</li>
+<li>timers: remember extra setTimeout() arguments when timeout==0</li>
+<li>punycode: use Mathias Bynens's punycode library, it's more compliant</li>
+<li>repl: improved tab completion (Ryan Emery)</li>
+<li>buffer: fix range checks in .writeInt() functions (Lukasz Walukiewicz)</li>
+<li>tls: make cipher list configurable</li>
+<li>addons: make Buffer and ObjectWrap visible to Windows add-ons (Bert Belder)</li>
+<li>crypto: add PKCS#1 a.k.a RSA public key verification support</li>
+<li>windows: fix stdout writes when redirected to nul</li>
+<li>sunos: fix build on Solaris and Illumos</li>
+<li>Upgrade V8 to 3.6.6.8</li>
+</ul>
+<p>Source Code: <a href="http://nodejs.org/dist/v0.6.2/node-v0.6.2.tar.gz">http://nodejs.org/dist/v0.6.2/node-v0.6.2.tar.gz</a></p>
+<p>Windows Installer: <a href="http://nodejs.org/dist/v0.6.2/node-v0.6.2.msi">http://nodejs.org/dist/v0.6.2/node-v0.6.2.msi</a></p>
+<p>Macintosh Installer: <a href="http://nodejs.org/dist/v0.6.2/node-v0.6.2.pkg">http://nodejs.org/dist/v0.6.2/node-v0.6.2.pkg</a></p>
+<p>Website: <a href="http://nodejs.org/docs/v0.6.2/">http://nodejs.org/docs/v0.6.2/</a></p>
<p>Documentation: <a href="http://nodejs.org/docs/v0.6.2/api/">http://nodejs.org/docs/v0.6.2/api/</a></p>
category: release
slug: node-v0-6-3
-2011.11.25, Version 0.6.3 (stable)\r
-<ul>\r
- <li>#2083 Land NPM in Node. It is included in packages/installers and installed on `make install`.</li>\r
- <li>#2076 Add logos to windows installer.</li>\r
- <li>#1711 Correctly handle http requests without headers. (Ben Noordhuis, Felix Geisendörfer)</li>\r
- <li>TLS: expose more openssl SSL context options and constants. (Ben Noordhuis)</li>\r
- <li>#2177 Windows: don't kill UDP socket when a packet fails to reach its destination. (Bert Belder)</li>\r
- <li>Windows: support paths longer than 260 characters. (Igor Zinkovsky)</li>\r
- <li>Windows: correctly resolve drive-relative paths. (Bert Belder)</li>\r
- <li>#2166 Don't leave file descriptor open after lchmod. (Isaac Schlueter)</li>\r
- <li>#2084 Add OS X .pkg build script to make file.</li>\r
- <li>#2160 Documentation improvements. (Ben Noordhuis)</li>\r
-</ul>\r
-Source Code: <a href="http://nodejs.org/dist/v0.6.3/node-v0.6.3.tar.gz">http://nodejs.org/dist/v0.6.3/node-v0.6.3.tar.gz</a>\r
-\r
-Windows Installer: <a href="http://nodejs.org/dist/v0.6.3/node-v0.6.3.msi">http://nodejs.org/dist/v0.6.3/node-v0.6.3.msi</a>\r
-\r
-Macintosh Installer: <a href="http://nodejs.org/dist/v0.6.3/node-v0.6.3.pkg">http://nodejs.org/dist/v0.6.3/node-v0.6.3.pkg</a>\r
-\r
-Website: <a href="http://nodejs.org/docs/v0.6.3/">http://nodejs.org/docs/v0.6.3/</a>\r
-\r
+2011.11.25, Version 0.6.3 (stable)
+<ul>
+ <li>#2083 Land NPM in Node. It is included in packages/installers and installed on `make install`.</li>
+ <li>#2076 Add logos to windows installer.</li>
+ <li>#1711 Correctly handle http requests without headers. (Ben Noordhuis, Felix Geisendörfer)</li>
+ <li>TLS: expose more openssl SSL context options and constants. (Ben Noordhuis)</li>
+ <li>#2177 Windows: don't kill UDP socket when a packet fails to reach its destination. (Bert Belder)</li>
+ <li>Windows: support paths longer than 260 characters. (Igor Zinkovsky)</li>
+ <li>Windows: correctly resolve drive-relative paths. (Bert Belder)</li>
+ <li>#2166 Don't leave file descriptor open after lchmod. (Isaac Schlueter)</li>
+ <li>#2084 Add OS X .pkg build script to make file.</li>
+ <li>#2160 Documentation improvements. (Ben Noordhuis)</li>
+</ul>
+Source Code: <a href="http://nodejs.org/dist/v0.6.3/node-v0.6.3.tar.gz">http://nodejs.org/dist/v0.6.3/node-v0.6.3.tar.gz</a>
+
+Windows Installer: <a href="http://nodejs.org/dist/v0.6.3/node-v0.6.3.msi">http://nodejs.org/dist/v0.6.3/node-v0.6.3.msi</a>
+
+Macintosh Installer: <a href="http://nodejs.org/dist/v0.6.3/node-v0.6.3.pkg">http://nodejs.org/dist/v0.6.3/node-v0.6.3.pkg</a>
+
+Website: <a href="http://nodejs.org/docs/v0.6.3/">http://nodejs.org/docs/v0.6.3/</a>
+
Documentation: <a href="http://nodejs.org/docs/v0.6.3/api/">http://nodejs.org/docs/v0.6.3/api/</a>
category: release
slug: node-v0-6-4
-2011.12.02, Version 0.6.4 (stable)\r
-<ul>\r
-<li>doc improvements (Kyle Young, Tim Oxley, Roman Shtylman, Mathias Bynens)</li>\r
-<li>upgrade bundled npm (Isaac Schlueter)</li>\r
-<li>polish Windows installer (Igor Zinkovsky, Isaac Schlueter)</li>\r
-<li>punycode: upgrade to v0.2.1 (Mathias Bynens)</li>\r
-<li>build: add --without-npm flag to configure script</li>\r
-<li>sys: deprecate module some more, print stack trace if NODE_DEBUG=sys</li>\r
-<li>cli: add -p switch, prints result of --eval</li>\r
-<li>#1997: fix Blowfish ECB encryption and decryption (Ingmar Runge)</li>\r
-<li>#2223: fix socket 'close' event being emitted twice</li>\r
-<li>#2224: fix RSS memory usage > 4 GB reporting (Russ Bradberry)</li>\r
-<li>#2225: fix util.inspect() object stringification bug (Nathan Rajlich)</li>\r
-</ul>\r
-Source Code: <a href="http://nodejs.org/dist/v0.6.4/node-v0.6.4.tar.gz">http://nodejs.org/dist/v0.6.4/node-v0.6.4.tar.gz</a>\r
-\r
-Windows Installer: <a href="http://nodejs.org/dist/v0.6.4/node-v0.6.4.msi">http://nodejs.org/dist/v0.6.4/node-v0.6.4.msi</a>\r
-\r
-Macintosh Installer: <a href="http://nodejs.org/dist/v0.6.4/node-v0.6.4.pkg">http://nodejs.org/dist/v0.6.4/node-v0.6.4.pkg</a>\r
-\r
-Website: <a href="http://nodejs.org/docs/v0.6.4/">http://nodejs.org/docs/v0.6.4/</a>\r
-\r
+2011.12.02, Version 0.6.4 (stable)
+<ul>
+<li>doc improvements (Kyle Young, Tim Oxley, Roman Shtylman, Mathias Bynens)</li>
+<li>upgrade bundled npm (Isaac Schlueter)</li>
+<li>polish Windows installer (Igor Zinkovsky, Isaac Schlueter)</li>
+<li>punycode: upgrade to v0.2.1 (Mathias Bynens)</li>
+<li>build: add --without-npm flag to configure script</li>
+<li>sys: deprecate module some more, print stack trace if NODE_DEBUG=sys</li>
+<li>cli: add -p switch, prints result of --eval</li>
+<li>#1997: fix Blowfish ECB encryption and decryption (Ingmar Runge)</li>
+<li>#2223: fix socket 'close' event being emitted twice</li>
+<li>#2224: fix RSS memory usage > 4 GB reporting (Russ Bradberry)</li>
+<li>#2225: fix util.inspect() object stringification bug (Nathan Rajlich)</li>
+</ul>
+Source Code: <a href="http://nodejs.org/dist/v0.6.4/node-v0.6.4.tar.gz">http://nodejs.org/dist/v0.6.4/node-v0.6.4.tar.gz</a>
+
+Windows Installer: <a href="http://nodejs.org/dist/v0.6.4/node-v0.6.4.msi">http://nodejs.org/dist/v0.6.4/node-v0.6.4.msi</a>
+
+Macintosh Installer: <a href="http://nodejs.org/dist/v0.6.4/node-v0.6.4.pkg">http://nodejs.org/dist/v0.6.4/node-v0.6.4.pkg</a>
+
+Website: <a href="http://nodejs.org/docs/v0.6.4/">http://nodejs.org/docs/v0.6.4/</a>
+
Documentation: <a href="http://nodejs.org/docs/v0.6.4/api/">http://nodejs.org/docs/v0.6.4/api/</a>
category: release
slug: node-v0-6-5
-2011.12.04, Version 0.6.5 (stable)\r
-<ul><li>npm workaround Windows antivirus software (isaacs)\r
-<li>Upgrade V8 to 3.6.6.11</ul>\r
-\r
-Source Code: <a href="http://nodejs.org/dist/v0.6.5/node-v0.6.5.tar.gz">http://nodejs.org/dist/v0.6.5/node-v0.6.5.tar.gz</a>\r
-\r
-Windows Installer: <a href="http://nodejs.org/dist/v0.6.5/node-v0.6.5.msi">http://nodejs.org/dist/v0.6.5/node-v0.6.5.msi</a>\r
-\r
-Macintosh Installer: <a href="http://nodejs.org/dist/v0.6.5/node-v0.6.5.pkg">http://nodejs.org/dist/v0.6.5/node-v0.6.5.pkg</a>\r
-\r
-Website: <a href="http://nodejs.org/docs/v0.6.5/">http://nodejs.org/docs/v0.6.5/</a>\r
-\r
+2011.12.04, Version 0.6.5 (stable)
+<ul><li>npm workaround Windows antivirus software (isaacs)
+<li>Upgrade V8 to 3.6.6.11</ul>
+
+Source Code: <a href="http://nodejs.org/dist/v0.6.5/node-v0.6.5.tar.gz">http://nodejs.org/dist/v0.6.5/node-v0.6.5.tar.gz</a>
+
+Windows Installer: <a href="http://nodejs.org/dist/v0.6.5/node-v0.6.5.msi">http://nodejs.org/dist/v0.6.5/node-v0.6.5.msi</a>
+
+Macintosh Installer: <a href="http://nodejs.org/dist/v0.6.5/node-v0.6.5.pkg">http://nodejs.org/dist/v0.6.5/node-v0.6.5.pkg</a>
+
+Website: <a href="http://nodejs.org/docs/v0.6.5/">http://nodejs.org/docs/v0.6.5/</a>
+
Documentation: <a href="http://nodejs.org/docs/v0.6.5/api/">http://nodejs.org/docs/v0.6.5/api/</a>
category: release
slug: node-v0-6-6
-2011.12.14, Version 0.6.6 (stable)\r
-\r
-<ul>\r
-<li>npm update to 1.1.0-beta-4 (Isaac Z. Schlueter)</li>\r
-<li>cli: fix output of --help (Ben Noordhuis)</li>\r
-<li>new website</li>\r
-<li>pause/resume semantics for stdin (Isaac Z. Schlueter)</li>\r
-<li>Travis CI integration (Maciej Małecki)</li>\r
-<li>child_process: Fix bug regarding closed stdin (Ben Noordhuis)</li>\r
-<li>Enable upgrades in MSI. (Igor Zinkovsky)</li>\r
-<li>net: Fixes memory leak (Ben Noordhuis)</li>\r
-<li>fs: handle fractional or NaN ReadStream buffer size (Ben Noordhuis)</li>\r
-<li>crypto: fix memory leaks in PBKDF2 error path (Ben Noordhuis)</li>\r
-</ul>\r
-\r
-Source Code: <a href="http://nodejs.org/dist/v0.6.6/node-v0.6.6.tar.gz">http://nodejs.org/dist/v0.6.6/node-v0.6.6.tar.gz</a>\r
-\r
-Windows Installer: <a href="http://nodejs.org/dist/v0.6.6/node-v0.6.6.msi">http://nodejs.org/dist/v0.6.6/node-v0.6.6.msi</a>\r
-\r
-Macintosh Installer: <a href="http://nodejs.org/dist/v0.6.6/node-v0.6.6.pkg">http://nodejs.org/dist/v0.6.6/node-v0.6.6.pkg</a>\r
-\r
-Website: <a href="http://nodejs.org/docs/v0.6.6/">http://nodejs.org/docs/v0.6.6/</a>\r
-\r
+2011.12.14, Version 0.6.6 (stable)
+
+<ul>
+<li>npm update to 1.1.0-beta-4 (Isaac Z. Schlueter)</li>
+<li>cli: fix output of --help (Ben Noordhuis)</li>
+<li>new website</li>
+<li>pause/resume semantics for stdin (Isaac Z. Schlueter)</li>
+<li>Travis CI integration (Maciej Małecki)</li>
+<li>child_process: Fix bug regarding closed stdin (Ben Noordhuis)</li>
+<li>Enable upgrades in MSI. (Igor Zinkovsky)</li>
+<li>net: Fixes memory leak (Ben Noordhuis)</li>
+<li>fs: handle fractional or NaN ReadStream buffer size (Ben Noordhuis)</li>
+<li>crypto: fix memory leaks in PBKDF2 error path (Ben Noordhuis)</li>
+</ul>
+
+Source Code: <a href="http://nodejs.org/dist/v0.6.6/node-v0.6.6.tar.gz">http://nodejs.org/dist/v0.6.6/node-v0.6.6.tar.gz</a>
+
+Windows Installer: <a href="http://nodejs.org/dist/v0.6.6/node-v0.6.6.msi">http://nodejs.org/dist/v0.6.6/node-v0.6.6.msi</a>
+
+Macintosh Installer: <a href="http://nodejs.org/dist/v0.6.6/node-v0.6.6.pkg">http://nodejs.org/dist/v0.6.6/node-v0.6.6.pkg</a>
+
+Website: <a href="http://nodejs.org/docs/v0.6.6/">http://nodejs.org/docs/v0.6.6/</a>
+
Documentation: <a href="http://nodejs.org/docs/v0.6.6/api/">http://nodejs.org/docs/v0.6.6/api/</a>
category: release
slug: node-v0-6-7
-<p>2012.01.06, Version 0.6.7 (stable)</p>\r
-\r
-<ul>\r
-<li><p>V8 hash collision fix (Breaks MIPS) (Bert Belder, Erik Corry)</p></li>\r
-<li><p>Upgrade V8 to 3.6.6.15</p></li>\r
-<li><p>Upgrade npm to 1.1.0-beta-10 (isaacs)</p></li>\r
-<li><p>many doc updates (Ben Noordhuis, Jeremy Martin, koichik, Dave Irvine,\r
-Seong-Rak Choi, Shannen, Adam Malcontenti-Wilson, koichik)</p></li>\r
-<li><p>Fix segfault in <code>node_http_parser.cc</code></p></li>\r
-<li><p>dgram, timers: fix memory leaks (Ben Noordhuis, Yoshihiro Kikuchi)</p></li>\r
-<li><p>repl: fix repl.start not passing the <code>ignoreUndefined</code> arg (Damon Oehlman)</p></li>\r
-<li><p>#1980: Socket.pause null reference when called on a closed Stream (koichik)</p></li>\r
-<li><p>#2263: XMLHttpRequest piped in a writable file stream hang (koichik)</p></li>\r
-<li><p>#2069: http resource leak (koichik)</p></li>\r
-<li><p>buffer.readInt global pollution fix (Phil Sung)</p></li>\r
-<li><p>timers: fix performance regression (Ben Noordhuis)</p></li>\r
-<li><p>#2308, #2246: node swallows openssl error on request (koichik)</p></li>\r
-<li><p>#2114: timers: remove _idleTimeout from item in .unenroll() (James Hartig)</p></li>\r
-<li><p>#2379: debugger: Request backtrace w/o refs (Fedor Indutny)</p></li>\r
-<li><p>simple DTrace ustack helper (Dave Pacheco)</p></li>\r
-<li><p>crypto: rewrite HexDecode without snprintf (Roman Shtylman)</p></li>\r
-<li><p>crypto: don’t ignore DH init errors (Ben Noordhuis)</p></li>\r
-</ul>\r
-\r
-<p>Source Code: <a href="http://nodejs.org/dist/v0.6.7/node-v0.6.7.tar.gz">http://nodejs.org/dist/v0.6.7/node-v0.6.7.tar.gz</a></p>\r
-\r
-<p>Windows Installer: <a href="http://nodejs.org/dist/v0.6.7/node-v0.6.7.msi">http://nodejs.org/dist/v0.6.7/node-v0.6.7.msi</a></p>\r
-\r
-<p>Macintosh Installer: <a href="http://nodejs.org/dist/v0.6.7/node-v0.6.7.pkg">http://nodejs.org/dist/v0.6.7/node-v0.6.7.pkg</a></p>\r
-\r
-<p>Website: <a href="http://nodejs.org/docs/v0.6.7/">http://nodejs.org/docs/v0.6.7/</a></p>\r
-\r
+<p>2012.01.06, Version 0.6.7 (stable)</p>
+
+<ul>
+<li><p>V8 hash collision fix (Breaks MIPS) (Bert Belder, Erik Corry)</p></li>
+<li><p>Upgrade V8 to 3.6.6.15</p></li>
+<li><p>Upgrade npm to 1.1.0-beta-10 (isaacs)</p></li>
+<li><p>many doc updates (Ben Noordhuis, Jeremy Martin, koichik, Dave Irvine,
+Seong-Rak Choi, Shannen, Adam Malcontenti-Wilson, koichik)</p></li>
+<li><p>Fix segfault in <code>node_http_parser.cc</code></p></li>
+<li><p>dgram, timers: fix memory leaks (Ben Noordhuis, Yoshihiro Kikuchi)</p></li>
+<li><p>repl: fix repl.start not passing the <code>ignoreUndefined</code> arg (Damon Oehlman)</p></li>
+<li><p>#1980: Socket.pause null reference when called on a closed Stream (koichik)</p></li>
+<li><p>#2263: XMLHttpRequest piped in a writable file stream hang (koichik)</p></li>
+<li><p>#2069: http resource leak (koichik)</p></li>
+<li><p>buffer.readInt global pollution fix (Phil Sung)</p></li>
+<li><p>timers: fix performance regression (Ben Noordhuis)</p></li>
+<li><p>#2308, #2246: node swallows openssl error on request (koichik)</p></li>
+<li><p>#2114: timers: remove _idleTimeout from item in .unenroll() (James Hartig)</p></li>
+<li><p>#2379: debugger: Request backtrace w/o refs (Fedor Indutny)</p></li>
+<li><p>simple DTrace ustack helper (Dave Pacheco)</p></li>
+<li><p>crypto: rewrite HexDecode without snprintf (Roman Shtylman)</p></li>
+<li><p>crypto: don’t ignore DH init errors (Ben Noordhuis)</p></li>
+</ul>
+
+<p>Source Code: <a href="http://nodejs.org/dist/v0.6.7/node-v0.6.7.tar.gz">http://nodejs.org/dist/v0.6.7/node-v0.6.7.tar.gz</a></p>
+
+<p>Windows Installer: <a href="http://nodejs.org/dist/v0.6.7/node-v0.6.7.msi">http://nodejs.org/dist/v0.6.7/node-v0.6.7.msi</a></p>
+
+<p>Macintosh Installer: <a href="http://nodejs.org/dist/v0.6.7/node-v0.6.7.pkg">http://nodejs.org/dist/v0.6.7/node-v0.6.7.pkg</a></p>
+
+<p>Website: <a href="http://nodejs.org/docs/v0.6.7/">http://nodejs.org/docs/v0.6.7/</a></p>
+
<p>Documentation: <a href="http://nodejs.org/docs/v0.6.7/api/">http://nodejs.org/docs/v0.6.7/api/</a></p>
category: release
slug: node-v0-6-8
-<p>2012.01.19, Version 0.6.8 (stable)</p>\r
-\r
-<ul>\r
-<li><p>Update V8 to 3.6.6.19</p></li>\r
-<li><p>Numeric key hash collision fix for V8 (Erik Corry, Fedor Indutny)</p></li>\r
-<li><p>Add missing TTY key translations for F1-F5 on Windows (Brandon Benvie)</p></li>\r
-<li><p>path.extname bugfix with . and .. paths (Bert Belder)</p></li>\r
-<li><p>cluster: don't always kill the master on uncaughtException (Ben Noordhuis)</p></li>\r
-<li><p>Update npm to 1.1.0-2 (isaacs)</p></li>\r
-<li><p>typed arrays: set class name (Ben Noordhuis)</p></li>\r
-<li><p>zlib binding cleanup (isaacs, Bert Belder)</p></li>\r
-<li><p>dgram: use slab memory allocator (Michael Bernstein)</p></li>\r
-<li><p>fix segfault #2473</p></li>\r
-<li><p>#2521 60% improvement in fs.stat on Windows (Igor Zinkovsky)</p></li>\r
-</ul><p>Source Code: <a href="http://nodejs.org/dist/v0.6.8/node-v0.6.8.tar.gz">http://nodejs.org/dist/v0.6.8/node-v0.6.8.tar.gz</a></p>\r
-\r
-<p>Windows Installer: <a href="http://nodejs.org/dist/v0.6.8/node-v0.6.8.msi">http://nodejs.org/dist/v0.6.8/node-v0.6.8.msi</a></p>\r
-\r
-<p>Macintosh Installer: <a href="http://nodejs.org/dist/v0.6.8/node-v0.6.8.pkg">http://nodejs.org/dist/v0.6.8/node-v0.6.8.pkg</a></p>\r
-\r
-<p>Website: <a href="http://nodejs.org/docs/v0.6.8/">http://nodejs.org/docs/v0.6.8/</a></p>\r
-\r
+<p>2012.01.19, Version 0.6.8 (stable)</p>
+
+<ul>
+<li><p>Update V8 to 3.6.6.19</p></li>
+<li><p>Numeric key hash collision fix for V8 (Erik Corry, Fedor Indutny)</p></li>
+<li><p>Add missing TTY key translations for F1-F5 on Windows (Brandon Benvie)</p></li>
+<li><p>path.extname bugfix with . and .. paths (Bert Belder)</p></li>
+<li><p>cluster: don't always kill the master on uncaughtException (Ben Noordhuis)</p></li>
+<li><p>Update npm to 1.1.0-2 (isaacs)</p></li>
+<li><p>typed arrays: set class name (Ben Noordhuis)</p></li>
+<li><p>zlib binding cleanup (isaacs, Bert Belder)</p></li>
+<li><p>dgram: use slab memory allocator (Michael Bernstein)</p></li>
+<li><p>fix segfault #2473</p></li>
+<li><p>#2521 60% improvement in fs.stat on Windows (Igor Zinkovsky)</p></li>
+</ul><p>Source Code: <a href="http://nodejs.org/dist/v0.6.8/node-v0.6.8.tar.gz">http://nodejs.org/dist/v0.6.8/node-v0.6.8.tar.gz</a></p>
+
+<p>Windows Installer: <a href="http://nodejs.org/dist/v0.6.8/node-v0.6.8.msi">http://nodejs.org/dist/v0.6.8/node-v0.6.8.msi</a></p>
+
+<p>Macintosh Installer: <a href="http://nodejs.org/dist/v0.6.8/node-v0.6.8.pkg">http://nodejs.org/dist/v0.6.8/node-v0.6.8.pkg</a></p>
+
+<p>Website: <a href="http://nodejs.org/docs/v0.6.8/">http://nodejs.org/docs/v0.6.8/</a></p>
+
<p>Documentation: <a href="http://nodejs.org/docs/v0.6.8/api/">http://nodejs.org/docs/v0.6.8/api/</a></p>
category: release
slug: node-v0-6-9
-<p>2012.01.27, Version 0.6.9 (stable)</p>\r
-\r
-<ul>\r
-<li>\r
-<p>dgram: Bring back missing functionality for Unix (Dan VerWeire,\r
-Roman Shtylman, Ben Noordhuis)</p>\r
-<p>- Note: Windows UDP support not yet complete.</p></li>\r
-<li><p>http: Fix parser memory leak (koichik)</p></li>\r
-<li><p>zlib: Fix #2365 crashes on invalid input (Nicolas LaCasse)</p></li>\r
-<li><p>module: fix --debug-brk on symlinked scripts (Fedor Indutny)</p></li>\r
-<li><p>Documentation Restyling (Matthew Fitzsimmons)</p></li>\r
-<li><p>Update npm to 1.1.0-3 (isaacs)</p></li>\r
-<li><p>Windows: fix regression in stat() calls to C:\ (Bert Belder)</p></li>\r
-</ul><p>Source Code: <a href="http://nodejs.org/dist/v0.6.9/node-v0.6.9.tar.gz">http://nodejs.org/dist/v0.6.9/node-v0.6.9.tar.gz</a></p>\r
-\r
-<p>Windows Installer: <a href="http://nodejs.org/dist/v0.6.9/node-v0.6.9.msi">http://nodejs.org/dist/v0.6.9/node-v0.6.9.msi</a></p>\r
-\r
-<p>Macintosh Installer: <a href="http://nodejs.org/dist/v0.6.9/node-v0.6.9.pkg">http://nodejs.org/dist/v0.6.9/node-v0.6.9.pkg</a></p>\r
-\r
-<p>Website: <a href="http://nodejs.org/docs/v0.6.9/">http://nodejs.org/docs/v0.6.9/</a></p>\r
-\r
+<p>2012.01.27, Version 0.6.9 (stable)</p>
+
+<ul>
+<li>
+<p>dgram: Bring back missing functionality for Unix (Dan VerWeire,
+Roman Shtylman, Ben Noordhuis)</p>
+<p>- Note: Windows UDP support not yet complete.</p></li>
+<li><p>http: Fix parser memory leak (koichik)</p></li>
+<li><p>zlib: Fix #2365 crashes on invalid input (Nicolas LaCasse)</p></li>
+<li><p>module: fix --debug-brk on symlinked scripts (Fedor Indutny)</p></li>
+<li><p>Documentation Restyling (Matthew Fitzsimmons)</p></li>
+<li><p>Update npm to 1.1.0-3 (isaacs)</p></li>
+<li><p>Windows: fix regression in stat() calls to C:\ (Bert Belder)</p></li>
+</ul><p>Source Code: <a href="http://nodejs.org/dist/v0.6.9/node-v0.6.9.tar.gz">http://nodejs.org/dist/v0.6.9/node-v0.6.9.tar.gz</a></p>
+
+<p>Windows Installer: <a href="http://nodejs.org/dist/v0.6.9/node-v0.6.9.msi">http://nodejs.org/dist/v0.6.9/node-v0.6.9.msi</a></p>
+
+<p>Macintosh Installer: <a href="http://nodejs.org/dist/v0.6.9/node-v0.6.9.pkg">http://nodejs.org/dist/v0.6.9/node-v0.6.9.pkg</a></p>
+
+<p>Website: <a href="http://nodejs.org/docs/v0.6.9/">http://nodejs.org/docs/v0.6.9/</a></p>
+
<p>Documentation: <a href="http://nodejs.org/docs/v0.6.9/api/">http://nodejs.org/docs/v0.6.9/api/</a></p>
category: release
slug: node-v0-7-0-unstable
-<strong>This is the first release in the unstable v0.7 series. Almost all users will want to remain using the stable v0.6 releases.</strong>\r
-\r
-2012.01.16, Version 0.7.0 (unstable)\r
-<ul>\r
-<li>Upgrade V8 to 3.8.6\r
-<li>Use GYP build system on unix (Ben Noordhuis)\r
-<li>Experimenetal isolates support (Ben Noordhuis)\r
-<li>Improvements to Cluster API (Andreas Madsen)\r
-<li>Use isolates for internal debugger (Fedor Indutny)\r
-<li>Bug fixes</ul>\r
-\r
-\r
-Source Code: <a href="http://nodejs.org/dist/v0.7.0/node-v0.7.0.tar.gz">http://nodejs.org/dist/v0.7.0/node-v0.7.0.tar.gz</a>\r
-\r
-Windows Installer: <a href="http://nodejs.org/dist/v0.7.0/node-v0.7.0.msi">http://nodejs.org/dist/v0.7.0/node-v0.7.0.msi</a>\r
-\r
-Macintosh Installer: <a href="http://nodejs.org/dist/v0.7.0/node-v0.7.0.pkg">http://nodejs.org/dist/v0.7.0/node-v0.7.0.pkg</a>\r
-\r
-Website: <a href="http://nodejs.org/docs/v0.7.0/">http://nodejs.org/docs/v0.7.0/</a>\r
-\r
+<strong>This is the first release in the unstable v0.7 series. Almost all users will want to remain using the stable v0.6 releases.</strong>
+
+2012.01.16, Version 0.7.0 (unstable)
+<ul>
+<li>Upgrade V8 to 3.8.6
+<li>Use GYP build system on unix (Ben Noordhuis)
+<li>Experimenetal isolates support (Ben Noordhuis)
+<li>Improvements to Cluster API (Andreas Madsen)
+<li>Use isolates for internal debugger (Fedor Indutny)
+<li>Bug fixes</ul>
+
+
+Source Code: <a href="http://nodejs.org/dist/v0.7.0/node-v0.7.0.tar.gz">http://nodejs.org/dist/v0.7.0/node-v0.7.0.tar.gz</a>
+
+Windows Installer: <a href="http://nodejs.org/dist/v0.7.0/node-v0.7.0.msi">http://nodejs.org/dist/v0.7.0/node-v0.7.0.msi</a>
+
+Macintosh Installer: <a href="http://nodejs.org/dist/v0.7.0/node-v0.7.0.pkg">http://nodejs.org/dist/v0.7.0/node-v0.7.0.pkg</a>
+
+Website: <a href="http://nodejs.org/docs/v0.7.0/">http://nodejs.org/docs/v0.7.0/</a>
+
Documentation: <a href="http://nodejs.org/docs/v0.7.0/api/">http://nodejs.org/docs/v0.7.0/api/</a>
category: release
slug: node-v0-7-1
-<p>2012.01.23, Version 0.7.1 (unstable)</p>\r
-\r
-<ul>\r
-<li><p>Update V8 to 3.8.8</p></li>\r
-<li><p>Install node-waf by default (Fedor Indutny)</p></li>\r
-<li><p>crypto: Add ability to turn off PKCS padding (Ingmar Runge)</p></li>\r
-<li><p>v8: implement VirtualMemory class on SunOS (Ben Noordhuis)</p></li>\r
-<li><p>Add cluster.setupMaster (Andreas Madsen)</p></li>\r
-<li><p>move <code>path.exists*</code> to <code>fs.exists*</code> (Maciej Małecki)</p></li>\r
-<li><p>typed arrays: set class name (Ben Noordhuis)</p></li>\r
-<li><p>libuv bug fixes (Igor Zinkovsky, Ben Noordhuis, Dan VerWeire)</p></li>\r
-</ul>\r
-\r
-<p>Source: <a href="http://nodejs.org/dist/v0.7.1/node-v0.7.1.tar.gz">http://nodejs.org/dist/v0.7.1/node-v0.7.1.tar.gz</a></p>\r
-\r
-<p>Windows Installer: <a href="http://nodejs.org/dist/v0.7.1/node-v0.7.1.msi">http://nodejs.org/dist/v0.7.1/node-v0.7.1.msi</a></p>\r
-\r
-<p>Macintosh Installer: <a href="http://nodejs.org/dist/v0.7.1/node-v0.7.1.pkg">http://nodejs.org/dist/v0.7.1/node-v0.7.1.pkg</a></p>\r
-\r
-<p>Website: <a href="http://nodejs.org/docs/v0.7.1/">http://nodejs.org/docs/v0.7.1/</a></p>\r
-\r
+<p>2012.01.23, Version 0.7.1 (unstable)</p>
+
+<ul>
+<li><p>Update V8 to 3.8.8</p></li>
+<li><p>Install node-waf by default (Fedor Indutny)</p></li>
+<li><p>crypto: Add ability to turn off PKCS padding (Ingmar Runge)</p></li>
+<li><p>v8: implement VirtualMemory class on SunOS (Ben Noordhuis)</p></li>
+<li><p>Add cluster.setupMaster (Andreas Madsen)</p></li>
+<li><p>move <code>path.exists*</code> to <code>fs.exists*</code> (Maciej Małecki)</p></li>
+<li><p>typed arrays: set class name (Ben Noordhuis)</p></li>
+<li><p>libuv bug fixes (Igor Zinkovsky, Ben Noordhuis, Dan VerWeire)</p></li>
+</ul>
+
+<p>Source: <a href="http://nodejs.org/dist/v0.7.1/node-v0.7.1.tar.gz">http://nodejs.org/dist/v0.7.1/node-v0.7.1.tar.gz</a></p>
+
+<p>Windows Installer: <a href="http://nodejs.org/dist/v0.7.1/node-v0.7.1.msi">http://nodejs.org/dist/v0.7.1/node-v0.7.1.msi</a></p>
+
+<p>Macintosh Installer: <a href="http://nodejs.org/dist/v0.7.1/node-v0.7.1.pkg">http://nodejs.org/dist/v0.7.1/node-v0.7.1.pkg</a></p>
+
+<p>Website: <a href="http://nodejs.org/docs/v0.7.1/">http://nodejs.org/docs/v0.7.1/</a></p>
+
<p>Documentation: <a href="http://nodejs.org/docs/v0.7.1/api/">http://nodejs.org/docs/v0.7.1/api/</a></p>
category: release
slug: node-v0-7-2-unstable
-<p>2012.02.01, Version 0.7.2 (unstable)</p>\r
-\r
-<ul>\r
-<li><p>Update V8 to 3.8.9</p></li>\r
-<li><p>Support for sharing streams across Isolates (Igor Zinkovsky)</p></li>\r
-<li><p>#2636 - Fix case where http_parsers are freed too early (koichik)</p></li>\r
-<li><p>url: Support for IPv6 addresses in URLs (Łukasz Walukiewicz)</p></li>\r
-<li><p>child_process: Add disconnect() method to child processes (Andreas Madsen)</p></li>\r
-<li><p>fs: add O_EXCL support, exclusive open file (Ben Noordhuis)</p></li>\r
-<li><p>fs: more specific error messages (Tj Holowaychuk)</p></li>\r
-<li><p>tty: emit 'unknown' key event if key sequence not found (Dan VerWeire, Nathan Rajlich)</p></li>\r
-<li><p>build: compile release build too if BUILDTYPE=Debug (Ben Noordhuis)</p></li>\r
-<li><p>module: fix --debug-brk on symlinked scripts (Fedor Indutny)</p></li>\r
-<li><p>zlib: fix <code>Failed to set dictionary</code> issue (Fedor Indutny)</p></li>\r
-<li><p>waf: predict target arch for OS X (Fedor Indutny)</p></li>\r
-</ul><p>Source Code: <a href="http://nodejs.org/dist/v0.7.2/node-v0.7.2.tar.gz">http://nodejs.org/dist/v0.7.2/node-v0.7.2.tar.gz</a></p>\r
-\r
-<p>Windows Installer: <a href="http://nodejs.org/dist/v0.7.2/node-v0.7.2.msi">http://nodejs.org/dist/v0.7.2/node-v0.7.2.msi</a></p>\r
-\r
-<p>Macintosh Installer: <a href="http://nodejs.org/dist/v0.7.2/node-v0.7.2.pkg">http://nodejs.org/dist/v0.7.2/node-v0.7.2.pkg</a></p>\r
-\r
-<p>Website: <a href="http://nodejs.org/docs/v0.7.2/">http://nodejs.org/docs/v0.7.2/</a></p>\r
-\r
+<p>2012.02.01, Version 0.7.2 (unstable)</p>
+
+<ul>
+<li><p>Update V8 to 3.8.9</p></li>
+<li><p>Support for sharing streams across Isolates (Igor Zinkovsky)</p></li>
+<li><p>#2636 - Fix case where http_parsers are freed too early (koichik)</p></li>
+<li><p>url: Support for IPv6 addresses in URLs (Łukasz Walukiewicz)</p></li>
+<li><p>child_process: Add disconnect() method to child processes (Andreas Madsen)</p></li>
+<li><p>fs: add O_EXCL support, exclusive open file (Ben Noordhuis)</p></li>
+<li><p>fs: more specific error messages (Tj Holowaychuk)</p></li>
+<li><p>tty: emit 'unknown' key event if key sequence not found (Dan VerWeire, Nathan Rajlich)</p></li>
+<li><p>build: compile release build too if BUILDTYPE=Debug (Ben Noordhuis)</p></li>
+<li><p>module: fix --debug-brk on symlinked scripts (Fedor Indutny)</p></li>
+<li><p>zlib: fix <code>Failed to set dictionary</code> issue (Fedor Indutny)</p></li>
+<li><p>waf: predict target arch for OS X (Fedor Indutny)</p></li>
+</ul><p>Source Code: <a href="http://nodejs.org/dist/v0.7.2/node-v0.7.2.tar.gz">http://nodejs.org/dist/v0.7.2/node-v0.7.2.tar.gz</a></p>
+
+<p>Windows Installer: <a href="http://nodejs.org/dist/v0.7.2/node-v0.7.2.msi">http://nodejs.org/dist/v0.7.2/node-v0.7.2.msi</a></p>
+
+<p>Macintosh Installer: <a href="http://nodejs.org/dist/v0.7.2/node-v0.7.2.pkg">http://nodejs.org/dist/v0.7.2/node-v0.7.2.pkg</a></p>
+
+<p>Website: <a href="http://nodejs.org/docs/v0.7.2/">http://nodejs.org/docs/v0.7.2/</a></p>
+
<p>Documentation: <a href="http://nodejs.org/docs/v0.7.2/api/">http://nodejs.org/docs/v0.7.2/api/</a></p>
category: release
slug: node-v0-7-3
-<p>2012.02.07, Version 0.7.3 (unstable)\r
-\r
-</p>\r
-<ul>\r
-<li><p>Upgrade V8 to 3.9.2</p>\r
-</li>\r
-<li><p>Revert support for isolates. (Ben Noordhuis)</p>\r
-</li>\r
-<li><p>cluster: Cleanup docs, event handling, and process.disconnect (Andreas Madsen)</p>\r
-</li>\r
-<li><p>gyp_addon: link with node.lib on Windows (Nathan Rajlich)</p>\r
-</li>\r
-<li><p>http: fix case where http-parser is freed twice (koichik)</p>\r
-</li>\r
-<li><p>Windows: disable RTTI and exceptions (Bert Belder)</p>\r
-</li>\r
-</ul>\r
-<p>Source Code: <a href="http://nodejs.org/dist/v0.7.3/node-v0.7.3.tar.gz">http://nodejs.org/dist/v0.7.3/node-v0.7.3.tar.gz</a>\r
-\r
-</p>\r
-<p>Windows Installer: <a href="http://nodejs.org/dist/v0.7.3/node-v0.7.3.msi">http://nodejs.org/dist/v0.7.3/node-v0.7.3.msi</a>\r
-\r
-</p>\r
-<p>Macintosh Installer: <a href="http://nodejs.org/dist/v0.7.3/node-v0.7.3.pkg">http://nodejs.org/dist/v0.7.3/node-v0.7.3.pkg</a>\r
-\r
-</p>\r
-<p>Website: <a href="http://nodejs.org/docs/v0.7.3/">http://nodejs.org/docs/v0.7.3/</a>\r
-\r
-</p>\r
-<p>Documentation: <a href="http://nodejs.org/docs/v0.7.3/api/">http://nodejs.org/docs/v0.7.3/api/</a>\r
+<p>2012.02.07, Version 0.7.3 (unstable)
+
+</p>
+<ul>
+<li><p>Upgrade V8 to 3.9.2</p>
+</li>
+<li><p>Revert support for isolates. (Ben Noordhuis)</p>
+</li>
+<li><p>cluster: Cleanup docs, event handling, and process.disconnect (Andreas Madsen)</p>
+</li>
+<li><p>gyp_addon: link with node.lib on Windows (Nathan Rajlich)</p>
+</li>
+<li><p>http: fix case where http-parser is freed twice (koichik)</p>
+</li>
+<li><p>Windows: disable RTTI and exceptions (Bert Belder)</p>
+</li>
+</ul>
+<p>Source Code: <a href="http://nodejs.org/dist/v0.7.3/node-v0.7.3.tar.gz">http://nodejs.org/dist/v0.7.3/node-v0.7.3.tar.gz</a>
+
+</p>
+<p>Windows Installer: <a href="http://nodejs.org/dist/v0.7.3/node-v0.7.3.msi">http://nodejs.org/dist/v0.7.3/node-v0.7.3.msi</a>
+
+</p>
+<p>Macintosh Installer: <a href="http://nodejs.org/dist/v0.7.3/node-v0.7.3.pkg">http://nodejs.org/dist/v0.7.3/node-v0.7.3.pkg</a>
+
+</p>
+<p>Website: <a href="http://nodejs.org/docs/v0.7.3/">http://nodejs.org/docs/v0.7.3/</a>
+
+</p>
+<p>Documentation: <a href="http://nodejs.org/docs/v0.7.3/api/">http://nodejs.org/docs/v0.7.3/api/</a>
</p>
category: release
slug: node-version-0-6-19-stable
-<p>2012.06.06 Version 0.6.19 (stable)\r
-\r
-</p>\r
-<ul>\r
-<li><p>npm: upgrade to 1.1.24</p>\r
-</li>\r
-<li><p>fs: no end emit after createReadStream.pause() (Andreas Madsen)</p>\r
-</li>\r
-<li><p>vm: cleanup module memory leakage (Marcel Laverdet)</p>\r
-</li>\r
-<li><p>unix: fix loop starvation under high network load (Ben Noordhuis)</p>\r
-</li>\r
-<li><p>unix: remove abort() in ev_unref() (Ben Noordhuis)</p>\r
-</li>\r
-<li><p>windows/tty: never report error after forcibly aborting line-buffered read (Bert Belder)</p>\r
-</li>\r
-<li><p>windows: skip GetFileAttributes call when opening a file (Bert Belder)</p>\r
-</li>\r
-</ul>\r
-<p>Source Code: <a href="http://nodejs.org/dist/v0.6.19/node-v0.6.19.tar.gz">http://nodejs.org/dist/v0.6.19/node-v0.6.19.tar.gz</a>\r
-\r
-</p>\r
-<p>Windows Installer: <a href="http://nodejs.org/dist/v0.6.19/node-v0.6.19.msi">http://nodejs.org/dist/v0.6.19/node-v0.6.19.msi</a>\r
-\r
-</p>\r
-<p>Windows x64 Files: <a href="http://nodejs.org/dist/v0.6.19/x64/">http://nodejs.org/dist/v0.6.19/x64/</a>\r
-\r
-</p>\r
-<p>Macintosh Installer (Universal): <a href="http://nodejs.org/dist/v0.6.19/node-v0.6.19.pkg">http://nodejs.org/dist/v0.6.19/node-v0.6.19.pkg</a>\r
-\r
-</p>\r
-<p>Other release files: <a href="http://nodejs.org/dist/v0.6.19/">http://nodejs.org/dist/v0.6.19/</a>\r
-\r
-</p>\r
-<p>Website: <a href="http://nodejs.org/docs/v0.6.19/">http://nodejs.org/docs/v0.6.19/</a>\r
-\r
-</p>\r
-<p>Documentation: <a href="http://nodejs.org/docs/v0.6.19/api/">http://nodejs.org/docs/v0.6.19/api/</a>\r
-</p>\r
-\r
-<p>Shasums:</p>\r
-<pre>ef4f5c1e5f12f6ef3478a794d6a81f59669332f9 node-v0.6.19.msi\r
-781616f33208f532f168633758a648c20e1ea68b node-v0.6.19.pkg\r
-f6c5cfbadff4788ac3a95f8263a0c2f4e07444b6 node-v0.6.19.tar.gz\r
-10f729ca236825821d97556441fa64f994cb4ca8 node.exe\r
-5b8cd02e5f92ed6512aabdac11766ad8c1abc436 node.exp\r
-20037e4901de605e08e48d0c85531334912844e3 node.lib\r
-c44f62852918d449850014d9b29dd073cb6920a5 node.pdb\r
-04db25c93c5357394941dd2de12cb61959eb82d1 x64/node-v0.6.19.msi\r
-f77c77f2e470cfc9071853af2f277ba91d660b9c x64/node.exe\r
-fcf26a3f984a3f19804e0567414604b77b1d3bac x64/node.exp\r
-bfed2a24f253dbac99379d6f22fc8e9e85ade7ed x64/node.lib\r
+<p>2012.06.06 Version 0.6.19 (stable)
+
+</p>
+<ul>
+<li><p>npm: upgrade to 1.1.24</p>
+</li>
+<li><p>fs: no end emit after createReadStream.pause() (Andreas Madsen)</p>
+</li>
+<li><p>vm: cleanup module memory leakage (Marcel Laverdet)</p>
+</li>
+<li><p>unix: fix loop starvation under high network load (Ben Noordhuis)</p>
+</li>
+<li><p>unix: remove abort() in ev_unref() (Ben Noordhuis)</p>
+</li>
+<li><p>windows/tty: never report error after forcibly aborting line-buffered read (Bert Belder)</p>
+</li>
+<li><p>windows: skip GetFileAttributes call when opening a file (Bert Belder)</p>
+</li>
+</ul>
+<p>Source Code: <a href="http://nodejs.org/dist/v0.6.19/node-v0.6.19.tar.gz">http://nodejs.org/dist/v0.6.19/node-v0.6.19.tar.gz</a>
+
+</p>
+<p>Windows Installer: <a href="http://nodejs.org/dist/v0.6.19/node-v0.6.19.msi">http://nodejs.org/dist/v0.6.19/node-v0.6.19.msi</a>
+
+</p>
+<p>Windows x64 Files: <a href="http://nodejs.org/dist/v0.6.19/x64/">http://nodejs.org/dist/v0.6.19/x64/</a>
+
+</p>
+<p>Macintosh Installer (Universal): <a href="http://nodejs.org/dist/v0.6.19/node-v0.6.19.pkg">http://nodejs.org/dist/v0.6.19/node-v0.6.19.pkg</a>
+
+</p>
+<p>Other release files: <a href="http://nodejs.org/dist/v0.6.19/">http://nodejs.org/dist/v0.6.19/</a>
+
+</p>
+<p>Website: <a href="http://nodejs.org/docs/v0.6.19/">http://nodejs.org/docs/v0.6.19/</a>
+
+</p>
+<p>Documentation: <a href="http://nodejs.org/docs/v0.6.19/api/">http://nodejs.org/docs/v0.6.19/api/</a>
+</p>
+
+<p>Shasums:</p>
+<pre>ef4f5c1e5f12f6ef3478a794d6a81f59669332f9 node-v0.6.19.msi
+781616f33208f532f168633758a648c20e1ea68b node-v0.6.19.pkg
+f6c5cfbadff4788ac3a95f8263a0c2f4e07444b6 node-v0.6.19.tar.gz
+10f729ca236825821d97556441fa64f994cb4ca8 node.exe
+5b8cd02e5f92ed6512aabdac11766ad8c1abc436 node.exp
+20037e4901de605e08e48d0c85531334912844e3 node.lib
+c44f62852918d449850014d9b29dd073cb6920a5 node.pdb
+04db25c93c5357394941dd2de12cb61959eb82d1 x64/node-v0.6.19.msi
+f77c77f2e470cfc9071853af2f277ba91d660b9c x64/node.exe
+fcf26a3f984a3f19804e0567414604b77b1d3bac x64/node.exp
+bfed2a24f253dbac99379d6f22fc8e9e85ade7ed x64/node.lib
95226c1cc5170ea05c2e54431040f06c3e95e99f x64/node.pdb</pre>
category: release
slug: node-version-0-7-9-unstable
-<p>2012.05.28, Version 0.7.9 (unstable)\r
-\r
-</p>\r
-<ul>\r
-<li><p>Upgrade V8 to 3.11.1</p>\r
-</li>\r
-<li><p>Upgrade npm to 1.1.23</p>\r
-</li>\r
-<li><p>uv: rework reference counting scheme (Ben Noordhuis)</p>\r
-</li>\r
-<li><p>uv: add interface for joining external event loops (Bert Belder)</p>\r
-</li>\r
-<li><p>repl, readline: Handle Ctrl+Z and SIGCONT better (Nathan Rajlich)</p>\r
-</li>\r
-<li><p>fs: 64bit offsets for fs calls (Igor Zinkovsky)</p>\r
-</li>\r
-<li><p>fs: add sync open flags 'rs' and 'rs+' (Kevin Bowman)</p>\r
-</li>\r
-<li><p>windows: enable creating directory junctions with fs.symlink (Igor Zinkovsky, Bert Belder)</p>\r
-</li>\r
-<li><p>windows: fix fs.lstat to properly detect symlinks. (Igor Zinkovsky)</p>\r
-</li>\r
-<li><p>Fix #3270 Escape url.parse delims (isaacs)</p>\r
-</li>\r
-<li><p>http: make http.get() accept a URL (Adam Malcontenti-Wilson)</p>\r
-</li>\r
-<li><p>Cleanup vm module memory leakage (Marcel Laverdet)</p>\r
-</li>\r
-<li><p>Optimize writing strings with Socket.write (Bert Belder)</p>\r
-</li>\r
-<li><p>add support for CESU-8 and UTF-16LE encodings (koichik)</p>\r
-</li>\r
-<li><p>path: add path.sep to get the path separator. (Yi, EungJun)</p>\r
-</li>\r
-<li><p>net, http: add backlog parameter to .listen() (Erik Dubbelboer)</p>\r
-</li>\r
-<li><p>debugger: support mirroring Date objects (Fedor Indutny)</p>\r
-</li>\r
-<li><p>addon: add AtExit() function (Ben Noordhuis)</p>\r
-</li>\r
-<li><p>net: signal localAddress bind failure in connect (Brian Schroeder)</p>\r
-</li>\r
-<li><p>util: handle non-string return value in .inspect() (Alex Kocharin)</p>\r
-</li>\r
-</ul>\r
-<p>Source Code: <a href="http://nodejs.org/dist/v0.7.9/node-v0.7.9.tar.gz">http://nodejs.org/dist/v0.7.9/node-v0.7.9.tar.gz</a>\r
-\r
-</p>\r
-<p>Windows Installer: <a href="http://nodejs.org/dist/v0.7.9/node-v0.7.9.msi">http://nodejs.org/dist/v0.7.9/node-v0.7.9.msi</a>\r
-\r
-</p>\r
-<p>Windows x64 Files: <a href="http://nodejs.org/dist/v0.7.9/x64/">http://nodejs.org/dist/v0.7.9/x64/</a>\r
-\r
-</p>\r
-<p>Macintosh Installer (Universal): <a href="http://nodejs.org/dist/v0.7.9/node-v0.7.9.pkg">http://nodejs.org/dist/v0.7.9/node-v0.7.9.pkg</a>\r
-\r
-</p>\r
-<p>Other release files: <a href="http://nodejs.org/dist/v0.7.9/">http://nodejs.org/dist/v0.7.9/</a>\r
-\r
-</p>\r
-<p>Website: <a href="http://nodejs.org/docs/v0.7.9/">http://nodejs.org/docs/v0.7.9/</a>\r
-\r
-</p>\r
-<p>Documentation: <a href="http://nodejs.org/docs/v0.7.9/api/">http://nodejs.org/docs/v0.7.9/api/</a>\r
+<p>2012.05.28, Version 0.7.9 (unstable)
+
+</p>
+<ul>
+<li><p>Upgrade V8 to 3.11.1</p>
+</li>
+<li><p>Upgrade npm to 1.1.23</p>
+</li>
+<li><p>uv: rework reference counting scheme (Ben Noordhuis)</p>
+</li>
+<li><p>uv: add interface for joining external event loops (Bert Belder)</p>
+</li>
+<li><p>repl, readline: Handle Ctrl+Z and SIGCONT better (Nathan Rajlich)</p>
+</li>
+<li><p>fs: 64bit offsets for fs calls (Igor Zinkovsky)</p>
+</li>
+<li><p>fs: add sync open flags 'rs' and 'rs+' (Kevin Bowman)</p>
+</li>
+<li><p>windows: enable creating directory junctions with fs.symlink (Igor Zinkovsky, Bert Belder)</p>
+</li>
+<li><p>windows: fix fs.lstat to properly detect symlinks. (Igor Zinkovsky)</p>
+</li>
+<li><p>Fix #3270 Escape url.parse delims (isaacs)</p>
+</li>
+<li><p>http: make http.get() accept a URL (Adam Malcontenti-Wilson)</p>
+</li>
+<li><p>Cleanup vm module memory leakage (Marcel Laverdet)</p>
+</li>
+<li><p>Optimize writing strings with Socket.write (Bert Belder)</p>
+</li>
+<li><p>add support for CESU-8 and UTF-16LE encodings (koichik)</p>
+</li>
+<li><p>path: add path.sep to get the path separator. (Yi, EungJun)</p>
+</li>
+<li><p>net, http: add backlog parameter to .listen() (Erik Dubbelboer)</p>
+</li>
+<li><p>debugger: support mirroring Date objects (Fedor Indutny)</p>
+</li>
+<li><p>addon: add AtExit() function (Ben Noordhuis)</p>
+</li>
+<li><p>net: signal localAddress bind failure in connect (Brian Schroeder)</p>
+</li>
+<li><p>util: handle non-string return value in .inspect() (Alex Kocharin)</p>
+</li>
+</ul>
+<p>Source Code: <a href="http://nodejs.org/dist/v0.7.9/node-v0.7.9.tar.gz">http://nodejs.org/dist/v0.7.9/node-v0.7.9.tar.gz</a>
+
+</p>
+<p>Windows Installer: <a href="http://nodejs.org/dist/v0.7.9/node-v0.7.9.msi">http://nodejs.org/dist/v0.7.9/node-v0.7.9.msi</a>
+
+</p>
+<p>Windows x64 Files: <a href="http://nodejs.org/dist/v0.7.9/x64/">http://nodejs.org/dist/v0.7.9/x64/</a>
+
+</p>
+<p>Macintosh Installer (Universal): <a href="http://nodejs.org/dist/v0.7.9/node-v0.7.9.pkg">http://nodejs.org/dist/v0.7.9/node-v0.7.9.pkg</a>
+
+</p>
+<p>Other release files: <a href="http://nodejs.org/dist/v0.7.9/">http://nodejs.org/dist/v0.7.9/</a>
+
+</p>
+<p>Website: <a href="http://nodejs.org/docs/v0.7.9/">http://nodejs.org/docs/v0.7.9/</a>
+
+</p>
+<p>Documentation: <a href="http://nodejs.org/docs/v0.7.9/api/">http://nodejs.org/docs/v0.7.9/api/</a>
</p>
category: release
slug: version-0-6-11-stable
-<p>2012.02.17 Version 0.6.11 (stable)\r
-\r
-</p>\r
-<ul>\r
-<li><p>http: allow multiple WebSocket RFC6455 headers (Einar Otto Stangvik)</p>\r
-</li>\r
-<li><p>http: allow multiple WWW-Authenticate headers (Ben Noordhuis)</p>\r
-</li>\r
-<li><p>windows: support unicode argv and environment variables (Bert Belder)</p>\r
-</li>\r
-<li><p>tls: mitigate session renegotiation attacks (Ben Noordhuis)</p>\r
-</li>\r
-<li><p>tcp, pipe: don't assert on uv_accept() errors (Ben Noordhuis)</p>\r
-</li>\r
-<li><p>tls: Allow establishing secure connection on the existing socket (koichik)</p>\r
-</li>\r
-<li><p>dgram: handle close of dgram socket before DNS lookup completes (Seth Fitzsimmons)</p>\r
-</li>\r
-<li><p>windows: Support half-duplex pipes (Igor Zinkovsky)</p>\r
-</li>\r
-<li><p>build: disable omit-frame-pointer on solaris systems (Dave Pacheco)</p>\r
-</li>\r
-<li><p>debugger: fix --debug-brk (Ben Noordhuis)</p>\r
-</li>\r
-<li><p>net: fix large file downloads failing (koichik)</p>\r
-</li>\r
-<li><p>fs: fix ReadStream failure to read from existing fd (Christopher Jeffrey)</p>\r
-</li>\r
-<li><p>net: destroy socket on DNS error (Stefan Rusu)</p>\r
-</li>\r
-<li><p>dtrace: add missing translator (Dave Pacheco)</p>\r
-</li>\r
-<li><p>unix: don't flush tty on switch to raw mode (Ben Noordhuis)</p>\r
-</li>\r
-<li><p>windows: reset brightness when reverting to default text color (Bert Belder)</p>\r
-</li>\r
-<li><p>npm: update to 1.1.1</p>\r
-\r
-<p>- Update which, fstream, mkdirp, request, and rimraf<br>- Fix #2123 Set path properly for lifecycle scripts on windows<br>- Mark the root as seen, so we don't recurse into it. Fixes #1838. (Martin Cooper)</p>\r
-\r
-</li>\r
-</ul>\r
-<p>Source Code: <a href="http://nodejs.org/dist/v0.6.11/node-v0.6.11.tar.gz">http://nodejs.org/dist/v0.6.11/node-v0.6.11.tar.gz</a>\r
-\r
-</p>\r
-<p>Windows Installer: <a href="http://nodejs.org/dist/v0.6.11/node-v0.6.11.msi">http://nodejs.org/dist/v0.6.11/node-v0.6.11.msi</a>\r
-\r
-</p>\r
-<p>Macintosh Installer: <a href="http://nodejs.org/dist/v0.6.11/node-v0.6.11.pkg">http://nodejs.org/dist/v0.6.11/node-v0.6.11.pkg</a>\r
-\r
-</p>\r
-<p>Website: <a href="http://nodejs.org/docs/v0.6.11/">http://nodejs.org/docs/v0.6.11/</a>\r
-\r
-</p>\r
-<p>Documentation: <a href="http://nodejs.org/docs/v0.6.11/api/">http://nodejs.org/docs/v0.6.11/api/</a>\r
+<p>2012.02.17 Version 0.6.11 (stable)
+
+</p>
+<ul>
+<li><p>http: allow multiple WebSocket RFC6455 headers (Einar Otto Stangvik)</p>
+</li>
+<li><p>http: allow multiple WWW-Authenticate headers (Ben Noordhuis)</p>
+</li>
+<li><p>windows: support unicode argv and environment variables (Bert Belder)</p>
+</li>
+<li><p>tls: mitigate session renegotiation attacks (Ben Noordhuis)</p>
+</li>
+<li><p>tcp, pipe: don't assert on uv_accept() errors (Ben Noordhuis)</p>
+</li>
+<li><p>tls: Allow establishing secure connection on the existing socket (koichik)</p>
+</li>
+<li><p>dgram: handle close of dgram socket before DNS lookup completes (Seth Fitzsimmons)</p>
+</li>
+<li><p>windows: Support half-duplex pipes (Igor Zinkovsky)</p>
+</li>
+<li><p>build: disable omit-frame-pointer on solaris systems (Dave Pacheco)</p>
+</li>
+<li><p>debugger: fix --debug-brk (Ben Noordhuis)</p>
+</li>
+<li><p>net: fix large file downloads failing (koichik)</p>
+</li>
+<li><p>fs: fix ReadStream failure to read from existing fd (Christopher Jeffrey)</p>
+</li>
+<li><p>net: destroy socket on DNS error (Stefan Rusu)</p>
+</li>
+<li><p>dtrace: add missing translator (Dave Pacheco)</p>
+</li>
+<li><p>unix: don't flush tty on switch to raw mode (Ben Noordhuis)</p>
+</li>
+<li><p>windows: reset brightness when reverting to default text color (Bert Belder)</p>
+</li>
+<li><p>npm: update to 1.1.1</p>
+
+<p>- Update which, fstream, mkdirp, request, and rimraf<br>- Fix #2123 Set path properly for lifecycle scripts on windows<br>- Mark the root as seen, so we don't recurse into it. Fixes #1838. (Martin Cooper)</p>
+
+</li>
+</ul>
+<p>Source Code: <a href="http://nodejs.org/dist/v0.6.11/node-v0.6.11.tar.gz">http://nodejs.org/dist/v0.6.11/node-v0.6.11.tar.gz</a>
+
+</p>
+<p>Windows Installer: <a href="http://nodejs.org/dist/v0.6.11/node-v0.6.11.msi">http://nodejs.org/dist/v0.6.11/node-v0.6.11.msi</a>
+
+</p>
+<p>Macintosh Installer: <a href="http://nodejs.org/dist/v0.6.11/node-v0.6.11.pkg">http://nodejs.org/dist/v0.6.11/node-v0.6.11.pkg</a>
+
+</p>
+<p>Website: <a href="http://nodejs.org/docs/v0.6.11/">http://nodejs.org/docs/v0.6.11/</a>
+
+</p>
+<p>Documentation: <a href="http://nodejs.org/docs/v0.6.11/api/">http://nodejs.org/docs/v0.6.11/api/</a>
</p>
category: release
slug: version-0-6-12-stable
-<p>2012.03.02 Version 0.6.12 (stable)\r
-\r
-</p>\r
-<ul>\r
-<li><p>Upgrade V8 to 3.6.6.24</p>\r
-</li>\r
-<li><p>dtrace ustack helper improvements (Dave Pacheco)</p>\r
-</li>\r
-<li><p>API Documentation refactor (isaacs)</p>\r
-</li>\r
-<li><p>#2827 net: fix race write() before and after connect() (koichik)</p>\r
-</li>\r
-<li><p>#2554 #2567 throw if fs args for 'start' or 'end' are strings (AJ ONeal)</p>\r
-</li>\r
-<li><p>punycode: Update to v1.0.0 (Mathias Bynens)</p>\r
-</li>\r
-<li><p>Make a fat binary for the OS X pkg (isaacs)</p>\r
-</li>\r
-<li><p>Fix hang on accessing process.stdin (isaacs)</p>\r
-</li>\r
-<li><p>repl: make tab completion work on non-objects (Nathan Rajlich)</p>\r
-</li>\r
-<li><p>Fix fs.watch on OS X (Ben Noordhuis)</p>\r
-</li>\r
-<li><p>Fix #2515 nested setTimeouts cause premature process exit (Ben Noordhuis)</p>\r
-</li>\r
-<li><p>windows: fix time conversion in stat (Igor Zinkovsky)</p>\r
-</li>\r
-<li><p>windows: fs: handle EOF in read (Brandon Philips)</p>\r
-</li>\r
-<li><p>windows: avoid IOCP short-circuit on non-ifs lsps (Igor Zinkovsky)</p>\r
-</li>\r
-<li><p>Upgrade npm to 1.1.4 (isaacs)</p>\r
-<p>\r
-- windows fixes<br>\r
-- Bundle nested bundleDependencies properly<br>\r
-- install: support --save with url install targets<br>\r
-- shrinkwrap: behave properly with url-installed modules<br>\r
-- support installing uncompressed tars or single file modules from urls etc.<br>\r
-- don't run make clean on rebuild<br>\r
-- support HTTPS-over-HTTP proxy tunneling<br>\r
-</p>\r
-</li>\r
-</ul>\r
-<p>Source Code: <a href="http://nodejs.org/dist/v0.6.12/node-v0.6.12.tar.gz">http://nodejs.org/dist/v0.6.12/node-v0.6.12.tar.gz</a>\r
-\r
-</p>\r
-<p>Windows Installer: <a href="http://nodejs.org/dist/v0.6.12/node-v0.6.12.msi">http://nodejs.org/dist/v0.6.12/node-v0.6.12.msi</a>\r
-\r
-</p>\r
-<p>Macintosh Installer: <a href="http://nodejs.org/dist/v0.6.12/node-v0.6.12.pkg">http://nodejs.org/dist/v0.6.12/node-v0.6.12.pkg</a>\r
-\r
-</p>\r
-<p>Website: <a href="http://nodejs.org/docs/v0.6.12/">http://nodejs.org/docs/v0.6.12/</a>\r
-\r
-</p>\r
-<p>Documentation: <a href="http://nodejs.org/docs/v0.6.12/api/">http://nodejs.org/docs/v0.6.12/api/</a>\r
+<p>2012.03.02 Version 0.6.12 (stable)
+
+</p>
+<ul>
+<li><p>Upgrade V8 to 3.6.6.24</p>
+</li>
+<li><p>dtrace ustack helper improvements (Dave Pacheco)</p>
+</li>
+<li><p>API Documentation refactor (isaacs)</p>
+</li>
+<li><p>#2827 net: fix race write() before and after connect() (koichik)</p>
+</li>
+<li><p>#2554 #2567 throw if fs args for 'start' or 'end' are strings (AJ ONeal)</p>
+</li>
+<li><p>punycode: Update to v1.0.0 (Mathias Bynens)</p>
+</li>
+<li><p>Make a fat binary for the OS X pkg (isaacs)</p>
+</li>
+<li><p>Fix hang on accessing process.stdin (isaacs)</p>
+</li>
+<li><p>repl: make tab completion work on non-objects (Nathan Rajlich)</p>
+</li>
+<li><p>Fix fs.watch on OS X (Ben Noordhuis)</p>
+</li>
+<li><p>Fix #2515 nested setTimeouts cause premature process exit (Ben Noordhuis)</p>
+</li>
+<li><p>windows: fix time conversion in stat (Igor Zinkovsky)</p>
+</li>
+<li><p>windows: fs: handle EOF in read (Brandon Philips)</p>
+</li>
+<li><p>windows: avoid IOCP short-circuit on non-ifs lsps (Igor Zinkovsky)</p>
+</li>
+<li><p>Upgrade npm to 1.1.4 (isaacs)</p>
+<p>
+- windows fixes<br>
+- Bundle nested bundleDependencies properly<br>
+- install: support --save with url install targets<br>
+- shrinkwrap: behave properly with url-installed modules<br>
+- support installing uncompressed tars or single file modules from urls etc.<br>
+- don't run make clean on rebuild<br>
+- support HTTPS-over-HTTP proxy tunneling<br>
+</p>
+</li>
+</ul>
+<p>Source Code: <a href="http://nodejs.org/dist/v0.6.12/node-v0.6.12.tar.gz">http://nodejs.org/dist/v0.6.12/node-v0.6.12.tar.gz</a>
+
+</p>
+<p>Windows Installer: <a href="http://nodejs.org/dist/v0.6.12/node-v0.6.12.msi">http://nodejs.org/dist/v0.6.12/node-v0.6.12.msi</a>
+
+</p>
+<p>Macintosh Installer: <a href="http://nodejs.org/dist/v0.6.12/node-v0.6.12.pkg">http://nodejs.org/dist/v0.6.12/node-v0.6.12.pkg</a>
+
+</p>
+<p>Website: <a href="http://nodejs.org/docs/v0.6.12/">http://nodejs.org/docs/v0.6.12/</a>
+
+</p>
+<p>Documentation: <a href="http://nodejs.org/docs/v0.6.12/api/">http://nodejs.org/docs/v0.6.12/api/</a>
</p>
category: release
slug: version-0-6-13-stable
-<p>2012.03.15 Version 0.6.13 (stable)\r
-\r
-</p>\r
-<ul>\r
-<li><p>Windows: Many libuv test fixes (Bert Belder)</p>\r
-</li>\r
-<li><p>Windows: avoid uv_guess_handle crash in when fd < 0 (Bert Belder)</p>\r
-</li>\r
-<li><p>Map EBUSY and ENOTEMPTY errors (Bert Belder)</p>\r
-</li>\r
-<li><p>Windows: include syscall in fs errors (Bert Belder)</p>\r
-</li>\r
-<li><p>Fix fs.watch ENOSYS on Linux kernel version mismatch (Ben Noordhuis)</p>\r
-</li>\r
-<li><p>Update npm to 1.1.9</p>\r
-<p>\r
-- upgrade node-gyp to 0.3.5 (Nathan Rajlich)<br>\r
-- Fix isaacs/npm#2249 Add cache-max and cache-min configs<br>\r
-- Properly redirect across https/http registry requests<br>\r
-- log config usage if undefined key in set function (Kris Windham)<br>\r
-- Add support for os/cpu fields in package.json (Adam Blackburn)<br>\r
-- Automatically node-gyp packages containing a binding.gyp<br>\r
-- Fix failures unpacking in UNC shares<br>\r
-- Never create un-listable directories<br>\r
-- Handle cases where an optionalDependency fails to build\r
-</p>\r
-</li>\r
-</ul>\r
-<p>Source Code: <a href="http://nodejs.org/dist/v0.6.13/node-v0.6.13.tar.gz">http://nodejs.org/dist/v0.6.13/node-v0.6.13.tar.gz</a>\r
-\r
-</p>\r
-<p>Windows Installer: <a href="http://nodejs.org/dist/v0.6.13/node-v0.6.13.msi">http://nodejs.org/dist/v0.6.13/node-v0.6.13.msi</a>\r
-\r
-</p>\r
-<p>Macintosh Installer: <a href="http://nodejs.org/dist/v0.6.13/node-v0.6.13.pkg">http://nodejs.org/dist/v0.6.13/node-v0.6.13.pkg</a>\r
-\r
-</p>\r
-<p>Website: <a href="http://nodejs.org/docs/v0.6.13/">http://nodejs.org/docs/v0.6.13/</a>\r
-\r
-</p>\r
-<p>Documentation: <a href="http://nodejs.org/docs/v0.6.13/api/">http://nodejs.org/docs/v0.6.13/api/</a>\r
+<p>2012.03.15 Version 0.6.13 (stable)
+
+</p>
+<ul>
+<li><p>Windows: Many libuv test fixes (Bert Belder)</p>
+</li>
+<li><p>Windows: avoid uv_guess_handle crash in when fd < 0 (Bert Belder)</p>
+</li>
+<li><p>Map EBUSY and ENOTEMPTY errors (Bert Belder)</p>
+</li>
+<li><p>Windows: include syscall in fs errors (Bert Belder)</p>
+</li>
+<li><p>Fix fs.watch ENOSYS on Linux kernel version mismatch (Ben Noordhuis)</p>
+</li>
+<li><p>Update npm to 1.1.9</p>
+<p>
+- upgrade node-gyp to 0.3.5 (Nathan Rajlich)<br>
+- Fix isaacs/npm#2249 Add cache-max and cache-min configs<br>
+- Properly redirect across https/http registry requests<br>
+- log config usage if undefined key in set function (Kris Windham)<br>
+- Add support for os/cpu fields in package.json (Adam Blackburn)<br>
+- Automatically node-gyp packages containing a binding.gyp<br>
+- Fix failures unpacking in UNC shares<br>
+- Never create un-listable directories<br>
+- Handle cases where an optionalDependency fails to build
+</p>
+</li>
+</ul>
+<p>Source Code: <a href="http://nodejs.org/dist/v0.6.13/node-v0.6.13.tar.gz">http://nodejs.org/dist/v0.6.13/node-v0.6.13.tar.gz</a>
+
+</p>
+<p>Windows Installer: <a href="http://nodejs.org/dist/v0.6.13/node-v0.6.13.msi">http://nodejs.org/dist/v0.6.13/node-v0.6.13.msi</a>
+
+</p>
+<p>Macintosh Installer: <a href="http://nodejs.org/dist/v0.6.13/node-v0.6.13.pkg">http://nodejs.org/dist/v0.6.13/node-v0.6.13.pkg</a>
+
+</p>
+<p>Website: <a href="http://nodejs.org/docs/v0.6.13/">http://nodejs.org/docs/v0.6.13/</a>
+
+</p>
+<p>Documentation: <a href="http://nodejs.org/docs/v0.6.13/api/">http://nodejs.org/docs/v0.6.13/api/</a>
</p>
category: release
slug: version-0-6-14-stable
-<p>2012.03.22 Version 0.6.14 (stable)\r
-\r
-</p>\r
-<ul>\r
-<li><p>net: don't crash when queued write fails (Igor Zinkovsky)</p>\r
-</li>\r
-<li><p>sunos: fix EMFILE on process.memoryUsage() (Bryan Cantrill)</p>\r
-</li>\r
-<li><p>crypto: fix compile-time error with openssl 0.9.7e (Ben Noordhuis)</p>\r
-</li>\r
-<li><p>unix: ignore ECONNABORTED errors from accept() (Ben Noordhuis)</p>\r
-</li>\r
-<li><p>Add UV_ENOSPC and mappings to it (Bert Belder)</p>\r
-</li>\r
-<li><p>http-parser: Fix response body is not read (koichik)</p>\r
-</li>\r
-<li><p>Upgrade npm to 1.1.12</p>\r
-<p>\r
-- upgrade node-gyp to 0.3.7<br>\r
-- work around AV-locked directories on Windows<br>\r
-- Fix isaacs/npm#2293 Don't try to 'uninstall' /<br>\r
-- Exclude symbolic links from packages.<br>\r
-- Fix isaacs/npm#2275 Spurious 'unresolvable cycle' error.<br>\r
-- Exclude/include dot files as if they were normal files\r
-</p>\r
-</li>\r
-</ul>\r
-<p>Source Code: <a href="http://nodejs.org/dist/v0.6.14/node-v0.6.14.tar.gz">http://nodejs.org/dist/v0.6.14/node-v0.6.14.tar.gz</a>\r
-\r
-</p>\r
-<p>Windows Installer: <a href="http://nodejs.org/dist/v0.6.14/node-v0.6.14.msi">http://nodejs.org/dist/v0.6.14/node-v0.6.14.msi</a>\r
-\r
-</p>\r
-<p>Windows x64 Files: <a href="http://nodejs.org/dist/v0.6.14/x64/">http://nodejs.org/dist/v0.6.14/x64/</a>\r
-\r
-</p>\r
-<p>Macintosh Installer (Universal): <a href="http://nodejs.org/dist/v0.6.14/node-v0.6.14.pkg">http://nodejs.org/dist/v0.6.14/node-v0.6.14.pkg</a>\r
-\r
-</p>\r
-<p>Other release files: <a href="http://nodejs.org/dist/v0.6.14/">http://nodejs.org/dist/v0.6.14/</a>\r
-\r
-</p>\r
-<p>Website: <a href="http://nodejs.org/docs/v0.6.14/">http://nodejs.org/docs/v0.6.14/</a>\r
-\r
-</p>\r
-<p>Documentation: <a href="http://nodejs.org/docs/v0.6.14/api/">http://nodejs.org/docs/v0.6.14/api/</a>\r
+<p>2012.03.22 Version 0.6.14 (stable)
+
+</p>
+<ul>
+<li><p>net: don't crash when queued write fails (Igor Zinkovsky)</p>
+</li>
+<li><p>sunos: fix EMFILE on process.memoryUsage() (Bryan Cantrill)</p>
+</li>
+<li><p>crypto: fix compile-time error with openssl 0.9.7e (Ben Noordhuis)</p>
+</li>
+<li><p>unix: ignore ECONNABORTED errors from accept() (Ben Noordhuis)</p>
+</li>
+<li><p>Add UV_ENOSPC and mappings to it (Bert Belder)</p>
+</li>
+<li><p>http-parser: Fix response body is not read (koichik)</p>
+</li>
+<li><p>Upgrade npm to 1.1.12</p>
+<p>
+- upgrade node-gyp to 0.3.7<br>
+- work around AV-locked directories on Windows<br>
+- Fix isaacs/npm#2293 Don't try to 'uninstall' /<br>
+- Exclude symbolic links from packages.<br>
+- Fix isaacs/npm#2275 Spurious 'unresolvable cycle' error.<br>
+- Exclude/include dot files as if they were normal files
+</p>
+</li>
+</ul>
+<p>Source Code: <a href="http://nodejs.org/dist/v0.6.14/node-v0.6.14.tar.gz">http://nodejs.org/dist/v0.6.14/node-v0.6.14.tar.gz</a>
+
+</p>
+<p>Windows Installer: <a href="http://nodejs.org/dist/v0.6.14/node-v0.6.14.msi">http://nodejs.org/dist/v0.6.14/node-v0.6.14.msi</a>
+
+</p>
+<p>Windows x64 Files: <a href="http://nodejs.org/dist/v0.6.14/x64/">http://nodejs.org/dist/v0.6.14/x64/</a>
+
+</p>
+<p>Macintosh Installer (Universal): <a href="http://nodejs.org/dist/v0.6.14/node-v0.6.14.pkg">http://nodejs.org/dist/v0.6.14/node-v0.6.14.pkg</a>
+
+</p>
+<p>Other release files: <a href="http://nodejs.org/dist/v0.6.14/">http://nodejs.org/dist/v0.6.14/</a>
+
+</p>
+<p>Website: <a href="http://nodejs.org/docs/v0.6.14/">http://nodejs.org/docs/v0.6.14/</a>
+
+</p>
+<p>Documentation: <a href="http://nodejs.org/docs/v0.6.14/api/">http://nodejs.org/docs/v0.6.14/api/</a>
</p>
category: release
slug: version-0-6-15-stable
-<p>2012.04.09 Version 0.6.15 (stable)\r
-\r
-</p>\r
-<ul>\r
-<li><p>Update npm to 1.1.16</p>\r
-</li>\r
-<li><p>Show licenses in binary installers.</p>\r
-</li>\r
-<li><p>unix: add uv_fs_read64, uv_fs_write64 and uv_fs_ftruncate64 (Ben Noordhuis)</p>\r
-</li>\r
-<li><p>add 64bit offset fs functions (Igor Zinkovsky)</p>\r
-</li>\r
-<li><p>windows: don't report ENOTSOCK when attempting to bind an udp handle twice (Bert Belder)</p>\r
-</li>\r
-<li><p>windows: backport pipe-connect-to-file fixes from master (Bert Belder)</p>\r
-</li>\r
-<li><p>windows: never call fs event callbacks after closing the watcher (Bert Belder)</p>\r
-</li>\r
-<li><p>fs.readFile: don't make the callback before the fd is closed (Bert Belder)</p>\r
-</li>\r
-<li><p>windows: use 64bit offsets for uv_fs apis (Igor Zinkovsky)</p>\r
-</li>\r
-<li><p>Fix #2061: segmentation fault on OS X due to stat size mismatch (Ben Noordhuis)</p>\r
-</li>\r
-</ul>\r
-<p>Source Code: <a href="http://nodejs.org/dist/v0.6.15/node-v0.6.15.tar.gz">http://nodejs.org/dist/v0.6.15/node-v0.6.15.tar.gz</a>\r
-\r
-</p>\r
-<p>Windows Installer: <a href="http://nodejs.org/dist/v0.6.15/node-v0.6.15.msi">http://nodejs.org/dist/v0.6.15/node-v0.6.15.msi</a>\r
-\r
-</p>\r
-<p>Windows x64 Files: <a href="http://nodejs.org/dist/v0.6.15/x64/">http://nodejs.org/dist/v0.6.15/x64/</a>\r
-\r
-</p>\r
-<p>Macintosh Installer (Universal): <a href="http://nodejs.org/dist/v0.6.15/node-v0.6.15.pkg">http://nodejs.org/dist/v0.6.15/node-v0.6.15.pkg</a>\r
-\r
-</p>\r
-<p>Other release files: <a href="http://nodejs.org/dist/v0.6.15/">http://nodejs.org/dist/v0.6.15/</a>\r
-\r
-</p>\r
-<p>Website: <a href="http://nodejs.org/docs/v0.6.15/">http://nodejs.org/docs/v0.6.15/</a>\r
-\r
-</p>\r
-<p>Documentation: <a href="http://nodejs.org/docs/v0.6.15/api/">http://nodejs.org/docs/v0.6.15/api/</a>\r
+<p>2012.04.09 Version 0.6.15 (stable)
+
+</p>
+<ul>
+<li><p>Update npm to 1.1.16</p>
+</li>
+<li><p>Show licenses in binary installers.</p>
+</li>
+<li><p>unix: add uv_fs_read64, uv_fs_write64 and uv_fs_ftruncate64 (Ben Noordhuis)</p>
+</li>
+<li><p>add 64bit offset fs functions (Igor Zinkovsky)</p>
+</li>
+<li><p>windows: don't report ENOTSOCK when attempting to bind an udp handle twice (Bert Belder)</p>
+</li>
+<li><p>windows: backport pipe-connect-to-file fixes from master (Bert Belder)</p>
+</li>
+<li><p>windows: never call fs event callbacks after closing the watcher (Bert Belder)</p>
+</li>
+<li><p>fs.readFile: don't make the callback before the fd is closed (Bert Belder)</p>
+</li>
+<li><p>windows: use 64bit offsets for uv_fs apis (Igor Zinkovsky)</p>
+</li>
+<li><p>Fix #2061: segmentation fault on OS X due to stat size mismatch (Ben Noordhuis)</p>
+</li>
+</ul>
+<p>Source Code: <a href="http://nodejs.org/dist/v0.6.15/node-v0.6.15.tar.gz">http://nodejs.org/dist/v0.6.15/node-v0.6.15.tar.gz</a>
+
+</p>
+<p>Windows Installer: <a href="http://nodejs.org/dist/v0.6.15/node-v0.6.15.msi">http://nodejs.org/dist/v0.6.15/node-v0.6.15.msi</a>
+
+</p>
+<p>Windows x64 Files: <a href="http://nodejs.org/dist/v0.6.15/x64/">http://nodejs.org/dist/v0.6.15/x64/</a>
+
+</p>
+<p>Macintosh Installer (Universal): <a href="http://nodejs.org/dist/v0.6.15/node-v0.6.15.pkg">http://nodejs.org/dist/v0.6.15/node-v0.6.15.pkg</a>
+
+</p>
+<p>Other release files: <a href="http://nodejs.org/dist/v0.6.15/">http://nodejs.org/dist/v0.6.15/</a>
+
+</p>
+<p>Website: <a href="http://nodejs.org/docs/v0.6.15/">http://nodejs.org/docs/v0.6.15/</a>
+
+</p>
+<p>Documentation: <a href="http://nodejs.org/docs/v0.6.15/api/">http://nodejs.org/docs/v0.6.15/api/</a>
</p>
category: release
slug: version-0-6-16-stable
-<p>2012.04.30 Version 0.6.16 (stable)\r
-\r
-</p>\r
-<ul>\r
-<li><p>Upgrade V8 to 3.6.6.25</p>\r
-</li>\r
-<li><p>Upgrade npm to 1.1.18</p>\r
-</li>\r
-<li><p>Windows: add mappings for UV_ENOENT (Bert Belder)</p>\r
-</li>\r
-<li><p>linux: add IN_MOVE_SELF to inotify event mask (Ben Noordhuis)</p>\r
-</li>\r
-<li><p>unix: call pipe handle connection cb on accept() error (Ben Noordhuis)</p>\r
-</li>\r
-<li><p>unix: handle EWOULDBLOCK (Ben Noordhuis)</p>\r
-</li>\r
-<li><p>map EWOULDBLOCK to UV_EAGAIN (Ben Noordhuis)</p>\r
-</li>\r
-<li><p>Map ENOMEM to UV_ENOMEM (isaacs)</p>\r
-</li>\r
-<li><p>Child process: support the <code>gid</code> and <code>uid</code> options (Bert Belder)</p>\r
-</li>\r
-<li><p>test: cluster: add worker death event test (Ben Noordhuis)</p>\r
-</li>\r
-<li><p>typo in node_http_parser (isaacs)</p>\r
-</li>\r
-<li><p>http_parser: Eat CRLF between requests, even on connection:close. (Ben Noordhuis)</p>\r
-</li>\r
-<li><p>don't check return value of unsetenv (Ben Noordhuis)</p>\r
-</li>\r
-</ul>\r
-<p>Source Code: <a href="http://nodejs.org/dist/v0.6.16/node-v0.6.16.tar.gz">http://nodejs.org/dist/v0.6.16/node-v0.6.16.tar.gz</a>\r
-\r
-</p>\r
-<p>Windows Installer: <a href="http://nodejs.org/dist/v0.6.16/node-v0.6.16.msi">http://nodejs.org/dist/v0.6.16/node-v0.6.16.msi</a>\r
-\r
-</p>\r
-<p>Windows x64 Files: <a href="http://nodejs.org/dist/v0.6.16/x64/">http://nodejs.org/dist/v0.6.16/x64/</a>\r
-\r
-</p>\r
-<p>Macintosh Installer (Universal): <a href="http://nodejs.org/dist/v0.6.16/node-v0.6.16.pkg">http://nodejs.org/dist/v0.6.16/node-v0.6.16.pkg</a>\r
-\r
-</p>\r
-<p>Other release files: <a href="http://nodejs.org/dist/v0.6.16/">http://nodejs.org/dist/v0.6.16/</a>\r
-\r
-</p>\r
-<p>Website: <a href="http://nodejs.org/docs/v0.6.16/">http://nodejs.org/docs/v0.6.16/</a>\r
-\r
-</p>\r
-<p>Documentation: <a href="http://nodejs.org/docs/v0.6.16/api/">http://nodejs.org/docs/v0.6.16/api/</a>\r
+<p>2012.04.30 Version 0.6.16 (stable)
+
+</p>
+<ul>
+<li><p>Upgrade V8 to 3.6.6.25</p>
+</li>
+<li><p>Upgrade npm to 1.1.18</p>
+</li>
+<li><p>Windows: add mappings for UV_ENOENT (Bert Belder)</p>
+</li>
+<li><p>linux: add IN_MOVE_SELF to inotify event mask (Ben Noordhuis)</p>
+</li>
+<li><p>unix: call pipe handle connection cb on accept() error (Ben Noordhuis)</p>
+</li>
+<li><p>unix: handle EWOULDBLOCK (Ben Noordhuis)</p>
+</li>
+<li><p>map EWOULDBLOCK to UV_EAGAIN (Ben Noordhuis)</p>
+</li>
+<li><p>Map ENOMEM to UV_ENOMEM (isaacs)</p>
+</li>
+<li><p>Child process: support the <code>gid</code> and <code>uid</code> options (Bert Belder)</p>
+</li>
+<li><p>test: cluster: add worker death event test (Ben Noordhuis)</p>
+</li>
+<li><p>typo in node_http_parser (isaacs)</p>
+</li>
+<li><p>http_parser: Eat CRLF between requests, even on connection:close. (Ben Noordhuis)</p>
+</li>
+<li><p>don't check return value of unsetenv (Ben Noordhuis)</p>
+</li>
+</ul>
+<p>Source Code: <a href="http://nodejs.org/dist/v0.6.16/node-v0.6.16.tar.gz">http://nodejs.org/dist/v0.6.16/node-v0.6.16.tar.gz</a>
+
+</p>
+<p>Windows Installer: <a href="http://nodejs.org/dist/v0.6.16/node-v0.6.16.msi">http://nodejs.org/dist/v0.6.16/node-v0.6.16.msi</a>
+
+</p>
+<p>Windows x64 Files: <a href="http://nodejs.org/dist/v0.6.16/x64/">http://nodejs.org/dist/v0.6.16/x64/</a>
+
+</p>
+<p>Macintosh Installer (Universal): <a href="http://nodejs.org/dist/v0.6.16/node-v0.6.16.pkg">http://nodejs.org/dist/v0.6.16/node-v0.6.16.pkg</a>
+
+</p>
+<p>Other release files: <a href="http://nodejs.org/dist/v0.6.16/">http://nodejs.org/dist/v0.6.16/</a>
+
+</p>
+<p>Website: <a href="http://nodejs.org/docs/v0.6.16/">http://nodejs.org/docs/v0.6.16/</a>
+
+</p>
+<p>Documentation: <a href="http://nodejs.org/docs/v0.6.16/api/">http://nodejs.org/docs/v0.6.16/api/</a>
</p>
category: release
slug: version-0-6-17-stable
-<p>2012.05.04 Version 0.6.17 (stable)\r
-\r
-</p>\r
-<ul>\r
-<li><p>Upgrade npm to 1.1.21</p>\r
-</li>\r
-<li><p>uv: Add support for EROFS errors (Ben Noordhuis, Maciej Małecki)</p>\r
-</li>\r
-<li><p>uv: Add support for EIO and ENOSPC errors (Fedor Indutny)</p>\r
-</li>\r
-<li><p>windows: Add support for EXDEV errors (Bert Belder)</p>\r
-</li>\r
-<li><p>http: Fix client memory leaks (isaacs, Vincent Voyer)</p>\r
-</li>\r
-<li><p>fs: fix file descriptor leak in sync functions (Ben Noordhuis)</p>\r
-</li>\r
-<li><p>fs: fix ReadStream / WriteStream double close bug (Ben Noordhuis)</p>\r
-</li>\r
-</ul>\r
-<p>Source Code: <a href="http://nodejs.org/dist/v0.6.17/node-v0.6.17.tar.gz">http://nodejs.org/dist/v0.6.17/node-v0.6.17.tar.gz</a>\r
-\r
-</p>\r
-<p>Windows Installer: <a href="http://nodejs.org/dist/v0.6.17/node-v0.6.17.msi">http://nodejs.org/dist/v0.6.17/node-v0.6.17.msi</a>\r
-\r
-</p>\r
-<p>Windows x64 Files: <a href="http://nodejs.org/dist/v0.6.17/x64/">http://nodejs.org/dist/v0.6.17/x64/</a>\r
-\r
-</p>\r
-<p>Macintosh Installer (Universal): <a href="http://nodejs.org/dist/v0.6.17/node-v0.6.17.pkg">http://nodejs.org/dist/v0.6.17/node-v0.6.17.pkg</a>\r
-\r
-</p>\r
-<p>Other release files: <a href="http://nodejs.org/dist/v0.6.17/">http://nodejs.org/dist/v0.6.17/</a>\r
-\r
-</p>\r
-<p>Website: <a href="http://nodejs.org/docs/v0.6.17/">http://nodejs.org/docs/v0.6.17/</a>\r
-\r
-</p>\r
-<p>Documentation: <a href="http://nodejs.org/docs/v0.6.17/api/">http://nodejs.org/docs/v0.6.17/api/</a>\r
+<p>2012.05.04 Version 0.6.17 (stable)
+
+</p>
+<ul>
+<li><p>Upgrade npm to 1.1.21</p>
+</li>
+<li><p>uv: Add support for EROFS errors (Ben Noordhuis, Maciej Małecki)</p>
+</li>
+<li><p>uv: Add support for EIO and ENOSPC errors (Fedor Indutny)</p>
+</li>
+<li><p>windows: Add support for EXDEV errors (Bert Belder)</p>
+</li>
+<li><p>http: Fix client memory leaks (isaacs, Vincent Voyer)</p>
+</li>
+<li><p>fs: fix file descriptor leak in sync functions (Ben Noordhuis)</p>
+</li>
+<li><p>fs: fix ReadStream / WriteStream double close bug (Ben Noordhuis)</p>
+</li>
+</ul>
+<p>Source Code: <a href="http://nodejs.org/dist/v0.6.17/node-v0.6.17.tar.gz">http://nodejs.org/dist/v0.6.17/node-v0.6.17.tar.gz</a>
+
+</p>
+<p>Windows Installer: <a href="http://nodejs.org/dist/v0.6.17/node-v0.6.17.msi">http://nodejs.org/dist/v0.6.17/node-v0.6.17.msi</a>
+
+</p>
+<p>Windows x64 Files: <a href="http://nodejs.org/dist/v0.6.17/x64/">http://nodejs.org/dist/v0.6.17/x64/</a>
+
+</p>
+<p>Macintosh Installer (Universal): <a href="http://nodejs.org/dist/v0.6.17/node-v0.6.17.pkg">http://nodejs.org/dist/v0.6.17/node-v0.6.17.pkg</a>
+
+</p>
+<p>Other release files: <a href="http://nodejs.org/dist/v0.6.17/">http://nodejs.org/dist/v0.6.17/</a>
+
+</p>
+<p>Website: <a href="http://nodejs.org/docs/v0.6.17/">http://nodejs.org/docs/v0.6.17/</a>
+
+</p>
+<p>Documentation: <a href="http://nodejs.org/docs/v0.6.17/api/">http://nodejs.org/docs/v0.6.17/api/</a>
</p>
category: release
slug: version-0-6-18-stable
-<p>2012.05.15 Version 0.6.18 (stable)\r
-\r
-</p>\r
-<ul>\r
-<li><p>windows: skip GetFileAttributes call when opening a file (Bert Belder)</p>\r
-</li>\r
-<li><p>crypto: add PKCS12/PFX support (Sambasiva Suda)</p>\r
-</li>\r
-<li><p>#3240: child_process: delete NODE_CHANNEL_FD from env in spawn (Ben Noordhuis)</p>\r
-</li>\r
-<li><p>windows: add test for path.normalize with UNC paths (Bert Belder)</p>\r
-</li>\r
-<li><p>windows: make path.normalize convert all slashes to backslashes (Bert Belder)</p>\r
-</li>\r
-<li><p>fs: Automatically close FSWatcher on error (Bert Belder)</p>\r
-</li>\r
-<li><p>#3258: fs.ReadStream.pause() emits duplicate data event (koichik)</p>\r
-</li>\r
-<li><p>pipe_wrap: don't assert() on pipe accept errors (Ben Noordhuis)</p>\r
-</li>\r
-<li><p>Better exception output for module load and process.nextTick (Felix Geisendörfer)</p>\r
-</li>\r
-<li><p>zlib: fix error reporting (Ben Noordhuis)</p>\r
-</li>\r
-<li><p>http: Don't destroy on timeout (isaacs)</p>\r
-</li>\r
-<li><p>#3231: http: Don't try to emit error on a null'ed req object (isaacs)</p>\r
-</li>\r
-<li><p>#3236: http: Refactor ClientRequest.onSocket (isaacs)</p>\r
-</li>\r
-</ul>\r
-<p>Source Code: <a href="http://nodejs.org/dist/v0.6.18/node-v0.6.18.tar.gz">http://nodejs.org/dist/v0.6.18/node-v0.6.18.tar.gz</a>\r
-\r
-</p>\r
-<p>Windows Installer: <a href="http://nodejs.org/dist/v0.6.18/node-v0.6.18.msi">http://nodejs.org/dist/v0.6.18/node-v0.6.18.msi</a>\r
-\r
-</p>\r
-<p>Windows x64 Files: <a href="http://nodejs.org/dist/v0.6.18/x64/">http://nodejs.org/dist/v0.6.18/x64/</a>\r
-\r
-</p>\r
-<p>Macintosh Installer (Universal): <a href="http://nodejs.org/dist/v0.6.18/node-v0.6.18.pkg">http://nodejs.org/dist/v0.6.18/node-v0.6.18.pkg</a>\r
-\r
-</p>\r
-<p>Other release files: <a href="http://nodejs.org/dist/v0.6.18/">http://nodejs.org/dist/v0.6.18/</a>\r
-\r
-</p>\r
-<p>Website: <a href="http://nodejs.org/docs/v0.6.18/">http://nodejs.org/docs/v0.6.18/</a>\r
-\r
-</p>\r
-<p>Documentation: <a href="http://nodejs.org/docs/v0.6.18/api/">http://nodejs.org/docs/v0.6.18/api/</a>\r
+<p>2012.05.15 Version 0.6.18 (stable)
+
+</p>
+<ul>
+<li><p>windows: skip GetFileAttributes call when opening a file (Bert Belder)</p>
+</li>
+<li><p>crypto: add PKCS12/PFX support (Sambasiva Suda)</p>
+</li>
+<li><p>#3240: child_process: delete NODE_CHANNEL_FD from env in spawn (Ben Noordhuis)</p>
+</li>
+<li><p>windows: add test for path.normalize with UNC paths (Bert Belder)</p>
+</li>
+<li><p>windows: make path.normalize convert all slashes to backslashes (Bert Belder)</p>
+</li>
+<li><p>fs: Automatically close FSWatcher on error (Bert Belder)</p>
+</li>
+<li><p>#3258: fs.ReadStream.pause() emits duplicate data event (koichik)</p>
+</li>
+<li><p>pipe_wrap: don't assert() on pipe accept errors (Ben Noordhuis)</p>
+</li>
+<li><p>Better exception output for module load and process.nextTick (Felix Geisendörfer)</p>
+</li>
+<li><p>zlib: fix error reporting (Ben Noordhuis)</p>
+</li>
+<li><p>http: Don't destroy on timeout (isaacs)</p>
+</li>
+<li><p>#3231: http: Don't try to emit error on a null'ed req object (isaacs)</p>
+</li>
+<li><p>#3236: http: Refactor ClientRequest.onSocket (isaacs)</p>
+</li>
+</ul>
+<p>Source Code: <a href="http://nodejs.org/dist/v0.6.18/node-v0.6.18.tar.gz">http://nodejs.org/dist/v0.6.18/node-v0.6.18.tar.gz</a>
+
+</p>
+<p>Windows Installer: <a href="http://nodejs.org/dist/v0.6.18/node-v0.6.18.msi">http://nodejs.org/dist/v0.6.18/node-v0.6.18.msi</a>
+
+</p>
+<p>Windows x64 Files: <a href="http://nodejs.org/dist/v0.6.18/x64/">http://nodejs.org/dist/v0.6.18/x64/</a>
+
+</p>
+<p>Macintosh Installer (Universal): <a href="http://nodejs.org/dist/v0.6.18/node-v0.6.18.pkg">http://nodejs.org/dist/v0.6.18/node-v0.6.18.pkg</a>
+
+</p>
+<p>Other release files: <a href="http://nodejs.org/dist/v0.6.18/">http://nodejs.org/dist/v0.6.18/</a>
+
+</p>
+<p>Website: <a href="http://nodejs.org/docs/v0.6.18/">http://nodejs.org/docs/v0.6.18/</a>
+
+</p>
+<p>Documentation: <a href="http://nodejs.org/docs/v0.6.18/api/">http://nodejs.org/docs/v0.6.18/api/</a>
</p>
category: release
slug: version-0-7-10-unstable
-<p>2012.06.11, Version 0.7.10 (unstable)\r
-\r
-</p>\r
-<p>This is the second-to-last release on the 0.7 branch. Version 0.8.0\r
-will be released some time next week. As other even-numbered Node\r
-releases before it, the v0.8.x releases will maintain API and binary\r
-compatibility.\r
-\r
-</p>\r
-<p>The major changes are detailed in\r
-<a href="https://github.com/joyent/node/wiki/API-changes-between-v0.6-and-v0.8">https://github.com/joyent/node/wiki/API-changes-between-v0.6-and-v0.8</a>\r
-\r
-</p>\r
-<p>Please try out this release. There will be very few changes between\r
-this and the v0.8.x release family. This is the last chance to comment\r
-on the API before it is locked down for stability.\r
-\r
-\r
-</p>\r
-<ul>\r
-<li><p>Roll V8 back to 3.9.24.31</p>\r
-</li>\r
-<li><p>build: x64 target should always pass -m64 (Robert Mustacchi)</p>\r
-</li>\r
-<li><p>add NODE_EXTERN to node::Start (Joel Brandt)</p>\r
-</li>\r
-<li><p>repl: Warn about running npm commands (isaacs)</p>\r
-</li>\r
-<li><p>slab_allocator: fix crash in dtor if V8 is dead (Ben Noordhuis)</p>\r
-</li>\r
-<li><p>slab_allocator: fix leak of Persistent handles (Shigeki Ohtsu)</p>\r
-</li>\r
-<li><p>windows/msi: add node.js prompt to startmenu (Jeroen Janssen)</p>\r
-</li>\r
-<li><p>windows/msi: fix adding node to PATH (Jeroen Janssen)</p>\r
-</li>\r
-<li><p>windows/msi: add start menu links when installing (Jeroen Janssen)</p>\r
-</li>\r
-<li><p>windows: don't install x64 version into the 'program files (x86)' folder (Matt Gollob)</p>\r
-</li>\r
-<li><p>domain: Fix #3379 domain.intercept no longer passes error arg to cb (Marc Harter)</p>\r
-</li>\r
-<li><p>fs: make callbacks run in global context (Ben Noordhuis)</p>\r
-</li>\r
-<li><p>fs: enable fs.realpath on windows (isaacs)</p>\r
-</li>\r
-<li><p>child_process: expose UV_PROCESS_DETACHED as options.detached (Charlie McConnell)</p>\r
-</li>\r
-<li><p>child_process: new stdio API for .spawn() method (Fedor Indutny)</p>\r
-</li>\r
-<li><p>child_process: spawn().ref() and spawn().unref() (Fedor Indutny)</p>\r
-</li>\r
-<li><p>Upgrade npm to 1.1.25</p>\r
-</li>\r
-<ul><li>Enable npm link on windows</li>\r
-<li>Properly remove sh-shim on Windows</li>\r
-<li>Abstract out registry client and logger</li></ul>\r
-</ul>\r
-<p>Source Code: <a href="http://nodejs.org/dist/v0.7.10/node-v0.7.10.tar.gz">http://nodejs.org/dist/v0.7.10/node-v0.7.10.tar.gz</a>\r
-\r
-</p>\r
-<p>Windows Installer: <a href="http://nodejs.org/dist/v0.7.10/node-v0.7.10.msi">http://nodejs.org/dist/v0.7.10/node-v0.7.10.msi</a>\r
-\r
-</p>\r
-<p>Windows x64 Files: <a href="http://nodejs.org/dist/v0.7.10/x64/">http://nodejs.org/dist/v0.7.10/x64/</a>\r
-\r
-</p>\r
-<p>Macintosh Installer (Universal): <a href="http://nodejs.org/dist/v0.7.10/node-v0.7.10.pkg">http://nodejs.org/dist/v0.7.10/node-v0.7.10.pkg</a>\r
-\r
-</p>\r
-<p>Other release files: <a href="http://nodejs.org/dist/v0.7.10/">http://nodejs.org/dist/v0.7.10/</a>\r
-\r
-</p>\r
-<p>Website: <a href="http://nodejs.org/docs/v0.7.10/">http://nodejs.org/docs/v0.7.10/</a>\r
-\r
-</p>\r
-<p>Documentation: <a href="http://nodejs.org/docs/v0.7.10/api/">http://nodejs.org/docs/v0.7.10/api/</a>\r
+<p>2012.06.11, Version 0.7.10 (unstable)
+
+</p>
+<p>This is the second-to-last release on the 0.7 branch. Version 0.8.0
+will be released some time next week. As other even-numbered Node
+releases before it, the v0.8.x releases will maintain API and binary
+compatibility.
+
+</p>
+<p>The major changes are detailed in
+<a href="https://github.com/joyent/node/wiki/API-changes-between-v0.6-and-v0.8">https://github.com/joyent/node/wiki/API-changes-between-v0.6-and-v0.8</a>
+
+</p>
+<p>Please try out this release. There will be very few changes between
+this and the v0.8.x release family. This is the last chance to comment
+on the API before it is locked down for stability.
+
+
+</p>
+<ul>
+<li><p>Roll V8 back to 3.9.24.31</p>
+</li>
+<li><p>build: x64 target should always pass -m64 (Robert Mustacchi)</p>
+</li>
+<li><p>add NODE_EXTERN to node::Start (Joel Brandt)</p>
+</li>
+<li><p>repl: Warn about running npm commands (isaacs)</p>
+</li>
+<li><p>slab_allocator: fix crash in dtor if V8 is dead (Ben Noordhuis)</p>
+</li>
+<li><p>slab_allocator: fix leak of Persistent handles (Shigeki Ohtsu)</p>
+</li>
+<li><p>windows/msi: add node.js prompt to startmenu (Jeroen Janssen)</p>
+</li>
+<li><p>windows/msi: fix adding node to PATH (Jeroen Janssen)</p>
+</li>
+<li><p>windows/msi: add start menu links when installing (Jeroen Janssen)</p>
+</li>
+<li><p>windows: don't install x64 version into the 'program files (x86)' folder (Matt Gollob)</p>
+</li>
+<li><p>domain: Fix #3379 domain.intercept no longer passes error arg to cb (Marc Harter)</p>
+</li>
+<li><p>fs: make callbacks run in global context (Ben Noordhuis)</p>
+</li>
+<li><p>fs: enable fs.realpath on windows (isaacs)</p>
+</li>
+<li><p>child_process: expose UV_PROCESS_DETACHED as options.detached (Charlie McConnell)</p>
+</li>
+<li><p>child_process: new stdio API for .spawn() method (Fedor Indutny)</p>
+</li>
+<li><p>child_process: spawn().ref() and spawn().unref() (Fedor Indutny)</p>
+</li>
+<li><p>Upgrade npm to 1.1.25</p>
+</li>
+<ul><li>Enable npm link on windows</li>
+<li>Properly remove sh-shim on Windows</li>
+<li>Abstract out registry client and logger</li></ul>
+</ul>
+<p>Source Code: <a href="http://nodejs.org/dist/v0.7.10/node-v0.7.10.tar.gz">http://nodejs.org/dist/v0.7.10/node-v0.7.10.tar.gz</a>
+
+</p>
+<p>Windows Installer: <a href="http://nodejs.org/dist/v0.7.10/node-v0.7.10.msi">http://nodejs.org/dist/v0.7.10/node-v0.7.10.msi</a>
+
+</p>
+<p>Windows x64 Files: <a href="http://nodejs.org/dist/v0.7.10/x64/">http://nodejs.org/dist/v0.7.10/x64/</a>
+
+</p>
+<p>Macintosh Installer (Universal): <a href="http://nodejs.org/dist/v0.7.10/node-v0.7.10.pkg">http://nodejs.org/dist/v0.7.10/node-v0.7.10.pkg</a>
+
+</p>
+<p>Other release files: <a href="http://nodejs.org/dist/v0.7.10/">http://nodejs.org/dist/v0.7.10/</a>
+
+</p>
+<p>Website: <a href="http://nodejs.org/docs/v0.7.10/">http://nodejs.org/docs/v0.7.10/</a>
+
+</p>
+<p>Documentation: <a href="http://nodejs.org/docs/v0.7.10/api/">http://nodejs.org/docs/v0.7.10/api/</a>
</p>
category: release
slug: version-0-7-11-unstable
-<p>This is the most stable 0.7 release yet. Please try it out.\r
-\r
-</p>\r
-<p>Version 0.8 will be out very soon. You can follow the remaining issues\r
-on the github issue tracker.\r
-\r
-</p>\r
-<p><a href="https://github.com/joyent/node/issues?milestone=10&state=open">https://github.com/joyent/node/issues?milestone=10&state=open</a>\r
-\r
-</p>\r
-<p>2012.06.15, Version 0.7.11 (unstable)\r
-\r
-</p>\r
-<ul>\r
-<li><p>V8: Upgrade to v3.11.10</p>\r
-</li>\r
-<li><p>npm: Upgrade to 1.1.26</p>\r
-</li>\r
-<li><p>doc: Improve cross-linking in API docs markdown (Ben Kelly)</p>\r
-</li>\r
-<li><p>Fix #3425: removeAllListeners should delete array (Reid Burke)</p>\r
-</li>\r
-<li><p>cluster: don't silently drop messages when the write queue gets big (Bert Belder)</p>\r
-</li>\r
-<li><p>Add Buffer.concat method (isaacs)</p>\r
-</li>\r
-<li><p>windows: make symlinks tolerant to forward slashes (Bert Belder)</p>\r
-</li>\r
-<li><p>build: Add node.d and node.1 to installer (isaacs)</p>\r
-</li>\r
-<li><p>cluster: rename worker.unqiueID to worker.id (Andreas Madsen)</p>\r
-</li>\r
-<li><p>Windows: Enable ETW events on Windows for existing DTrace probes. (Igor Zinkovsky)</p>\r
-</li>\r
-<li><p>test: bundle node-weak in test/gc so that it doesn't need to be downloaded (Nathan Rajlich)</p>\r
-</li>\r
-<li><p>Make many tests pass on Windows (Bert Belder)</p>\r
-</li>\r
-<li><p>Fix #3388 Support listening on file descriptors (isaacs)</p>\r
-</li>\r
-<li><p>Fix #3407 Add os.tmpDir() (isaacs)</p>\r
-</li>\r
-<li><p>Unbreak the snapshotted build on Windows (Bert Belder)</p>\r
-</li>\r
-<li><p>Clean up child_process.kill throws (Bert Belder)</p>\r
-</li>\r
-<li><p>crypto: make cipher/decipher accept buffer args (Ben Noordhuis)</p>\r
-</li>\r
-</ul>\r
-<p>Source Code: <a href="http://nodejs.org/dist/v0.7.11/node-v0.7.11.tar.gz">http://nodejs.org/dist/v0.7.11/node-v0.7.11.tar.gz</a>\r
-\r
-</p>\r
-<p>Macintosh Installer (Universal): <a href="http://nodejs.org/dist/v0.7.11/node-v0.7.11.pkg">http://nodejs.org/dist/v0.7.11/node-v0.7.11.pkg</a>\r
-\r
-</p>\r
-<p>Windows Installer: <a href="http://nodejs.org/dist/v0.7.11/node-v0.7.11-x86.msi">http://nodejs.org/dist/v0.7.11/node-v0.7.11-x86.msi</a>\r
-\r
-</p>\r
-<p>Windows x64 Installer: <a href="http://nodejs.org/dist/v0.7.11/node-v0.7.11-x64.msi">http://nodejs.org/dist/v0.7.11/node-v0.7.11-x64.msi</a>\r
-\r
-</p>\r
-<p>Windows x64 Files: <a href="http://nodejs.org/dist/v0.7.11/x64/">http://nodejs.org/dist/v0.7.11/x64/</a>\r
-\r
-</p>\r
-<p>Other release files: <a href="http://nodejs.org/dist/v0.7.11/">http://nodejs.org/dist/v0.7.11/</a>\r
-\r
-</p>\r
-<p>Website: <a href="http://nodejs.org/docs/v0.7.11/">http://nodejs.org/docs/v0.7.11/</a>\r
-\r
-</p>\r
-<p>Documentation: <a href="http://nodejs.org/docs/v0.7.11/api/">http://nodejs.org/docs/v0.7.11/api/</a>\r
+<p>This is the most stable 0.7 release yet. Please try it out.
+
+</p>
+<p>Version 0.8 will be out very soon. You can follow the remaining issues
+on the github issue tracker.
+
+</p>
+<p><a href="https://github.com/joyent/node/issues?milestone=10&state=open">https://github.com/joyent/node/issues?milestone=10&state=open</a>
+
+</p>
+<p>2012.06.15, Version 0.7.11 (unstable)
+
+</p>
+<ul>
+<li><p>V8: Upgrade to v3.11.10</p>
+</li>
+<li><p>npm: Upgrade to 1.1.26</p>
+</li>
+<li><p>doc: Improve cross-linking in API docs markdown (Ben Kelly)</p>
+</li>
+<li><p>Fix #3425: removeAllListeners should delete array (Reid Burke)</p>
+</li>
+<li><p>cluster: don't silently drop messages when the write queue gets big (Bert Belder)</p>
+</li>
+<li><p>Add Buffer.concat method (isaacs)</p>
+</li>
+<li><p>windows: make symlinks tolerant to forward slashes (Bert Belder)</p>
+</li>
+<li><p>build: Add node.d and node.1 to installer (isaacs)</p>
+</li>
+<li><p>cluster: rename worker.unqiueID to worker.id (Andreas Madsen)</p>
+</li>
+<li><p>Windows: Enable ETW events on Windows for existing DTrace probes. (Igor Zinkovsky)</p>
+</li>
+<li><p>test: bundle node-weak in test/gc so that it doesn't need to be downloaded (Nathan Rajlich)</p>
+</li>
+<li><p>Make many tests pass on Windows (Bert Belder)</p>
+</li>
+<li><p>Fix #3388 Support listening on file descriptors (isaacs)</p>
+</li>
+<li><p>Fix #3407 Add os.tmpDir() (isaacs)</p>
+</li>
+<li><p>Unbreak the snapshotted build on Windows (Bert Belder)</p>
+</li>
+<li><p>Clean up child_process.kill throws (Bert Belder)</p>
+</li>
+<li><p>crypto: make cipher/decipher accept buffer args (Ben Noordhuis)</p>
+</li>
+</ul>
+<p>Source Code: <a href="http://nodejs.org/dist/v0.7.11/node-v0.7.11.tar.gz">http://nodejs.org/dist/v0.7.11/node-v0.7.11.tar.gz</a>
+
+</p>
+<p>Macintosh Installer (Universal): <a href="http://nodejs.org/dist/v0.7.11/node-v0.7.11.pkg">http://nodejs.org/dist/v0.7.11/node-v0.7.11.pkg</a>
+
+</p>
+<p>Windows Installer: <a href="http://nodejs.org/dist/v0.7.11/node-v0.7.11-x86.msi">http://nodejs.org/dist/v0.7.11/node-v0.7.11-x86.msi</a>
+
+</p>
+<p>Windows x64 Installer: <a href="http://nodejs.org/dist/v0.7.11/node-v0.7.11-x64.msi">http://nodejs.org/dist/v0.7.11/node-v0.7.11-x64.msi</a>
+
+</p>
+<p>Windows x64 Files: <a href="http://nodejs.org/dist/v0.7.11/x64/">http://nodejs.org/dist/v0.7.11/x64/</a>
+
+</p>
+<p>Other release files: <a href="http://nodejs.org/dist/v0.7.11/">http://nodejs.org/dist/v0.7.11/</a>
+
+</p>
+<p>Website: <a href="http://nodejs.org/docs/v0.7.11/">http://nodejs.org/docs/v0.7.11/</a>
+
+</p>
+<p>Documentation: <a href="http://nodejs.org/docs/v0.7.11/api/">http://nodejs.org/docs/v0.7.11/api/</a>
</p>
category: release
slug: version-0-7-12
-<p>2012.06.19, Version 0.7.12 (unstable) </p>\r
-<p>This is the last release on the 0.7 branch. Version 0.8.0 will be released some time later this week, barring any major problems. </p>\r
-<p>As with other even-numbered Node releases before it, the v0.8.x releases will maintain API and binary compatibility. </p>\r
-<p>The major changes between v0.6 and v0.8 are detailed in <a href="https://github.com/joyent/node/wiki/API-changes-between-v0.6-and-v0.8">https://github.com/joyent/node/wiki/API-changes-between-v0.6-and-v0.8</a> </p>\r
-<p>Please try out this release. There will be very virtually no changes between this and the v0.8.x release family. This is the last chance to comment before it is locked down for stability. The API is effectively frozen now. </p>\r
-<p>This version adds backwards-compatible shims for binary addons that use libeio and libev directly. If you find that binary modules that could compile on v0.6 can not compile on this version, please let us know. Note that libev is officially deprecated in v0.8, and will be removed in v0.9. You should be porting your modules to use libuv as soon as possible. </p>\r
-<p>V8 is on 3.11.10 currently, and will remain on the V8 3.11.x branch for the duration of Node v0.8.x. </p>\r
-<ul> <li><p>npm: Upgrade to 1.1.30<br> - Improved 'npm init'<br> - Fix the 'cb never called' error from 'oudated' and 'update'<br> - Add --save-bundle|-B config<br> - Fix isaacs/npm#2465: Make npm script and windows shims cygwin-aware<br> - Fix isaacs/npm#2452 Use --save(-dev|-optional) in npm rm<br> - <code>logstream</code> option to replace removed <code>logfd</code> (Rod Vagg)<br> - Read default descriptions from README.md files </p>\r
- </li> <li><p>Shims to support deprecated <code>ev_*</code> and <code>eio_*</code> methods (Ben Noordhuis)</p>\r
- </li> <li><p>#3118 net.Socket: Delay pause/resume until after connect (isaacs)</p>\r
- </li> <li><p>#3465 Add ./configure --no-ifaddrs flag (isaacs)</p>\r
- </li> <li><p>child_process: add .stdin stream to forks (Fedor Indutny)</p>\r
- </li> <li><p>build: fix <code>make install DESTDIR=/path</code> (Ben Noordhuis)</p>\r
- </li> <li><p>tls: fix off-by-one error in renegotiation check (Ben Noordhuis)</p>\r
- </li> <li><p>crypto: Fix diffie-hellman key generation UTF-8 errors (Fedor Indutny)</p>\r
- </li> <li><p>node: change the constructor name of process from EventEmitter to process (Andreas Madsen)</p>\r
- </li> <li><p>net: Prevent property access throws during close (Reid Burke)</p>\r
- </li> <li><p>querystring: improved speed and code cleanup (Felix Böhm)</p>\r
- </li> <li><p>sunos: fix assertion errors breaking fs.watch() (Fedor Indutny)</p>\r
- </li> <li><p>unix: stat: detect sub-second changes (Ben Noordhuis)</p>\r
- </li> <li><p>add stat() based file watcher (Ben Noordhuis)</p>\r
- </li> </ul> <p>Source Code: <a href="http://nodejs.org/dist/v0.7.12/node-v0.7.12.tar.gz">http://nodejs.org/dist/v0.7.12/node-v0.7.12.tar.gz</a> </p>\r
- <p>Macintosh Installer (Universal): <a href="http://nodejs.org/dist/v0.7.12/node-v0.7.12.pkg">http://nodejs.org/dist/v0.7.12/node-v0.7.12.pkg</a> </p>\r
- <p>Windows Installer: <a href="http://nodejs.org/dist/v0.7.12/node-v0.7.12-x86.msi">http://nodejs.org/dist/v0.7.12/node-v0.7.12-x86.msi</a> </p>\r
- <p>Windows x64 Installer: <a href="http://nodejs.org/dist/v0.7.12/x64/node-v0.7.12-x64.msi">http://nodejs.org/dist/v0.7.12/x64/node-v0.7.12-x64.msi</a> </p>\r
- <p>Windows x64 Files: <a href="http://nodejs.org/dist/v0.7.12/x64/">http://nodejs.org/dist/v0.7.12/x64/</a> </p>\r
- <p>Other release files: <a href="http://nodejs.org/dist/v0.7.12/">http://nodejs.org/dist/v0.7.12/</a> </p>\r
- <p>Website: <a href="http://nodejs.org/docs/v0.7.12/">http://nodejs.org/docs/v0.7.12/</a> </p>\r
- <p>Documentation: <a href="http://nodejs.org/docs/v0.7.12/api/">http://nodejs.org/docs/v0.7.12/api/</a> </p>\r
-\r
-<h2>Shasums</h2>\r
-\r
-<pre>ded6a2197b1149b594eb45fea921e8538ba442aa blog.html\r
-dfabff0923d4b4f1d53bd9831514c1ac8c4b1876 email.md\r
-be313d35511e6d7e43cae5fa2b18f3e0d2275ba1 node-v0.7.12-x86.msi\r
-8f7ba0c8283e3863de32fd5c034f5b599c78f830 node-v0.7.12.pkg\r
-cb570abacbf4eb7e23c3d2620d00dd3080d9c19d node-v0.7.12.tar.gz\r
-e13a6edfcba1c67ffe794982dd20a222ce8ce40f node.exe\r
-20906ad76a43eca52795b2a089654a105e11c1e6 node.exp\r
-acbcbb87b6f7f2af34a3ed0abe6131d9e7a237af node.lib\r
-4013d5b25fe36ae4245433b972818686cd9a2205 node.pdb\r
-6c0a7a2e8ee360e2800156293fb2f6a5c1a57382 npm-1.1.30.tgz\r
-9d23e42e8260fa20001d5618d2583a62792bf63f npm-1.1.30.zip\r
-840157b2d6f7389ba70b07fc9ddc048b92c501cc x64/node-v0.7.12-x64.msi\r
-862d42706c21ea83bf73cd827101f0fe598b0cf7 x64/node.exe\r
-de0af95fac083762f99c875f91bab830dc030f71 x64/node.exp\r
-3122bd886dfb96f3b41846cef0bdd7e97326044a x64/node.lib\r
+<p>2012.06.19, Version 0.7.12 (unstable) </p>
+<p>This is the last release on the 0.7 branch. Version 0.8.0 will be released some time later this week, barring any major problems. </p>
+<p>As with other even-numbered Node releases before it, the v0.8.x releases will maintain API and binary compatibility. </p>
+<p>The major changes between v0.6 and v0.8 are detailed in <a href="https://github.com/joyent/node/wiki/API-changes-between-v0.6-and-v0.8">https://github.com/joyent/node/wiki/API-changes-between-v0.6-and-v0.8</a> </p>
+<p>Please try out this release. There will be very virtually no changes between this and the v0.8.x release family. This is the last chance to comment before it is locked down for stability. The API is effectively frozen now. </p>
+<p>This version adds backwards-compatible shims for binary addons that use libeio and libev directly. If you find that binary modules that could compile on v0.6 can not compile on this version, please let us know. Note that libev is officially deprecated in v0.8, and will be removed in v0.9. You should be porting your modules to use libuv as soon as possible. </p>
+<p>V8 is on 3.11.10 currently, and will remain on the V8 3.11.x branch for the duration of Node v0.8.x. </p>
+<ul> <li><p>npm: Upgrade to 1.1.30<br> - Improved 'npm init'<br> - Fix the 'cb never called' error from 'oudated' and 'update'<br> - Add --save-bundle|-B config<br> - Fix isaacs/npm#2465: Make npm script and windows shims cygwin-aware<br> - Fix isaacs/npm#2452 Use --save(-dev|-optional) in npm rm<br> - <code>logstream</code> option to replace removed <code>logfd</code> (Rod Vagg)<br> - Read default descriptions from README.md files </p>
+ </li> <li><p>Shims to support deprecated <code>ev_*</code> and <code>eio_*</code> methods (Ben Noordhuis)</p>
+ </li> <li><p>#3118 net.Socket: Delay pause/resume until after connect (isaacs)</p>
+ </li> <li><p>#3465 Add ./configure --no-ifaddrs flag (isaacs)</p>
+ </li> <li><p>child_process: add .stdin stream to forks (Fedor Indutny)</p>
+ </li> <li><p>build: fix <code>make install DESTDIR=/path</code> (Ben Noordhuis)</p>
+ </li> <li><p>tls: fix off-by-one error in renegotiation check (Ben Noordhuis)</p>
+ </li> <li><p>crypto: Fix diffie-hellman key generation UTF-8 errors (Fedor Indutny)</p>
+ </li> <li><p>node: change the constructor name of process from EventEmitter to process (Andreas Madsen)</p>
+ </li> <li><p>net: Prevent property access throws during close (Reid Burke)</p>
+ </li> <li><p>querystring: improved speed and code cleanup (Felix Böhm)</p>
+ </li> <li><p>sunos: fix assertion errors breaking fs.watch() (Fedor Indutny)</p>
+ </li> <li><p>unix: stat: detect sub-second changes (Ben Noordhuis)</p>
+ </li> <li><p>add stat() based file watcher (Ben Noordhuis)</p>
+ </li> </ul> <p>Source Code: <a href="http://nodejs.org/dist/v0.7.12/node-v0.7.12.tar.gz">http://nodejs.org/dist/v0.7.12/node-v0.7.12.tar.gz</a> </p>
+ <p>Macintosh Installer (Universal): <a href="http://nodejs.org/dist/v0.7.12/node-v0.7.12.pkg">http://nodejs.org/dist/v0.7.12/node-v0.7.12.pkg</a> </p>
+ <p>Windows Installer: <a href="http://nodejs.org/dist/v0.7.12/node-v0.7.12-x86.msi">http://nodejs.org/dist/v0.7.12/node-v0.7.12-x86.msi</a> </p>
+ <p>Windows x64 Installer: <a href="http://nodejs.org/dist/v0.7.12/x64/node-v0.7.12-x64.msi">http://nodejs.org/dist/v0.7.12/x64/node-v0.7.12-x64.msi</a> </p>
+ <p>Windows x64 Files: <a href="http://nodejs.org/dist/v0.7.12/x64/">http://nodejs.org/dist/v0.7.12/x64/</a> </p>
+ <p>Other release files: <a href="http://nodejs.org/dist/v0.7.12/">http://nodejs.org/dist/v0.7.12/</a> </p>
+ <p>Website: <a href="http://nodejs.org/docs/v0.7.12/">http://nodejs.org/docs/v0.7.12/</a> </p>
+ <p>Documentation: <a href="http://nodejs.org/docs/v0.7.12/api/">http://nodejs.org/docs/v0.7.12/api/</a> </p>
+
+<h2>Shasums</h2>
+
+<pre>ded6a2197b1149b594eb45fea921e8538ba442aa blog.html
+dfabff0923d4b4f1d53bd9831514c1ac8c4b1876 email.md
+be313d35511e6d7e43cae5fa2b18f3e0d2275ba1 node-v0.7.12-x86.msi
+8f7ba0c8283e3863de32fd5c034f5b599c78f830 node-v0.7.12.pkg
+cb570abacbf4eb7e23c3d2620d00dd3080d9c19d node-v0.7.12.tar.gz
+e13a6edfcba1c67ffe794982dd20a222ce8ce40f node.exe
+20906ad76a43eca52795b2a089654a105e11c1e6 node.exp
+acbcbb87b6f7f2af34a3ed0abe6131d9e7a237af node.lib
+4013d5b25fe36ae4245433b972818686cd9a2205 node.pdb
+6c0a7a2e8ee360e2800156293fb2f6a5c1a57382 npm-1.1.30.tgz
+9d23e42e8260fa20001d5618d2583a62792bf63f npm-1.1.30.zip
+840157b2d6f7389ba70b07fc9ddc048b92c501cc x64/node-v0.7.12-x64.msi
+862d42706c21ea83bf73cd827101f0fe598b0cf7 x64/node.exe
+de0af95fac083762f99c875f91bab830dc030f71 x64/node.exp
+3122bd886dfb96f3b41846cef0bdd7e97326044a x64/node.lib
e0fa4e42cd19cadf8179e492ca606b7232bbc018 x64/node.pdb</pre>
category: release
slug: version-0-7-4-unstable
-<p>2012.02.14, Version 0.7.4 (unstable)\r
-\r
-</p>\r
-<ul>\r
-<li><p>Upgrade V8 to 3.9.5</p>\r
-</li>\r
-<li><p>Upgrade npm to 1.1.1</p>\r
-</li>\r
-<li><p>build: Detect host_arch better (Karl Skomski)</p>\r
-</li>\r
-<li><p>debugger: export <code>debug_port</code> to <code>process</code> (Fedor Indutny)</p>\r
-</li>\r
-<li><p>api docs: CSS bug fixes (isaacs)</p>\r
-</li>\r
-<li><p>build: use -fPIC for native addons on UNIX (Nathan Rajlich)</p>\r
-</li>\r
-<li><p>Re-add top-level v8::Locker (Marcel Laverdet)</p>\r
-</li>\r
-<li><p>Move images out of the dist tarballs (isaacs)</p>\r
-</li>\r
-<li><p>libuv: Remove uv_export and uv_import (Ben Noordhuis)</p>\r
-</li>\r
-<li><p>build: Support x64 build on Windows (Igor Zinkovsky)</p>\r
-</li>\r
-</ul>\r
-<p>Source Code: <a href="http://nodejs.org/dist/v0.7.4/node-v0.7.4.tar.gz">http://nodejs.org/dist/v0.7.4/node-v0.7.4.tar.gz</a>\r
-\r
-</p>\r
-<p>Windows Installer: <a href="http://nodejs.org/dist/v0.7.4/node-v0.7.4.msi">http://nodejs.org/dist/v0.7.4/node-v0.7.4.msi</a>\r
-\r
-</p>\r
-<p>Macintosh Installer: <a href="http://nodejs.org/dist/v0.7.4/node-v0.7.4.pkg">http://nodejs.org/dist/v0.7.4/node-v0.7.4.pkg</a>\r
-\r
-</p>\r
-<p>Other release files: <a href="http://nodejs.org/dist/v0.7.4/">http://nodejs.org/dist/v0.7.4/</a>\r
-\r
-</p>\r
-<p>Website: <a href="http://nodejs.org/docs/v0.7.4/">http://nodejs.org/docs/v0.7.4/</a>\r
-\r
-</p>\r
-<p>Documentation: <a href="http://nodejs.org/docs/v0.7.4/api/">http://nodejs.org/docs/v0.7.4/api/</a>\r
+<p>2012.02.14, Version 0.7.4 (unstable)
+
+</p>
+<ul>
+<li><p>Upgrade V8 to 3.9.5</p>
+</li>
+<li><p>Upgrade npm to 1.1.1</p>
+</li>
+<li><p>build: Detect host_arch better (Karl Skomski)</p>
+</li>
+<li><p>debugger: export <code>debug_port</code> to <code>process</code> (Fedor Indutny)</p>
+</li>
+<li><p>api docs: CSS bug fixes (isaacs)</p>
+</li>
+<li><p>build: use -fPIC for native addons on UNIX (Nathan Rajlich)</p>
+</li>
+<li><p>Re-add top-level v8::Locker (Marcel Laverdet)</p>
+</li>
+<li><p>Move images out of the dist tarballs (isaacs)</p>
+</li>
+<li><p>libuv: Remove uv_export and uv_import (Ben Noordhuis)</p>
+</li>
+<li><p>build: Support x64 build on Windows (Igor Zinkovsky)</p>
+</li>
+</ul>
+<p>Source Code: <a href="http://nodejs.org/dist/v0.7.4/node-v0.7.4.tar.gz">http://nodejs.org/dist/v0.7.4/node-v0.7.4.tar.gz</a>
+
+</p>
+<p>Windows Installer: <a href="http://nodejs.org/dist/v0.7.4/node-v0.7.4.msi">http://nodejs.org/dist/v0.7.4/node-v0.7.4.msi</a>
+
+</p>
+<p>Macintosh Installer: <a href="http://nodejs.org/dist/v0.7.4/node-v0.7.4.pkg">http://nodejs.org/dist/v0.7.4/node-v0.7.4.pkg</a>
+
+</p>
+<p>Other release files: <a href="http://nodejs.org/dist/v0.7.4/">http://nodejs.org/dist/v0.7.4/</a>
+
+</p>
+<p>Website: <a href="http://nodejs.org/docs/v0.7.4/">http://nodejs.org/docs/v0.7.4/</a>
+
+</p>
+<p>Documentation: <a href="http://nodejs.org/docs/v0.7.4/api/">http://nodejs.org/docs/v0.7.4/api/</a>
</p>
category: release
slug: version-0-7-5-unstable
-<p>2012.02.23, Version 0.7.5 (unstable)\r
-\r
-</p>\r
-<ul>\r
-<li><p>startup speed improvements (Maciej Małecki)</p>\r
-</li>\r
-<li><p>crypto: add function getDiffieHellman() (Tomasz Buchert)</p>\r
-</li>\r
-<li><p>buffer: support decoding of URL-safe base64 (Ben Noordhuis)</p>\r
-</li>\r
-<li><p>Make QueryString.parse() even faster (Brian White)</p>\r
-</li>\r
-<li><p>url: decode url entities in auth section (Ben Noordhuis)</p>\r
-</li>\r
-<li><p>http: support PURGE request method (Ben Noordhuis)</p>\r
-</li>\r
-<li><p>http: Generate Date headers on responses (Mark Nottingham)</p>\r
-</li>\r
-<li><p>Fix #2762: Add callback to close function. (Mikeal Rogers)</p>\r
-</li>\r
-<li><p>dgram: fix out-of-bound memory read (Ben Noordhuis)</p>\r
-</li>\r
-<li><p>repl: add automatic loading of built-in libs (Brandon Benvie)</p>\r
-</li>\r
-<li><p>repl: remove double calls where possible (Fedor Indutny)</p>\r
-</li>\r
-<li><p>Readline improvements. Related: #2737 #2756 (Colton Baker)</p>\r
-</li>\r
-<li><p>build: disable -fomit-frame-pointer on solaris (Dave Pacheco)</p>\r
-</li>\r
-<li><p>build: arch detection improvements (Nathan Rajlich)</p>\r
-</li>\r
-<li><p>build: Make a fat binary for the OS X <code>make pkg</code>. (Nathan Rajlich)</p>\r
-</li>\r
-<li><p>jslint src/ and lib/ on 'make test' (isaacs)</p>\r
-</li>\r
-</ul>\r
-<p>Source Code: <a href="http://nodejs.org/dist/v0.7.5/node-v0.7.5.tar.gz">http://nodejs.org/dist/v0.7.5/node-v0.7.5.tar.gz</a>\r
-\r
-</p>\r
-<p>Windows Installer: <a href="http://nodejs.org/dist/v0.7.5/node-v0.7.5.msi">http://nodejs.org/dist/v0.7.5/node-v0.7.5.msi</a>\r
-\r
-</p>\r
-<p>Macintosh Installer: <a href="http://nodejs.org/dist/v0.7.5/node-v0.7.5.pkg">http://nodejs.org/dist/v0.7.5/node-v0.7.5.pkg</a>\r
-\r
-</p>\r
-<p>Other release files: <a href="http://nodejs.org/dist/v0.7.5/">http://nodejs.org/dist/v0.7.5/</a>\r
-\r
-</p>\r
-<p>Website: <a href="http://nodejs.org/docs/v0.7.5/">http://nodejs.org/docs/v0.7.5/</a>\r
-\r
-</p>\r
-<p>Documentation: <a href="http://nodejs.org/docs/v0.7.5/api/">http://nodejs.org/docs/v0.7.5/api/</a>\r
+<p>2012.02.23, Version 0.7.5 (unstable)
+
+</p>
+<ul>
+<li><p>startup speed improvements (Maciej Małecki)</p>
+</li>
+<li><p>crypto: add function getDiffieHellman() (Tomasz Buchert)</p>
+</li>
+<li><p>buffer: support decoding of URL-safe base64 (Ben Noordhuis)</p>
+</li>
+<li><p>Make QueryString.parse() even faster (Brian White)</p>
+</li>
+<li><p>url: decode url entities in auth section (Ben Noordhuis)</p>
+</li>
+<li><p>http: support PURGE request method (Ben Noordhuis)</p>
+</li>
+<li><p>http: Generate Date headers on responses (Mark Nottingham)</p>
+</li>
+<li><p>Fix #2762: Add callback to close function. (Mikeal Rogers)</p>
+</li>
+<li><p>dgram: fix out-of-bound memory read (Ben Noordhuis)</p>
+</li>
+<li><p>repl: add automatic loading of built-in libs (Brandon Benvie)</p>
+</li>
+<li><p>repl: remove double calls where possible (Fedor Indutny)</p>
+</li>
+<li><p>Readline improvements. Related: #2737 #2756 (Colton Baker)</p>
+</li>
+<li><p>build: disable -fomit-frame-pointer on solaris (Dave Pacheco)</p>
+</li>
+<li><p>build: arch detection improvements (Nathan Rajlich)</p>
+</li>
+<li><p>build: Make a fat binary for the OS X <code>make pkg</code>. (Nathan Rajlich)</p>
+</li>
+<li><p>jslint src/ and lib/ on 'make test' (isaacs)</p>
+</li>
+</ul>
+<p>Source Code: <a href="http://nodejs.org/dist/v0.7.5/node-v0.7.5.tar.gz">http://nodejs.org/dist/v0.7.5/node-v0.7.5.tar.gz</a>
+
+</p>
+<p>Windows Installer: <a href="http://nodejs.org/dist/v0.7.5/node-v0.7.5.msi">http://nodejs.org/dist/v0.7.5/node-v0.7.5.msi</a>
+
+</p>
+<p>Macintosh Installer: <a href="http://nodejs.org/dist/v0.7.5/node-v0.7.5.pkg">http://nodejs.org/dist/v0.7.5/node-v0.7.5.pkg</a>
+
+</p>
+<p>Other release files: <a href="http://nodejs.org/dist/v0.7.5/">http://nodejs.org/dist/v0.7.5/</a>
+
+</p>
+<p>Website: <a href="http://nodejs.org/docs/v0.7.5/">http://nodejs.org/docs/v0.7.5/</a>
+
+</p>
+<p>Documentation: <a href="http://nodejs.org/docs/v0.7.5/api/">http://nodejs.org/docs/v0.7.5/api/</a>
</p>
category: release
slug: version-0-7-6-unstable
-<p>2012.03.13, Version 0.7.6 (unstable)\r
-\r
-</p>\r
-<ul>\r
-<li><p>Upgrade v8 to 3.9.17</p>\r
-</li>\r
-<li><p>Upgrade npm to 1.1.8</p>\r
-<p>\r
-- Add support for os/cpu fields in package.json (Adam Blackburn)<br>\r
-- Automatically node-gyp packages containing a binding.gyp<br>\r
-- Fix failures unpacking in UNC shares<br>\r
-- Never create un-listable directories<br>\r
-- Handle cases where an optionalDependency fails to build<br>\r
-</p>\r
-</li>\r
-<li><p>events: newListener emit correct fn when using 'once' (Roly Fentanes)</p>\r
-</li>\r
-<li><p>url: Ignore empty port component (Łukasz Walukiewicz)</p>\r
-</li>\r
-<li><p>module: replace 'children' array (isaacs)</p>\r
-</li>\r
-<li><p>tls: parse multiple values of a key in ssl certificate (Sambasiva Suda)</p>\r
-</li>\r
-<li><p>cluster: support passing of named pipes (Ben Noordhuis)</p>\r
-</li>\r
-<li><p>Windows: include syscall in fs errors (Bert Belder)</p>\r
-</li>\r
-<li><p>http: #2888 Emit end event only once (Igor Zinkovsky)</p>\r
-</li>\r
-<li><p>readline: add multiline support (Rlidwka)</p>\r
-</li>\r
-<li><p>process: add <code>process.hrtime()</code> (Nathan Rajlich)</p>\r
-</li>\r
-<li><p>net, http, https: add localAddress option (Dmitry Nizovtsev)</p>\r
-</li>\r
-<li><p>addon improvements (Nathan Rajlich)</p>\r
-</li>\r
-<li><p>build improvements (Ben Noordhuis, Sadique Ali, T.C. Hollingsworth, Nathan Rajlich)</p>\r
-</li>\r
-<li><p>add support for "SEARCH" request methods (Nathan Rajlich)</p>\r
-</li>\r
-<li><p>expose the zlib and http_parser version in process.versions (Nathan Rajlich)</p>\r
-</li>\r
-</ul>\r
-<p>Source Code: <a href="http://nodejs.org/dist/v0.7.6/node-v0.7.6.tar.gz">http://nodejs.org/dist/v0.7.6/node-v0.7.6.tar.gz</a>\r
-\r
-</p>\r
-<p>Windows Installer: <a href="http://nodejs.org/dist/v0.7.6/node-v0.7.6.msi">http://nodejs.org/dist/v0.7.6/node-v0.7.6.msi</a>\r
-\r
-</p>\r
-<p>Windows x64 Files: <a href="http://nodejs.org/dist/v0.7.6/x64/">http://nodejs.org/dist/v0.7.6/x64/</a>\r
-\r
-</p>\r
-<p>Macintosh Installer (Universal): <a href="http://nodejs.org/dist/v0.7.6/node-v0.7.6.pkg">http://nodejs.org/dist/v0.7.6/node-v0.7.6.pkg</a>\r
-\r
-</p>\r
-<p>Other release files: <a href="http://nodejs.org/dist/v0.7.6/">http://nodejs.org/dist/v0.7.6/</a>\r
-\r
-</p>\r
-<p>Website: <a href="http://nodejs.org/docs/v0.7.6/">http://nodejs.org/docs/v0.7.6/</a>\r
-\r
-</p>\r
-<p>Documentation: <a href="http://nodejs.org/docs/v0.7.6/api/">http://nodejs.org/docs/v0.7.6/api/</a>\r
+<p>2012.03.13, Version 0.7.6 (unstable)
+
+</p>
+<ul>
+<li><p>Upgrade v8 to 3.9.17</p>
+</li>
+<li><p>Upgrade npm to 1.1.8</p>
+<p>
+- Add support for os/cpu fields in package.json (Adam Blackburn)<br>
+- Automatically node-gyp packages containing a binding.gyp<br>
+- Fix failures unpacking in UNC shares<br>
+- Never create un-listable directories<br>
+- Handle cases where an optionalDependency fails to build<br>
+</p>
+</li>
+<li><p>events: newListener emit correct fn when using 'once' (Roly Fentanes)</p>
+</li>
+<li><p>url: Ignore empty port component (Łukasz Walukiewicz)</p>
+</li>
+<li><p>module: replace 'children' array (isaacs)</p>
+</li>
+<li><p>tls: parse multiple values of a key in ssl certificate (Sambasiva Suda)</p>
+</li>
+<li><p>cluster: support passing of named pipes (Ben Noordhuis)</p>
+</li>
+<li><p>Windows: include syscall in fs errors (Bert Belder)</p>
+</li>
+<li><p>http: #2888 Emit end event only once (Igor Zinkovsky)</p>
+</li>
+<li><p>readline: add multiline support (Rlidwka)</p>
+</li>
+<li><p>process: add <code>process.hrtime()</code> (Nathan Rajlich)</p>
+</li>
+<li><p>net, http, https: add localAddress option (Dmitry Nizovtsev)</p>
+</li>
+<li><p>addon improvements (Nathan Rajlich)</p>
+</li>
+<li><p>build improvements (Ben Noordhuis, Sadique Ali, T.C. Hollingsworth, Nathan Rajlich)</p>
+</li>
+<li><p>add support for "SEARCH" request methods (Nathan Rajlich)</p>
+</li>
+<li><p>expose the zlib and http_parser version in process.versions (Nathan Rajlich)</p>
+</li>
+</ul>
+<p>Source Code: <a href="http://nodejs.org/dist/v0.7.6/node-v0.7.6.tar.gz">http://nodejs.org/dist/v0.7.6/node-v0.7.6.tar.gz</a>
+
+</p>
+<p>Windows Installer: <a href="http://nodejs.org/dist/v0.7.6/node-v0.7.6.msi">http://nodejs.org/dist/v0.7.6/node-v0.7.6.msi</a>
+
+</p>
+<p>Windows x64 Files: <a href="http://nodejs.org/dist/v0.7.6/x64/">http://nodejs.org/dist/v0.7.6/x64/</a>
+
+</p>
+<p>Macintosh Installer (Universal): <a href="http://nodejs.org/dist/v0.7.6/node-v0.7.6.pkg">http://nodejs.org/dist/v0.7.6/node-v0.7.6.pkg</a>
+
+</p>
+<p>Other release files: <a href="http://nodejs.org/dist/v0.7.6/">http://nodejs.org/dist/v0.7.6/</a>
+
+</p>
+<p>Website: <a href="http://nodejs.org/docs/v0.7.6/">http://nodejs.org/docs/v0.7.6/</a>
+
+</p>
+<p>Documentation: <a href="http://nodejs.org/docs/v0.7.6/api/">http://nodejs.org/docs/v0.7.6/api/</a>
</p>
category: release
slug: version-0-7-7-unstable
-<p>2012.03.30, Version 0.7.7 (unstable)\r
-\r
-</p>\r
-<ul>\r
-<li><p>Upgrade V8 to 3.9.24.7</p>\r
-</li>\r
-<li><p>Upgrade npm to 1.1.15</p>\r
-</li>\r
-<li><p>Handle Emoji characters properly (Erik Corry, Bert Belder)</p>\r
-</li>\r
-<li><p>readline: migrate ansi/vt100 logic from tty to readline (Nathan Rajlich)</p>\r
-</li>\r
-<li><p>readline: Fix multiline handling (Alex Kocharin)</p>\r
-</li>\r
-<li><p>add a -i/--interactive flag to force the REPL (Nathan Rajlich)</p>\r
-</li>\r
-<li><p>debugger: add breakOnException command (Fedor Indutny)</p>\r
-</li>\r
-<li><p>cluster: kill workers when master dies (Andreas Madsen)</p>\r
-</li>\r
-<li><p>cluster: add graceful disconnect support (Andreas Madsen)</p>\r
-</li>\r
-<li><p>child_process: Separate 'close' event from 'exit' (Charlie McConnell)</p>\r
-</li>\r
-<li><p>typed arrays: add Uint8ClampedArray (Mikael Bourges-Sevenier)</p>\r
-</li>\r
-<li><p>buffer: Fix byte alignment issues (Ben Noordhuis, Erik Lundin)</p>\r
-</li>\r
-<li><p>tls: fix CryptoStream.setKeepAlive() (Shigeki Ohtsu)</p>\r
-</li>\r
-<li><p>Expose http parse error codes (Felix Geisendörfer)</p>\r
-</li>\r
-<li><p>events: don't delete the listeners array (Ben Noordhuis, Nathan Rajlich)</p>\r
-</li>\r
-<li><p>process: add process.config to view node's ./configure settings (Nathan Rajlich)</p>\r
-</li>\r
-<li><p>process: process.execArgv to see node's arguments (Micheil Smith)</p>\r
-</li>\r
-<li><p>process: fix process.title setter (Ben Noordhuis)</p>\r
-</li>\r
-<li><p>timers: handle negative or non-numeric timeout values (Ben Noordhuis)</p>\r
-</li>\r
-</ul>\r
-<p>Source Code: <a href="http://nodejs.org/dist/v0.7.7/node-v0.7.7.tar.gz">http://nodejs.org/dist/v0.7.7/node-v0.7.7.tar.gz</a>\r
-\r
-</p>\r
-<p>Windows Installer: <a href="http://nodejs.org/dist/v0.7.7/node-v0.7.7.msi">http://nodejs.org/dist/v0.7.7/node-v0.7.7.msi</a>\r
-\r
-</p>\r
-<p>Windows x64 Files: <a href="http://nodejs.org/dist/v0.7.7/x64/">http://nodejs.org/dist/v0.7.7/x64/</a>\r
-\r
-</p>\r
-<p>Macintosh Installer (Universal): <a href="http://nodejs.org/dist/v0.7.7/node-v0.7.7.pkg">http://nodejs.org/dist/v0.7.7/node-v0.7.7.pkg</a>\r
-\r
-</p>\r
-<p>Other release files: <a href="http://nodejs.org/dist/v0.7.7/">http://nodejs.org/dist/v0.7.7/</a>\r
-\r
-</p>\r
-<p>Website: <a href="http://nodejs.org/docs/v0.7.7/">http://nodejs.org/docs/v0.7.7/</a>\r
-\r
-</p>\r
-<p>Documentation: <a href="http://nodejs.org/docs/v0.7.7/api/">http://nodejs.org/docs/v0.7.7/api/</a>\r
+<p>2012.03.30, Version 0.7.7 (unstable)
+
+</p>
+<ul>
+<li><p>Upgrade V8 to 3.9.24.7</p>
+</li>
+<li><p>Upgrade npm to 1.1.15</p>
+</li>
+<li><p>Handle Emoji characters properly (Erik Corry, Bert Belder)</p>
+</li>
+<li><p>readline: migrate ansi/vt100 logic from tty to readline (Nathan Rajlich)</p>
+</li>
+<li><p>readline: Fix multiline handling (Alex Kocharin)</p>
+</li>
+<li><p>add a -i/--interactive flag to force the REPL (Nathan Rajlich)</p>
+</li>
+<li><p>debugger: add breakOnException command (Fedor Indutny)</p>
+</li>
+<li><p>cluster: kill workers when master dies (Andreas Madsen)</p>
+</li>
+<li><p>cluster: add graceful disconnect support (Andreas Madsen)</p>
+</li>
+<li><p>child_process: Separate 'close' event from 'exit' (Charlie McConnell)</p>
+</li>
+<li><p>typed arrays: add Uint8ClampedArray (Mikael Bourges-Sevenier)</p>
+</li>
+<li><p>buffer: Fix byte alignment issues (Ben Noordhuis, Erik Lundin)</p>
+</li>
+<li><p>tls: fix CryptoStream.setKeepAlive() (Shigeki Ohtsu)</p>
+</li>
+<li><p>Expose http parse error codes (Felix Geisendörfer)</p>
+</li>
+<li><p>events: don't delete the listeners array (Ben Noordhuis, Nathan Rajlich)</p>
+</li>
+<li><p>process: add process.config to view node's ./configure settings (Nathan Rajlich)</p>
+</li>
+<li><p>process: process.execArgv to see node's arguments (Micheil Smith)</p>
+</li>
+<li><p>process: fix process.title setter (Ben Noordhuis)</p>
+</li>
+<li><p>timers: handle negative or non-numeric timeout values (Ben Noordhuis)</p>
+</li>
+</ul>
+<p>Source Code: <a href="http://nodejs.org/dist/v0.7.7/node-v0.7.7.tar.gz">http://nodejs.org/dist/v0.7.7/node-v0.7.7.tar.gz</a>
+
+</p>
+<p>Windows Installer: <a href="http://nodejs.org/dist/v0.7.7/node-v0.7.7.msi">http://nodejs.org/dist/v0.7.7/node-v0.7.7.msi</a>
+
+</p>
+<p>Windows x64 Files: <a href="http://nodejs.org/dist/v0.7.7/x64/">http://nodejs.org/dist/v0.7.7/x64/</a>
+
+</p>
+<p>Macintosh Installer (Universal): <a href="http://nodejs.org/dist/v0.7.7/node-v0.7.7.pkg">http://nodejs.org/dist/v0.7.7/node-v0.7.7.pkg</a>
+
+</p>
+<p>Other release files: <a href="http://nodejs.org/dist/v0.7.7/">http://nodejs.org/dist/v0.7.7/</a>
+
+</p>
+<p>Website: <a href="http://nodejs.org/docs/v0.7.7/">http://nodejs.org/docs/v0.7.7/</a>
+
+</p>
+<p>Documentation: <a href="http://nodejs.org/docs/v0.7.7/api/">http://nodejs.org/docs/v0.7.7/api/</a>
</p>
category: release
slug: version-0-7-8-unstable
-<p>2012.04.18, Version 0.7.8, (unstable)\r
-\r
-</p>\r
-<ul>\r
-<li><p>Upgrade V8 to 3.9.24.9</p>\r
-</li>\r
-<li><p>Upgrade OpenSSL to 1.0.0f</p>\r
-</li>\r
-<li><p>Upgrade npm to 1.1.18</p>\r
-</li>\r
-<li><p>Show licenses in Binary installers</p>\r
-</li>\r
-<li><p>Domains (isaacs)</p>\r
-</li>\r
-<li><p>readline: rename "end" to "close" (Nathan Rajlich)</p>\r
-</li>\r
-<li><p>tcp: make getsockname() return address family as string (Shigeki Ohtsu)</p>\r
-</li>\r
-<li><p>http, https: fix .setTimeout() (ssuda)</p>\r
-</li>\r
-<li><p>os: add cross platform EOL character (Mustansir Golawala)</p>\r
-</li>\r
-<li><p>typed arrays: unexport SizeOfArrayElementForType() (Aaron Jacobs)</p>\r
-</li>\r
-<li><p>net: honor 'enable' flag in .setNoDelay() (Ben Noordhuis)</p>\r
-</li>\r
-<li><p>child_process: emit error when .kill fails (Andreas Madsen)</p>\r
-</li>\r
-<li><p>gyp: fix 'argument list too long' build error (Ben Noordhuis)</p>\r
-</li>\r
-<li><p>fs.WriteStream: Handle modifications to fs.open (isaacs)</p>\r
-</li>\r
-<li><p>repl, readline: Handle newlines better (Nathan Rajlich, Nathan Friedly)</p>\r
-</li>\r
-<li><p>build: target OSX 10.5 when building on darwin (Nathan Rajlich)</p>\r
-</li>\r
-<li><p>Fix #3052 Handle errors properly in zlib (isaacs)</p>\r
-</li>\r
-<li><p>build: add support for DTrace and postmortem (Dave Pacheco)</p>\r
-</li>\r
-<li><p>core: add reusable Slab allocator (Ben Noordhuis)</p>\r
-</li>\r
-</ul>\r
-<p>Source Code: <a href="http://nodejs.org/dist/v0.7.8/node-v0.7.8.tar.gz">http://nodejs.org/dist/v0.7.8/node-v0.7.8.tar.gz</a>\r
-\r
-</p>\r
-<p>Windows Installer: <a href="http://nodejs.org/dist/v0.7.8/node-v0.7.8.msi">http://nodejs.org/dist/v0.7.8/node-v0.7.8.msi</a>\r
-\r
-</p>\r
-<p>Windows x64 Files: <a href="http://nodejs.org/dist/v0.7.8/x64/">http://nodejs.org/dist/v0.7.8/x64/</a>\r
-\r
-</p>\r
-<p>Macintosh Installer (Universal): <a href="http://nodejs.org/dist/v0.7.8/node-v0.7.8.pkg">http://nodejs.org/dist/v0.7.8/node-v0.7.8.pkg</a>\r
-\r
-</p>\r
-<p>Other release files: <a href="http://nodejs.org/dist/v0.7.8/">http://nodejs.org/dist/v0.7.8/</a>\r
-\r
-</p>\r
-<p>Website: <a href="http://nodejs.org/docs/v0.7.8/">http://nodejs.org/docs/v0.7.8/</a>\r
-\r
-</p>\r
-<p>Documentation: <a href="http://nodejs.org/docs/v0.7.8/api/">http://nodejs.org/docs/v0.7.8/api/</a>\r
+<p>2012.04.18, Version 0.7.8, (unstable)
+
+</p>
+<ul>
+<li><p>Upgrade V8 to 3.9.24.9</p>
+</li>
+<li><p>Upgrade OpenSSL to 1.0.0f</p>
+</li>
+<li><p>Upgrade npm to 1.1.18</p>
+</li>
+<li><p>Show licenses in Binary installers</p>
+</li>
+<li><p>Domains (isaacs)</p>
+</li>
+<li><p>readline: rename "end" to "close" (Nathan Rajlich)</p>
+</li>
+<li><p>tcp: make getsockname() return address family as string (Shigeki Ohtsu)</p>
+</li>
+<li><p>http, https: fix .setTimeout() (ssuda)</p>
+</li>
+<li><p>os: add cross platform EOL character (Mustansir Golawala)</p>
+</li>
+<li><p>typed arrays: unexport SizeOfArrayElementForType() (Aaron Jacobs)</p>
+</li>
+<li><p>net: honor 'enable' flag in .setNoDelay() (Ben Noordhuis)</p>
+</li>
+<li><p>child_process: emit error when .kill fails (Andreas Madsen)</p>
+</li>
+<li><p>gyp: fix 'argument list too long' build error (Ben Noordhuis)</p>
+</li>
+<li><p>fs.WriteStream: Handle modifications to fs.open (isaacs)</p>
+</li>
+<li><p>repl, readline: Handle newlines better (Nathan Rajlich, Nathan Friedly)</p>
+</li>
+<li><p>build: target OSX 10.5 when building on darwin (Nathan Rajlich)</p>
+</li>
+<li><p>Fix #3052 Handle errors properly in zlib (isaacs)</p>
+</li>
+<li><p>build: add support for DTrace and postmortem (Dave Pacheco)</p>
+</li>
+<li><p>core: add reusable Slab allocator (Ben Noordhuis)</p>
+</li>
+</ul>
+<p>Source Code: <a href="http://nodejs.org/dist/v0.7.8/node-v0.7.8.tar.gz">http://nodejs.org/dist/v0.7.8/node-v0.7.8.tar.gz</a>
+
+</p>
+<p>Windows Installer: <a href="http://nodejs.org/dist/v0.7.8/node-v0.7.8.msi">http://nodejs.org/dist/v0.7.8/node-v0.7.8.msi</a>
+
+</p>
+<p>Windows x64 Files: <a href="http://nodejs.org/dist/v0.7.8/x64/">http://nodejs.org/dist/v0.7.8/x64/</a>
+
+</p>
+<p>Macintosh Installer (Universal): <a href="http://nodejs.org/dist/v0.7.8/node-v0.7.8.pkg">http://nodejs.org/dist/v0.7.8/node-v0.7.8.pkg</a>
+
+</p>
+<p>Other release files: <a href="http://nodejs.org/dist/v0.7.8/">http://nodejs.org/dist/v0.7.8/</a>
+
+</p>
+<p>Website: <a href="http://nodejs.org/docs/v0.7.8/">http://nodejs.org/docs/v0.7.8/</a>
+
+</p>
+<p>Documentation: <a href="http://nodejs.org/docs/v0.7.8/api/">http://nodejs.org/docs/v0.7.8/api/</a>
</p>
category: video
slug: bryan-cantrill-instrumenting-the-real-time-web
-Bryan Cantrill, VP of Engineering at Joyent, describes the challenges of instrumenting a distributed, dynamic, highly virtualized system -- and what their experiences taught them about the problem, the technologies used to tackle it, and promising approaches.\r
-\r
-This talk was given at Velocity Conf in 2011.\r
-\r
-<table><tr><td align="center">\r
+Bryan Cantrill, VP of Engineering at Joyent, describes the challenges of instrumenting a distributed, dynamic, highly virtualized system -- and what their experiences taught them about the problem, the technologies used to tackle it, and promising approaches.
+
+This talk was given at Velocity Conf in 2011.
+
+<table><tr><td align="center">
<iframe width="640" height="360"
src="http://www.youtube.com/embed/F5jCXdTYJYc" frameborder="0"
-allowfullscreen></iframe>\r
-\r
+allowfullscreen></iframe>
+
<div style="width:425px" id="__ss_8332407">
<strong style="display:block;margin:12px 0 4px"><a href=
"http://www.slideshare.net/bcantrill/instrumenting-the-realtime-web"
category: vulnerability
slug: http-server-security-vulnerability-please-upgrade-to-0-6-17
-<h2>tl;dr</h2>\r
-\r
-<ul><li><p>A carefully crafted attack request can cause the contents of the HTTP parser's buffer to be appended to the attacking request's header, making it appear to come from the attacker. Since it is generally safe to echo back contents of a request, this can allow an attacker to get an otherwise correctly designed server to divulge information about other requests. It is theoretically possible that it could enable header-spoofing attacks, though such an attack has not been demonstrated.</li>\r
-<li>Versions affected: All versions of the 0.5/0.6 branch prior to 0.6.17, and all versions of the 0.7 branch prior to 0.7.8. Versions in the 0.4 branch are not affected.</li>\r
-<li>Fix: Upgrade to <a href="http://blog.nodejs.org/2012/05/04/version-0-6-17-stable/">v0.6.17</a>, or apply the fix in <a href="https://github.com/joyent/node/commit/c9a231d">c9a231d</a> to your system.</li></ul>\r
-\r
-<h2>Details</h2>\r
-\r
-<p>A few weeks ago, Matthew Daley found a security vulnerability in Node's HTTP implementation, and thankfully did the responsible thing and reported it to us via email. He explained it quite well, so I'll quote him here:</p>\r
-<blockquote>\r
-<p>There is a vulnerability in node's `http_parser` binding which allows information disclosure to a remote attacker:\r
-\r
-</p>\r
-<p>In node::StringPtr::Update, an attempt is made at an optimization on certain inputs (`node_http_parser.cc`, line 151). The intent is that if the current string pointer plus the current string size is equal to the incoming string pointer, the current string size is just increased to match, as the incoming string lies just beyond the current string pointer. However, the check to see whether or not this can be done is incorrect; "size" is used whereas "size_" should be used. Therefore, an attacker can call Update with a string of certain length and cause the current string to have other data appended to it. In the case of HTTP being parsed out of incoming socket data, this can be incoming data from other sockets.\r
-\r
-</p>\r
-<p>Normally node::StringPtr::Save, which is called after each execution of `http_parser`, would stop this from being exploitable as it converts strings to non-optimizable heap-based strings. However, this is not done to 0-length strings. An attacker can therefore exploit the mistake by making Update set a 0-length string, and then Update past its boundary, so long as it is done in one `http_parser` execution. This can be done with an HTTP header with empty value, followed by a continuation with a value of certain length.\r
-\r
-</p>\r
-<p>The <a href="https://gist.github.com/2628868">attached files</a> demonstrate the issue: </p>\r
-<pre><code>$ ./node ~/stringptr-update-poc-server.js &\r
-[1] 11801\r
-$ ~/stringptr-update-poc-client.py\r
-HTTP/1.1 200 OK\r
-Content-Type: text/plain\r
-Date: Wed, 18 Apr 2012 00:05:11 GMT\r
-Connection: close\r
-Transfer-Encoding: chunked\r
-\r
-64\r
-X header:\r
- This is private data, perhaps an HTTP request with a Cookie in it.\r
-0</code></pre>\r
-</blockquote>\r
-<p>The fix landed on <a href="https://github.com/joyent/node/commit/7b3fb22">7b3fb22</a> and <a href="https://github.com/joyent/node/commit/c9a231d">c9a231d</a>, for master and v0.6, respectively. The innocuous commit message does not give away the security implications, precisely because we wanted to get a fix out before making a big deal about it. </p>\r
-<p>The first releases with the fix are v0.7.8 and 0.6.17. So now is a good time to make a big deal about it. </p>\r
-<p>If you are using node version 0.6 in production, please upgrade to at least <a href="http://blog.nodejs.org/2012/05/04/version-0-6-17-stable/">v0.6.17</a>, or at least apply the fix in <a href="https://github.com/joyent/node/commit/c9a231d">c9a231d</a> to your system. (Version 0.6.17 also fixes some other important bugs, and is without doubt the most stable release of Node 0.6 to date, so it's a good idea to upgrade anyway.) </p>\r
+<h2>tl;dr</h2>
+
+<ul><li><p>A carefully crafted attack request can cause the contents of the HTTP parser's buffer to be appended to the attacking request's header, making it appear to come from the attacker. Since it is generally safe to echo back contents of a request, this can allow an attacker to get an otherwise correctly designed server to divulge information about other requests. It is theoretically possible that it could enable header-spoofing attacks, though such an attack has not been demonstrated.</li>
+<li>Versions affected: All versions of the 0.5/0.6 branch prior to 0.6.17, and all versions of the 0.7 branch prior to 0.7.8. Versions in the 0.4 branch are not affected.</li>
+<li>Fix: Upgrade to <a href="http://blog.nodejs.org/2012/05/04/version-0-6-17-stable/">v0.6.17</a>, or apply the fix in <a href="https://github.com/joyent/node/commit/c9a231d">c9a231d</a> to your system.</li></ul>
+
+<h2>Details</h2>
+
+<p>A few weeks ago, Matthew Daley found a security vulnerability in Node's HTTP implementation, and thankfully did the responsible thing and reported it to us via email. He explained it quite well, so I'll quote him here:</p>
+<blockquote>
+<p>There is a vulnerability in node's `http_parser` binding which allows information disclosure to a remote attacker:
+
+</p>
+<p>In node::StringPtr::Update, an attempt is made at an optimization on certain inputs (`node_http_parser.cc`, line 151). The intent is that if the current string pointer plus the current string size is equal to the incoming string pointer, the current string size is just increased to match, as the incoming string lies just beyond the current string pointer. However, the check to see whether or not this can be done is incorrect; "size" is used whereas "size_" should be used. Therefore, an attacker can call Update with a string of certain length and cause the current string to have other data appended to it. In the case of HTTP being parsed out of incoming socket data, this can be incoming data from other sockets.
+
+</p>
+<p>Normally node::StringPtr::Save, which is called after each execution of `http_parser`, would stop this from being exploitable as it converts strings to non-optimizable heap-based strings. However, this is not done to 0-length strings. An attacker can therefore exploit the mistake by making Update set a 0-length string, and then Update past its boundary, so long as it is done in one `http_parser` execution. This can be done with an HTTP header with empty value, followed by a continuation with a value of certain length.
+
+</p>
+<p>The <a href="https://gist.github.com/2628868">attached files</a> demonstrate the issue: </p>
+<pre><code>$ ./node ~/stringptr-update-poc-server.js &
+[1] 11801
+$ ~/stringptr-update-poc-client.py
+HTTP/1.1 200 OK
+Content-Type: text/plain
+Date: Wed, 18 Apr 2012 00:05:11 GMT
+Connection: close
+Transfer-Encoding: chunked
+
+64
+X header:
+ This is private data, perhaps an HTTP request with a Cookie in it.
+0</code></pre>
+</blockquote>
+<p>The fix landed on <a href="https://github.com/joyent/node/commit/7b3fb22">7b3fb22</a> and <a href="https://github.com/joyent/node/commit/c9a231d">c9a231d</a>, for master and v0.6, respectively. The innocuous commit message does not give away the security implications, precisely because we wanted to get a fix out before making a big deal about it. </p>
+<p>The first releases with the fix are v0.7.8 and 0.6.17. So now is a good time to make a big deal about it. </p>
+<p>If you are using node version 0.6 in production, please upgrade to at least <a href="http://blog.nodejs.org/2012/05/04/version-0-6-17-stable/">v0.6.17</a>, or at least apply the fix in <a href="https://github.com/joyent/node/commit/c9a231d">c9a231d</a> to your system. (Version 0.6.17 also fixes some other important bugs, and is without doubt the most stable release of Node 0.6 to date, so it's a good idea to upgrade anyway.) </p>
<p>I'm extremely grateful that Matthew took the time to report the problem to us with such an elegant explanation, and in such a way that we had a reasonable amount of time to fix the issue before making it public. </p>
projects / platform / upstream / nodejs.git / commitdiff