From 90efdb3a5b7eecb23d78cffee24c3181280efa56 Mon Sep 17 00:00:00 2001
From: Adam Malcontenti-Wilson 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. Running a seaport 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. fleet 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. To start using fleet, just install the fleet command with npm: Then on one of your servers, start a fleet hub. From a fresh directory, give it a passphrase and a port to listen on: 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! 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: where x.x.x.x is the address where the fleet hub is running. Spin up a few of these drones. Now navigate to the directory of the app you want to deploy. First set a remote so you don't need to type --hub and --secret all the time. Fleet just created a fleet.json file for you to save your settings. From the same app directory, to deploy your code just do: The deploy command does a git push 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. 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 fleet spawn command: 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 --drone switch if it matters. Start a few processes across all your worker drones and then show what is running with the fleet ps command: 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 fleet deploy again after checking in some new changes to git, the next time you fleet spawn 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 fleet stop. 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 http proxy! Even better, if you use a service registry like seaport 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. Fleet has many more commands that you can learn about with its git-style manpage-based help system! Just do fleet help to get a list of all the commands you can run. npm install -g fleet and check out the code on github! 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. Running a seaport 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. fleet 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. To start using fleet, just install the fleet command with npm: Then on one of your servers, start a fleet hub. From a fresh directory, give it a passphrase and a port to listen on: 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! 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: where x.x.x.x is the address where the fleet hub is running. Spin up a few of these drones. Now navigate to the directory of the app you want to deploy. First set a remote so you don't need to type --hub and --secret all the time. Fleet just created a fleet.json file for you to save your settings. From the same app directory, to deploy your code just do: The deploy command does a git push 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. 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 fleet spawn command: 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 --drone switch if it matters. Start a few processes across all your worker drones and then show what is running with the fleet ps command: 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 fleet deploy again after checking in some new changes to git, the next time you fleet spawn 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 fleet stop. 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 http proxy! Even better, if you use a service registry like seaport 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. Fleet has many more commands that you can learn about with its git-style manpage-based help system! Just do fleet help to get a list of all the commands you can run. npm install -g fleet and check out the code on github! 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. "Log. (Huh) What is it good for. Absolutely ..." 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 "printf-style" logs 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. Let's log in JSON. Let's format log records with a filter outside 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 definitely be improved. Let's not 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. At Joyent 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 SmartDataCenter product and observations of Joyent Cloud operations to suggest some improvements to service logging. I'll show the (open source) Bunyan logging library and tool that we're developing to improve the logging toolchain. What're we doing here? Five logs at random. Five different date formats. As Paul Querna points out 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. The current state of the art is various parsing libs, analysis tools and homebrew scripts ranging from grep to Perl, whose scope is limited to a few niches log formats. 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 But not handy enough. That 80's pastel jumpsuit awkwardness you're feeling isn't the JSON, it's your tools. Time to find a 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. Bunyan is a node.js module for logging in JSON and a Logging with Bunyan basically looks like this: And you'll get a log record like this: Pipe that through the Bunyan is log4j-like: create a Logger with a name, call 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 restify library -- which we used heavily here at Joyent. (Bunyan doesn't require restify at all, you can easily use Bunyan with Express or whatever.) You can follow along in https://github.com/trentm/hello-json-logging 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. Our server first creates a Bunyan logger: Every Bunyan logger must have a name. Unlike log4j, this is not a hierarchical dotted namespace. It is just a name field for the log records. Every Bunyan logger has one or more streams, 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'. Bunyan has the concept of serializers: 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 Restify 1.x and above has bunyan support baked in. You pass in your Bunyan logger like this: Our simple API will have a single If we run that, Let's add two things to our server. First, we'll use the This is the first time we've seen this Here we pass in the restify Request object, Remember that we already had this debug log statement in our endpoint handler: Second, use the restify server Now lets see what log output we get when somebody hits our API's endpoint: Here is the server log: Lets look at each in turn to see what is interesting -- pretty-printed with Here we logged the incoming request with Next the and the log of response in the "after" event: Two useful details of note here: The last two log messages include a "req_id" field (added to the 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. The last two log messages include a "route" field. 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. 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 my "hello.log" for an example. The This is logging you can use effectively. Bunyan is just one of many options for logging in node.js-land. Others (that I know of) supporting JSON logging are winston and logmagic. Paul Querna has an excellent post on using JSON for logging, which shows logmagic usage and also touches on topics like the GELF logging format, log transporting, indexing and searching. 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. 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. 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 statsd, records with a "loggly: true" could feed to loggly.com. 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. 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. "Log. (Huh) What is it good for. Absolutely ..." 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 "printf-style" logs 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. Let's log in JSON. Let's format log records with a filter outside 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 definitely be improved. Let's not 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. At Joyent 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 SmartDataCenter product and observations of Joyent Cloud operations to suggest some improvements to service logging. I'll show the (open source) Bunyan logging library and tool that we're developing to improve the logging toolchain. What're we doing here? Five logs at random. Five different date formats. As Paul Querna points out 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. The current state of the art is various parsing libs, analysis tools and homebrew scripts ranging from grep to Perl, whose scope is limited to a few niches log formats. 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 But not handy enough. That 80's pastel jumpsuit awkwardness you're feeling isn't the JSON, it's your tools. Time to find a 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. Bunyan is a node.js module for logging in JSON and a Logging with Bunyan basically looks like this: And you'll get a log record like this: Pipe that through the Bunyan is log4j-like: create a Logger with a name, call 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 restify library -- which we used heavily here at Joyent. (Bunyan doesn't require restify at all, you can easily use Bunyan with Express or whatever.) You can follow along in https://github.com/trentm/hello-json-logging 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. Our server first creates a Bunyan logger: Every Bunyan logger must have a name. Unlike log4j, this is not a hierarchical dotted namespace. It is just a name field for the log records. Every Bunyan logger has one or more streams, 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'. Bunyan has the concept of serializers: 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 Restify 1.x and above has bunyan support baked in. You pass in your Bunyan logger like this: Our simple API will have a single If we run that, Let's add two things to our server. First, we'll use the This is the first time we've seen this Here we pass in the restify Request object, Remember that we already had this debug log statement in our endpoint handler: Second, use the restify server Now lets see what log output we get when somebody hits our API's endpoint: Here is the server log: Lets look at each in turn to see what is interesting -- pretty-printed with Here we logged the incoming request with Next the and the log of response in the "after" event: Two useful details of note here: The last two log messages include a "req_id" field (added to the 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. The last two log messages include a "route" field. 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. 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 my "hello.log" for an example. The This is logging you can use effectively. Bunyan is just one of many options for logging in node.js-land. Others (that I know of) supporting JSON logging are winston and logmagic. Paul Querna has an excellent post on using JSON for logging, which shows logmagic usage and also touches on topics like the GELF logging format, log transporting, indexing and searching. 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. 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. 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 statsd, records with a "loggly: true" could feed to loggly.com. 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. Update (29-Mar-2012): Fix styles somewhat for RSS readers. Managing dependencies is a fundamental problem in building complex software. The terrific success of github and npm 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 semantic versioning, 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.
-
- 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.
-
- Put differently, 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. 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.
-
- 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?
-
- That brings us to npm shrinkwrap[1]:
-
- Let's consider package A:
-
- package B:
-
- and package C:
-
- If these are the only versions of A, B, and C available in the registry, then a normal "npm install A" will install:
-
- Then if B@0.0.2 is published, then a fresh "npm install A" will install:
-
- 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.
-
- In this case, A's author can use
-
- This generates npm-shrinkwrap.json, which will look something like this:
-
- The shrinkwrap command has locked down the dependencies based on what's currently installed in node_modules. 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). 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.
-
- 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.
-
- To shrinkwrap an existing package:
-
- To add or update a dependency in a shrinkwrapped package:
-
- You can still use npm outdated(1) to view which dependencies have newer versions available.
-
- For more details, check out the full docs on npm shrinkwrap, from which much of the above is taken.
-
- One previously proposed solution 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.[2] At best, this is second-class treatment for binary modules, which are critical for many important types of Node applications.[3]
-
- 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.[4] Instead, you check in the original sources and automate the transformations via the build process.
-
- 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?
-
- 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 separation of concerns: each repo specifies what it needs, while the build process figures out where to get it.
-
- 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.
-
- 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.
-
- 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.
-
- 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 logging and REST) and tools for understanding production failures post mortem, profile Node apps in production, and now managing Node dependencies. Again, we're interested to hear feedback from others using these tools.
-
- [1] Much of this section is taken directly from the "npm shrinkwrap" documentation.
-
- [2] We've had a lot of trouble with checking in node_modules with binary dependencies. The first problem is figuring out exactly which files not to check in (.o, .node, .dynlib, .so, *.a, ...). When Mark 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 ldapjs 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.
-
- [3] Like a good Node-based distributed system, our architecture uses lots of small HTTP servers. Each of these serves a REST API using restify. restify uses the binary module node-dtrace-provider, which gives each of our services deep DTrace-based observability for free. So literally almost all of our components are or will soon be depending on a binary add-on. Additionally, the foundation of Cloud Analytics are a pair of binary modules that extract data from DTrace and kstat. So this isn't a corner case for us, and we don't believe we're exceptional in this regard. The popular hiredis package for interfacing with redis from Node is also a binary module.
-
- Managing dependencies is a fundamental problem in building complex software. The terrific success of github and npm 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 semantic versioning, 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.
+
+ 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.
+
+ Put differently, 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. 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.
+
+ 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?
+
+ That brings us to npm shrinkwrap[1]:
+
+ Let's consider package A:
+
+ package B:
+
+ and package C:
+
+ If these are the only versions of A, B, and C available in the registry, then a normal "npm install A" will install:
+
+ Then if B@0.0.2 is published, then a fresh "npm install A" will install:
+
+ 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.
+
+ In this case, A's author can use
+
+ This generates npm-shrinkwrap.json, which will look something like this:
+
+ The shrinkwrap command has locked down the dependencies based on what's currently installed in node_modules. 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). 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.
+
+ 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.
+
+ To shrinkwrap an existing package:
+
+ To add or update a dependency in a shrinkwrapped package:
+
+ You can still use npm outdated(1) to view which dependencies have newer versions available.
+
+ For more details, check out the full docs on npm shrinkwrap, from which much of the above is taken.
+
+ One previously proposed solution 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.[2] At best, this is second-class treatment for binary modules, which are critical for many important types of Node applications.[3]
+
+ 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.[4] Instead, you check in the original sources and automate the transformations via the build process.
+
+ 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?
+
+ 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 separation of concerns: each repo specifies what it needs, while the build process figures out where to get it.
+
+ 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.
+
+ 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.
+
+ 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.
+
+ 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 logging and REST) and tools for understanding production failures post mortem, profile Node apps in production, and now managing Node dependencies. Again, we're interested to hear feedback from others using these tools.
+
+ [1] Much of this section is taken directly from the "npm shrinkwrap" documentation.
+
+ [2] We've had a lot of trouble with checking in node_modules with binary dependencies. The first problem is figuring out exactly which files not to check in (.o, .node, .dynlib, .so, *.a, ...). When Mark 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 ldapjs 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.
+
+ [3] Like a good Node-based distributed system, our architecture uses lots of small HTTP servers. Each of these serves a REST API using restify. restify uses the binary module node-dtrace-provider, which gives each of our services deep DTrace-based observability for free. So literally almost all of our components are or will soon be depending on a binary add-on. Additionally, the foundation of Cloud Analytics are a pair of binary modules that extract data from DTrace and kstat. So this isn't a corner case for us, and we don't believe we're exceptional in this regard. The popular hiredis package for interfacing with redis from Node is also a binary module.
+
+ [4] Note that I said this is an important principle for software version control, 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. npm 1.0 is in release candidate mode. Go get it! 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. In npm 0.x, there was a command called Also, there was that activation/deactivation thing. That’s confusing. In npm 1.0, there are two ways to install things: Whether to install a package globally or locally depends on the 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. In general, the rule of thumb is: Of course, there are some cases where you want to do both. Coffee-script and Express 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: 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 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. Let’s say you do something like this: In this case, npm will install If your package's npm 1.0 is in release candidate mode. Go get it! 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. In npm 0.x, there was a command called Also, there was that activation/deactivation thing. That’s confusing. In npm 1.0, there are two ways to install things: Whether to install a package globally or locally depends on the 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. In general, the rule of thumb is: Of course, there are some cases where you want to do both. Coffee-script and Express 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: 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 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. Let’s say you do something like this: In this case, npm will install If your package's npm 1.0 is in release candidate mode. Go get it! In npm 0.x, there was a command called 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. In npm 0.x, this was a pretty awful kludge. Back then, every package existed in some folder like: and the package’s version and name could be inferred from the path. Then, symbolic links were set up that looked like: It was easy enough to point that symlink to a different location. However, since the package.json file could change, that meant that the connection between the version and the folder was not reliable. 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. 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: And, in both cases, changes should be immediately apparent and not require any re-linking. Also, there’s a third use case that I didn’t really appreciate until I started writing more programs that had more dependencies: 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. Really, the second case above is a special-case of this third case. The first step is to link your local project into the global install space. (See global vs local installation for more on this global/local business.) I do this as I’m developing node projects (including npm itself). Because of how I have my computer set up, with Of course, if you set your paths differently, then you’ll have different results. (That’s why I tend to talk in terms of When you want to link the globally-installed package into your local development folder, you run For example, let’s say that I wanted to write some tap tests for my node-glob package. I’d first do the steps above to link tap into the global install space, and then I’d do this: Now when I make changes in 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. npm link is a development tool. It’s awesome 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. 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. 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. 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 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.) 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. 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?” 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…” “Dude. Either you do it, or I’m going to have to do it, and then there’ll be another package manager in node, instead of writing a registry for npm, and it won’t be as good anyway. Don’t be python.” npm 1.0 is in release candidate mode. Go get it! In npm 0.x, there was a command called 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. In npm 0.x, this was a pretty awful kludge. Back then, every package existed in some folder like: and the package’s version and name could be inferred from the path. Then, symbolic links were set up that looked like: It was easy enough to point that symlink to a different location. However, since the package.json file could change, that meant that the connection between the version and the folder was not reliable. 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. 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: And, in both cases, changes should be immediately apparent and not require any re-linking. Also, there’s a third use case that I didn’t really appreciate until I started writing more programs that had more dependencies: 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. Really, the second case above is a special-case of this third case. The first step is to link your local project into the global install space. (See global vs local installation for more on this global/local business.) I do this as I’m developing node projects (including npm itself). Because of how I have my computer set up, with Of course, if you set your paths differently, then you’ll have different results. (That’s why I tend to talk in terms of When you want to link the globally-installed package into your local development folder, you run For example, let’s say that I wanted to write some tap tests for my node-glob package. I’d first do the steps above to link tap into the global install space, and then I’d do this: Now when I make changes in 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. npm link is a development tool. It’s awesome 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. 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. 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. 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 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.) 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. 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?” 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…” “Dude. Either you do it, or I’m going to have to do it, and then there’ll be another package manager in node, instead of writing a registry for npm, and it won’t be as good anyway. Don’t be python.” The rest is history. npm 1.0 has been released. Here are the highlights: The focus is on npm being a development tool, rather than an apt-wannabe. To get the new version, run this command: 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: Or, if you want to not do the cleanup, and leave the old stuff behind, then do this: 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 :) npm will not have any major feature enhancements or architectural changes for at least 6 months. 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. Of course, bug reports are always welcome. npm 1.0 has been released. Here are the highlights: The focus is on npm being a development tool, rather than an apt-wannabe. To get the new version, run this command: 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: Or, if you want to not do the cleanup, and leave the old stuff behind, then do this: 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 :) npm will not have any major feature enhancements or architectural changes for at least 6 months. 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. Of course, bug reports are always welcome. See you at NodeConf! This is the first in a series of hopefully more than 1 posts, each detailing some aspect of npm 1.0. In npm 0.x, the As the registry has grown in size, this has gotten unwieldy. Also, since npm 1.0 manages dependencies differently, nesting them in The functionality of the Here’s an example of the output: This is after I’ve done Let’s see what happens when we create a broken situation: 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: Since you sometimes want a bigger view, I added the And, if you want to get at the globally-installed modules, you can use ls with the global flag: This is the first in a series of hopefully more than 1 posts, each detailing some aspect of npm 1.0. In npm 0.x, the As the registry has grown in size, this has gotten unwieldy. Also, since npm 1.0 manages dependencies differently, nesting them in The functionality of the Here’s an example of the output: This is after I’ve done Let’s see what happens when we create a broken situation: 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: Since you sometimes want a bigger view, I added the And, if you want to get at the globally-installed modules, you can use ls with the global flag: Those 2011.08.26, Version 0.5.5 (unstable)
-
-
-You'll be looking at something like this:
-
-
-$ dtrace -o stacks.out -n 'profile-97/execname == "node" && arg1/{
- @[jstack(100, 8000)] = count(); } tick-60s { exit(0); }'
- This will sample about 100 times per second for 60 seconds and emit results to stacks.out. Note that this will sample all running programs called "node". If you want a specific process, replace execname == "node" with pid == 12345 (the process id).
- $ npm install -g stackvis
- then use stackvis to convert the DTrace output to a flamegraph:
- $ stackvis dtrace flamegraph-svg < stacks.out > stacks.svg
-
-
-This is a visualization of all of the profiled call stacks. This example is from the "hello world" HTTP server on the Node.js home page under load. Start at the bottom, where you have "main", which is present in most Node stacks because Node spends most on-CPU time in the main thread. Above each row, you have the functions called by the frame beneath it. As you move up, you'll see actual JavaScript function names. The boxes in each row are not in chronological order, but their width indicates how much time was spent there. When you hover over each box, you can see exactly what percentage of time is spent in each function. This lets you see at a glance where your program spends its time.
-
-That's the summary. There are a few prerequisites:
-
-
-
-
-There are a few other notes:
-
---with-dtrace. The helper doesn't work with 64-bit Node yet. On illumos (including SmartOS), development releases (the 0.7.x train) include DTrace support by default.
-
-
-For more on the underlying pieces, see my previous post on Node.js profiling and Brendan's post on Flame Graphs.
-
-c++filt to demangle C++ symbols. Be sure to use the c++filt that came with the compiler you used to build Node. For example:
- c++filt < stacks.out > demangled.out
- then you can use demangled.out to create the flamegraph.
-
-$ stackvis dtrace collapsed < stacks.out | grep SomeFunction > collapsed.out
-$ stackvis collapsed flamegraph-svg < collapsed.out > stacks.svg
-
-
+It's incredibly easy to visualize where your Node program spends its time using DTrace and node-stackvis (a Node port of Brendan Gregg's FlameGraph tool):
+
+
+
+
+You'll be looking at something like this:
+
+
+$ dtrace -o stacks.out -n 'profile-97/execname == "node" && arg1/{
+ @[jstack(100, 8000)] = count(); } tick-60s { exit(0); }'
+ This will sample about 100 times per second for 60 seconds and emit results to stacks.out. Note that this will sample all running programs called "node". If you want a specific process, replace execname == "node" with pid == 12345 (the process id).
+ $ npm install -g stackvis
+ then use stackvis to convert the DTrace output to a flamegraph:
+ $ stackvis dtrace flamegraph-svg < stacks.out > stacks.svg
+
+
+This is a visualization of all of the profiled call stacks. This example is from the "hello world" HTTP server on the Node.js home page under load. Start at the bottom, where you have "main", which is present in most Node stacks because Node spends most on-CPU time in the main thread. Above each row, you have the functions called by the frame beneath it. As you move up, you'll see actual JavaScript function names. The boxes in each row are not in chronological order, but their width indicates how much time was spent there. When you hover over each box, you can see exactly what percentage of time is spent in each function. This lets you see at a glance where your program spends its time.
+
+That's the summary. There are a few prerequisites:
+
+
+
+
+There are a few other notes:
+
+--with-dtrace. The helper doesn't work with 64-bit Node yet. On illumos (including SmartOS), development releases (the 0.7.x train) include DTrace support by default.
+
+
+For more on the underlying pieces, see my previous post on Node.js profiling and Brendan's post on Flame Graphs.
+
+c++filt to demangle C++ symbols. Be sure to use the c++filt that came with the compiler you used to build Node. For example:
+ c++filt < stacks.out > demangled.out
+ then you can use demangled.out to create the flamegraph.
+
+$ stackvis dtrace collapsed < stacks.out | grep SomeFunction > collapsed.out
+$ stackvis collapsed flamegraph-svg < collapsed.out > stacks.svg
+
+
Dave Pacheco blogs at dtrace.org
From fe659a60179c5816f888585894faa6d4134ec3cc Mon Sep 17 00:00:00 2001
From: Dave Pacheco
-$ dtrace -o stacks.out -n 'profile-97/execname == "node" && arg1/{
- @[jstack(100, 8000)] = count(); } tick-60s { exit(0); }'
+$ dtrace -n 'profile-97/execname == "node" && arg1/{
+ @[jstack(150, 8000)] = count(); } tick-60s { exit(0); }' > stacks.out
This will sample about 100 times per second for 60 seconds and emit results to stacks.out. Note that this will sample all running programs called "node". If you want a specific process, replace execname == "node" with pid == 12345 (the process id).
--balance 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.
-
+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 --balance 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: the number of success stories from developers and corporations who are adopting the technology continues to grow.
diff --git a/doc/blog/Uncategorized/development-environment.md b/doc/blog/Uncategorized/development-environment.md
index f71418158..e6015e04c 100644
--- a/doc/blog/Uncategorized/development-environment.md
+++ b/doc/blog/Uncategorized/development-environment.md
@@ -5,21 +5,21 @@ status: publish
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 dpkg. Software that you compile yourself should *not* go into /usr, 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 $HOME/local/$PACKAGE. Here is how I install node on my machine:./configure --prefix=$HOME/local/node-v0.4.5 && make install
-
-To have my paths automatically set I put this inside my $HOME/.zshrc: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
-
-Node is under sufficiently rapid development that everyone should be compiling it themselves. A corollary of this is that npm (which should be installed alongside Node) does not require root to install packages.
-
+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 dpkg. Software that you compile yourself should *not* go into /usr, 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 $HOME/local/$PACKAGE. Here is how I install node on my machine:./configure --prefix=$HOME/local/node-v0.4.5 && make install
+
+To have my paths automatically set I put this inside my $HOME/.zshrc: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
+
+Node is under sufficiently rapid development that everyone should be compiling it themselves. A corollary of this is that npm (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 npm 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. npm is a development tool. When a program written in Node becomes sufficiently mature it should be distributed as a tarball, .deb, .rpm, or other package system. It should not be distributed to end users with npm.
diff --git a/doc/blog/Uncategorized/evolving-the-node-js-brand.md b/doc/blog/Uncategorized/evolving-the-node-js-brand.md
index dbb7f852f..e631a2270 100644
--- a/doc/blog/Uncategorized/evolving-the-node-js-brand.md
+++ b/doc/blog/Uncategorized/evolving-the-node-js-brand.md
@@ -5,30 +5,30 @@ status: publish
category: Uncategorized
slug: evolving-the-node-js-brand
-To echo Node’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.
-
-Building a brand
-
-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: kinetic,connected, scalable, modular, mechanical and organic. Working with designer Chris Glass, our explorations emphasized Node's dynamism and formed a visual language based on structure, relationships and interconnectedness.
-
-
-
-Inspired by process visualization, we discovered pattern, form, and by relief, the hex shape. The angled infrastructure encourages energy to move through the letterforms.
-
-
-
-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.
-
-
-
-We look forward to exploring this visual language as the technology charges into a very promising future.
-
-
-
-We hope you'll have fun using it.
-
-To download the new logo, visit nodejs.org/logos.
-
+To echo Node’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.
+
+Building a brand
+
+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: kinetic,connected, scalable, modular, mechanical and organic. Working with designer Chris Glass, our explorations emphasized Node's dynamism and formed a visual language based on structure, relationships and interconnectedness.
+
+
+
+Inspired by process visualization, we discovered pattern, form, and by relief, the hex shape. The angled infrastructure encourages energy to move through the letterforms.
+
+
+
+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.
+
+
+
+We look forward to exploring this visual language as the technology charges into a very promising future.
+
+
+
+We hope you'll have fun using it.
+
+To download the new logo, visit nodejs.org/logos.
+
diff --git a/doc/blog/Uncategorized/growing-up.md b/doc/blog/Uncategorized/growing-up.md
index 6faff59ce..10e1d58d0 100644
--- a/doc/blog/Uncategorized/growing-up.md
+++ b/doc/blog/Uncategorized/growing-up.md
@@ -5,8 +5,8 @@ status: publish
category: Uncategorized
slug: growing-up
-This week Microsoft announced support for Node in Windows Azure, 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 our website - 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 serving millions of users 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.
-
+This week Microsoft announced support for Node in Windows Azure, 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 our website - 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 serving millions of users 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.
diff --git a/doc/blog/Uncategorized/jobs-nodejs-org.md b/doc/blog/Uncategorized/jobs-nodejs-org.md
index bf8278b81..fe20efe91 100644
--- a/doc/blog/Uncategorized/jobs-nodejs-org.md
+++ b/doc/blog/Uncategorized/jobs-nodejs-org.md
@@ -5,10 +5,10 @@ status: publish
category: Uncategorized
slug: jobs-nodejs-org
-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".
-
+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".
+
jobs.nodejs.org
diff --git a/doc/blog/Uncategorized/ldapjs-a-reprise-of-ldap.md b/doc/blog/Uncategorized/ldapjs-a-reprise-of-ldap.md
index 57d4af7fe..7174e2b7c 100644
--- a/doc/blog/Uncategorized/ldapjs-a-reprise-of-ldap.md
+++ b/doc/blog/Uncategorized/ldapjs-a-reprise-of-ldap.md
@@ -5,80 +5,80 @@ status: publish
category: Uncategorized
slug: ldapjs-a-reprise-of-ldap
-This post has been about 10 years in the making. My first job out of college was at IBM working on the Tivoli Directory Server, 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 ldapjs different. Allow me to be the gray beard for a bit...
-What is LDAP and where did it come from?
+This post has been about 10 years in the making. My first job out of college was at IBM working on the Tivoli Directory Server, 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 ldapjs different. Allow me to be the gray beard for a bit...
+What is LDAP and where did it come from?
-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 X.500 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 actually on the OSI model).
-
-Several years after X.500 had been deployed (at telcos, academic institutions, etc.), it became clear that the Internet was "for real." LDAP, 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 graduate student 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 Berkeley Database (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 Active Directory 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 '389 Directory Server.' Probably the most popular fork of that code base now is OpenLDAP.
-
-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 engine yard pointed out a few years back, you can think of LDAP as the original NoSQL store.
-LDAP: The Good Parts
+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 X.500 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 actually on the OSI model).
-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:
- firstName: Mark
- lastName: Cavage
- city: Seattle
- uid: markc
- state: Washington
- mail: mcavagegmailcom
- phone: (206) 555-1212
- title: Software Engineer
- department: 123456
- objectclass: joyentPerson
-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:
- uid=david
- /
- uid=bryan
- / | \
- uid=markc uid=ryah uid=isaacs
-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:
-Â Â Â (title="Software Engineer")
-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:
-Â Â Â (&(title="Software Engineer")(city=Seattle))
-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.
-ldapjs: Why do I care?
+Several years after X.500 had been deployed (at telcos, academic institutions, etc.), it became clear that the Internet was "for real." LDAP, the "Lightweight Directory Access Protocol," was invented to act purely as an IP-accessible gateway to an X.500 directory.
-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:
-
-
-
-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 Joyent, and like everyone else, we have several use problems that are classic directory service problems. If you break down the list I outlined above:
-
-
-
-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 ASN.1 (the binary wire protocol) or the LDAP RFC in detail (this one mostly worked out; ldap_modify is still kind of a PITA).
-
-Within 24 hours of releasing ldapjs on Twitter, there was an implementation of an address book that works with Thunderbird/Evolution, by the end of that weekend there was some slick integration with CouchDB, and ldapjs even got used in one of the node knockout apps. Off to a pretty good start!
-
-The Road Ahead
+At some point in the early 90's, a graduate student 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 Berkeley Database (BDB) was put in, and still remains the de facto storage engine for most LDAP directories.
-Hopefully you've been motivated to learn a little bit more about LDAP and try out ldapjs. The best place to start is probably the guide. After that you'll probably need to pick up a book from back in the day. 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 dtrace support if you're running on Mac OS X or preferably Joyent's SmartOS (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.
+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 Active Directory 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 '389 Directory Server.' Probably the most popular fork of that code base now is OpenLDAP.
+
+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 engine yard pointed out a few years back, you can think of LDAP as the original NoSQL store.
+LDAP: The Good Parts
+
+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:
+ firstName: Mark
+ lastName: Cavage
+ city: Seattle
+ uid: markc
+ state: Washington
+ mail: mcavagegmailcom
+ phone: (206) 555-1212
+ title: Software Engineer
+ department: 123456
+ objectclass: joyentPerson
+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:
+ uid=david
+ /
+ uid=bryan
+ / | \
+ uid=markc uid=ryah uid=isaacs
+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:
+Â Â Â (title="Software Engineer")
+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:
+Â Â Â (&(title="Software Engineer")(city=Seattle))
+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.
+ldapjs: Why do I care?
+
+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:
+
+
+
+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 Joyent, and like everyone else, we have several use problems that are classic directory service problems. If you break down the list I outlined above:
+
+
+
+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 ASN.1 (the binary wire protocol) or the LDAP RFC in detail (this one mostly worked out; ldap_modify is still kind of a PITA).
+
+Within 24 hours of releasing ldapjs on Twitter, there was an implementation of an address book that works with Thunderbird/Evolution, by the end of that weekend there was some slick integration with CouchDB, and ldapjs even got used in one of the node knockout apps. Off to a pretty good start!
+
+The Road Ahead
+
+Hopefully you've been motivated to learn a little bit more about LDAP and try out ldapjs. The best place to start is probably the guide. After that you'll probably need to pick up a book from back in the day. 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 dtrace support if you're running on Mac OS X or preferably Joyent's SmartOS (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.
diff --git a/doc/blog/Uncategorized/libuv-status-report.md b/doc/blog/Uncategorized/libuv-status-report.md
index 68637a43b..4d7f3e987 100644
--- a/doc/blog/Uncategorized/libuv-status-report.md
+++ b/doc/blog/Uncategorized/libuv-status-report.md
@@ -5,41 +5,41 @@ status: publish
category: Uncategorized
slug: libuv-status-report
-We announced 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 libuv which has resulted from porting Node to Windows.
-
-libuv'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, libuv 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 libev and libeio. For DNS we integrated with Daniel Stenberg's C-Ares. For cross-platform build-system support we're relying on Chrome's GYP meta-build system.
-
-The current implmented features are:
-
-
-The features we are working on still are
-uv_getaddrinfo.uv_fs_*uv_hrtimeuv_exepathuv_queue_work
-
-For complete documentation see the header file: include/uv.h. There are a number of tests in the test directory which demonstrate the API.
-
-ReadDirectoryChangesW and will support kqueue and event ports in the near future.) uv_fs_event_tuv_tty_tuv_ipc_t (planned API)libuv 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 libuv:
-
-
+We announced 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 libuv which has resulted from porting Node to Windows.
+
+libuv'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, libuv 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 libev and libeio. For DNS we integrated with Daniel Stenberg's C-Ares. For cross-platform build-system support we're relying on Chrome's GYP meta-build system.
+
+The current implmented features are:
+
+
+The features we are working on still are
+uv_getaddrinfo.uv_fs_*uv_hrtimeuv_exepathuv_queue_work
+
+For complete documentation see the header file: include/uv.h. There are a number of tests in the test directory which demonstrate the API.
+
+ReadDirectoryChangesW and will support kqueue and event ports in the near future.) uv_fs_event_tuv_tty_tuv_ipc_t (planned API)libuv 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 libuv:
+
+
We hope to see more people contributing and using libuv in the future!
diff --git a/doc/blog/Uncategorized/node-meetup-this-thursday.md b/doc/blog/Uncategorized/node-meetup-this-thursday.md
index 0dfb98dae..6f38e9998 100644
--- a/doc/blog/Uncategorized/node-meetup-this-thursday.md
+++ b/doc/blog/Uncategorized/node-meetup-this-thursday.md
@@ -5,7 +5,7 @@ status: publish
category: Uncategorized
slug: node-meetup-this-thursday
-http://nodejs.org/meetup/
-http://nodemeetup.eventbrite.com/
-
+http://nodejs.org/meetup/
+http://nodemeetup.eventbrite.com/
+
Three companies will describe their distributed Node applications. Sign up soon, space is limited!
diff --git a/doc/blog/Uncategorized/node-office-hours-cut-short.md b/doc/blog/Uncategorized/node-office-hours-cut-short.md
index 48d034405..743394460 100644
--- a/doc/blog/Uncategorized/node-office-hours-cut-short.md
+++ b/doc/blog/Uncategorized/node-office-hours-cut-short.md
@@ -5,8 +5,8 @@ status: publish
category: Uncategorized
slug: node-office-hours-cut-short
-This week office hours are only from 4pm to 6pm. Isaac will be in the Joyent office in SF - everyone else is out of town. Sign up at http://nodeworkup.eventbrite.com/ if you would like to come.
-
-The week after, Thursday May 5th, we will all be at NodeConf in Portland.
-
+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.
diff --git a/doc/blog/Uncategorized/office-hours.md b/doc/blog/Uncategorized/office-hours.md
index e4c94992c..fc2769095 100644
--- a/doc/blog/Uncategorized/office-hours.md
+++ b/doc/blog/Uncategorized/office-hours.md
@@ -5,8 +5,8 @@ status: publish
category: Uncategorized
slug: office-hours
-Starting next Thursday Isaac, Tom, and I will be holding weekly office hours at Joyent HQ 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 Event Brite.
-
+Starting next Thursday Isaac, Tom, and I will be holding weekly office hours at Joyent HQ 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 Event Brite.
+
We start at 4p and end promptly at 8p.
diff --git a/doc/blog/Uncategorized/porting-node-to-windows-with-microsoft%e2%80%99s-help.md b/doc/blog/Uncategorized/porting-node-to-windows-with-microsoft%e2%80%99s-help.md
index d2be3e3ba..cea3e8802 100644
--- a/doc/blog/Uncategorized/porting-node-to-windows-with-microsoft%e2%80%99s-help.md
+++ b/doc/blog/Uncategorized/porting-node-to-windows-with-microsoft%e2%80%99s-help.md
@@ -5,8 +5,8 @@ status: publish
category: Uncategorized
slug: porting-node-to-windows-with-microsoft%e2%80%99s-help
-I'm pleased to announce that Microsoft is partnering with Joyent in formally contributing resources towards porting Node to Windows. As you may have heard in a talk 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. Rackspace is also contributing Bert Belder's time to this undertaking.
-
+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 talk 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. Rackspace is also contributing Bert Belder'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.
diff --git a/doc/blog/Uncategorized/some-new-node-projects.md b/doc/blog/Uncategorized/some-new-node-projects.md
index 77515af73..2590f547a 100644
--- a/doc/blog/Uncategorized/some-new-node-projects.md
+++ b/doc/blog/Uncategorized/some-new-node-projects.md
@@ -5,9 +5,9 @@ status: publish
category: Uncategorized
slug: some-new-node-projects
-
-
+Download: http://nodejs.org/dist/node-v0.5.0.tar.gz
+
+Website: http://nodejs.org/docs/v0.5.0/
+
Documentation: http://nodejs.org/docs/v0.5.0/api/
diff --git a/doc/blog/release/node-v0-5-1.md b/doc/blog/release/node-v0-5-1.md
index f9799d40b..8137e8c88 100644
--- a/doc/blog/release/node-v0-5-1.md
+++ b/doc/blog/release/node-v0-5-1.md
@@ -6,25 +6,25 @@ status: publish
category: release
slug: node-v0-5-1
-2011.07.14, Version 0.5.1 (unstable)
-
+
-Download: http://nodejs.org/dist/node-v0.5.0.tar.gz
-
-Website: http://nodejs.org/docs/v0.5.0/
-
+2011.07.05, Version 0.5.0 (unstable)
+
+
Scott Hanselman posted a detailed walkthrough of how to get started with iisnode
diff --git a/doc/blog/Uncategorized/the-videos-from-node-meetup.md b/doc/blog/Uncategorized/the-videos-from-node-meetup.md
index aa2ce5ac5..68c5effe1 100644
--- a/doc/blog/Uncategorized/the-videos-from-node-meetup.md
+++ b/doc/blog/Uncategorized/the-videos-from-node-meetup.md
@@ -5,6 +5,6 @@ status: publish
category: Uncategorized
slug: the-videos-from-node-meetup
-Uber, Voxer, and Joyent described how they use Node in production
-
+Uber, Voxer, and Joyent described how they use Node in production
+
http://joyeur.com/2011/08/11/node-js-meetup-distributed-web-architectures/
diff --git a/doc/blog/Uncategorized/trademark.md b/doc/blog/Uncategorized/trademark.md
index fc89cfa04..1bc177b58 100644
--- a/doc/blog/Uncategorized/trademark.md
+++ b/doc/blog/Uncategorized/trademark.md
@@ -5,13 +5,13 @@ status: publish
category: Uncategorized
slug: trademark
-One of the things Joyent accepted when we took on the Node project was to provide resources to help the community grow. The Node project is amazing because of the expertize, dedication and hard work of the community. However in all communities there is the possibility of people acting inappropriately. We decided to introduce trademarks on the “Node.js†and the “Node logo†in order to ensure that people or organisations who are not investing in the Node community misrepresent, or create confusion about the role of themselves or their products with Node.
-
-We are big fans of the people who have contributed to Node and we have worked hard to make sure that existing members of the community will be unaffected by this change. For most people they don’t have to do anything they are free to use the Node.js marks in their free open source projects (see guidelines). For others we’ve already granted them licenses to use Node.js marks in their domain names and their businesses. We value all of these contributions to the Node community and hope that we can continue to protect their good names and hard work.
-
-Where does our trademark policy come from? We started by looking at popular open source foundations like the Apache Software Foundation and Linux. By strongly basing our policy on the one used by the Apache Software Foundation we feel that we’ve created a policy which is liberal enough to allow the open source community to easily make use of the mark in the context of free open source software, but secure enough to protect the community’s work from being misrepresented by other organisations.
-
-While we realise that any changes involving lawyers can be intimidating to the community we want to make this transition as smoothly as possible and welcome your questions and feedback on the policy and how we are implementing it.
-
-http://nodejs.org/trademark-policy.pdf
+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.
+
+http://nodejs.org/trademark-policy.pdf
trademark@joyent.com
diff --git a/doc/blog/Uncategorized/version-0-6.md b/doc/blog/Uncategorized/version-0-6.md
index 9ab82985f..8dd9719e7 100644
--- a/doc/blog/Uncategorized/version-0-6.md
+++ b/doc/blog/Uncategorized/version-0-6.md
@@ -5,8 +5,8 @@ status: publish
category: Uncategorized
slug: version-0-6
-Version 0.6.0 will be released next week. Please spend some time this week upgrading your code to v0.5.10. Report any API differences at https://github.com/joyent/node/wiki/API-changes-between-v0.4-and-v0.6 or report a bug to us at http://github.com/joyent/node/issues 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.
-
+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 https://github.com/joyent/node/wiki/API-changes-between-v0.4-and-v0.6 or report a bug to us at http://github.com/joyent/node/issues 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 http://search.npmjs.org/ and try out random ones. This is especially encouraged of Windows users!
diff --git a/doc/blog/module/multi-server-continuous-deployment-with-fleet.md b/doc/blog/module/multi-server-continuous-deployment-with-fleet.md
index 7d76ad894..7849ee410 100644
--- a/doc/blog/module/multi-server-continuous-deployment-with-fleet.md
+++ b/doc/blog/module/multi-server-continuous-deployment-with-fleet.md
@@ -5,85 +5,85 @@ status: publish
category: module
slug: multi-server-continuous-deployment-with-fleet
-
This is a guest post by James "SubStack" Halliday, originally posted on his blog, and reposted here with permission.npm install -g fleet
-
-fleet hub --port=7000 --secret=beepboop
-
-fleet drone --hub=x.x.x.x:7000 --secret=beepboop
-
-fleet remote add default --hub=x.x.x.x:7000 --secret=beepboop
-
-fleet deploy
-
-fleet spawn -- node server.js 8080
-
-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
-
-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 `.
-
-
This is a guest post by James "SubStack" Halliday, originally posted on his blog, and reposted here with permission.npm install -g fleet
+
+fleet hub --port=7000 --secret=beepboop
+
+fleet drone --hub=x.x.x.x:7000 --secret=beepboop
+
+fleet remote add default --hub=x.x.x.x:7000 --secret=beepboop
+
+fleet deploy
+
+fleet spawn -- node server.js 8080
+
+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
+
+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 `.
+
+
diff --git a/doc/blog/module/service-logging-in-json-with-bunyan.md b/doc/blog/module/service-logging-in-json-with-bunyan.md
index 2a6891e7d..8a323c4ae 100644
--- a/doc/blog/module/service-logging-in-json-with-bunyan.md
+++ b/doc/blog/module/service-logging-in-json-with-bunyan.md
@@ -5,333 +5,333 @@ status: publish
category: module
slug: service-logging-in-json-with-bunyan
-
-
-
-
-
-Current State of Log Formatting
-
-
-
-# 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.
-JSON for Logs
-
-JSON.parse() solves all that. Let's log in JSON. But it means a change in thinking: The first-level audience for log files shouldn't be a person, but a machine.grep and awk awkward. Using less directly on a log is handy.json tool -- json is one, bunyan described below is another one. Time to learn your JSON library instead of your regex library: JavaScript, Python, Ruby, Java, Perl.Introducing Bunyan
-
-bunyan CLI tool to view those logs.
-
-$ cat hi.js
-var Logger = require('bunyan');
-var log = new Logger({name: 'hello' /*, ... */});
-log.info("hi %s", "paul");
-
-
-$ node hi.js
-{"name":"hello","hostname":"banana.local","pid":40026,"level":30,"msg":"hi paul","time":"2012-03-28T17:25:37.050Z","v":0}
-bunyan tool that is part of the "node-bunyan" install to get more readable output:
-
-$ 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
-}
-log.info(...), 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.Longer Bunyan Example
-
-
-
-git clone https://github.com/trentm/hello-json-logging.git
-cd hello-json-logging
-make
-Bunyan Logger
-
-
-
-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,
- },
-});
-Logger.stdSerializers.req function to convert HTTP Request objects (using the field name "req") to JSON. More on serializers later.Restify Server
-
-
-
-var server = restify.createServer({
- name: 'Hello API',
- log: log // Pass our logger to restify.
-});
-GET /hello?name=NAME endpoint:
-
-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();
-});
-node server.js, and call the endpoint, we get the expected restify response:
-
-$ 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"}
-Setup Server Logging
-
-server.pre to hook into restify's request handling before routing where we'll log the request.
-
-server.pre(function (request, response, next) {
- request.log.info({req: request}, 'start'); // (1)
- return next();
-});
-log.info style with an object as the first argument. Bunyan logging methods (log.trace, log.debug, ...) all support an optional first object argument with extra log record fields:
-
-log.info(<object> fields, <string> msg, ...)
-req. The "req" serializer we registered above will come into play here, but bear with me.
-
-req.log.debug('caller is "%s"', caller); // (2)
-after event to log the response:
-
-server.on('after', function (req, res, route) {
- req.log.info({res: res}, "finished"); // (3)
-});
-Log Output
-
-
-
-$ 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"}
-
-
-[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}
-node server.js | ./node_modules/.bin/bunyan -j:
-
-{ // (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
-}
-request.log.info({req: request}, 'start'). The use of the "req" field triggers the "req" serializer registered at Logger creation.req.log.debug in our handler:
-
-{ // (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
-}
-
-
-{ // (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
-}
-
-
-
-req.log logger by restify). Note that this is the same UUID as the "X-Request-Id" header in the curl response. This means that if you use req.log for logging in your API handlers you will get an easy way to collate all logging for particular requests.bunyan tool does a decent job of nicely formatting multiline messages and "req"/"res" keys (with color, not shown in the gist).Other Tools
-
-Final Thoughts
-
-
+
+
+Current State of Log Formatting
+
+
+
+# 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.
+JSON for Logs
+
+JSON.parse() solves all that. Let's log in JSON. But it means a change in thinking: The first-level audience for log files shouldn't be a person, but a machine.grep and awk awkward. Using less directly on a log is handy.json tool -- json is one, bunyan described below is another one. Time to learn your JSON library instead of your regex library: JavaScript, Python, Ruby, Java, Perl.Introducing Bunyan
+
+bunyan CLI tool to view those logs.
+
+$ cat hi.js
+var Logger = require('bunyan');
+var log = new Logger({name: 'hello' /*, ... */});
+log.info("hi %s", "paul");
+
+
+$ node hi.js
+{"name":"hello","hostname":"banana.local","pid":40026,"level":30,"msg":"hi paul","time":"2012-03-28T17:25:37.050Z","v":0}
+bunyan tool that is part of the "node-bunyan" install to get more readable output:
+
+$ 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
+}
+log.info(...), 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.Longer Bunyan Example
+
+
+
+git clone https://github.com/trentm/hello-json-logging.git
+cd hello-json-logging
+make
+Bunyan Logger
+
+
+
+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,
+ },
+});
+Logger.stdSerializers.req function to convert HTTP Request objects (using the field name "req") to JSON. More on serializers later.Restify Server
+
+
+
+var server = restify.createServer({
+ name: 'Hello API',
+ log: log // Pass our logger to restify.
+});
+GET /hello?name=NAME endpoint:
+
+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();
+});
+node server.js, and call the endpoint, we get the expected restify response:
+
+$ 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"}
+Setup Server Logging
+
+server.pre to hook into restify's request handling before routing where we'll log the request.
+
+server.pre(function (request, response, next) {
+ request.log.info({req: request}, 'start'); // (1)
+ return next();
+});
+log.info style with an object as the first argument. Bunyan logging methods (log.trace, log.debug, ...) all support an optional first object argument with extra log record fields:
+
+log.info(<object> fields, <string> msg, ...)
+req. The "req" serializer we registered above will come into play here, but bear with me.
+
+req.log.debug('caller is "%s"', caller); // (2)
+after event to log the response:
+
+server.on('after', function (req, res, route) {
+ req.log.info({res: res}, "finished"); // (3)
+});
+Log Output
+
+
+
+$ 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"}
+
+
+[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}
+node server.js | ./node_modules/.bin/bunyan -j:
+
+{ // (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
+}
+request.log.info({req: request}, 'start'). The use of the "req" field triggers the "req" serializer registered at Logger creation.req.log.debug in our handler:
+
+{ // (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
+}
+
+
+{ // (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
+}
+
+
+
+req.log logger by restify). Note that this is the same UUID as the "X-Request-Id" header in the curl response. This means that if you use req.log for logging in your API handlers you will get an easy way to collate all logging for particular requests.bunyan tool does a decent job of nicely formatting multiline messages and "req"/"res" keys (with color, not shown in the gist).Other Tools
+
+Final Thoughts
+
+Shrinkwrapping packages
-
-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.
-{
- "name": "A",
- "version": "0.1.0",
- "dependencies": {
- "B": "<0.1.0"
- }
-}
-{
- "name": "B",
- "version": "0.0.1",
- "dependencies": {
- "C": "<0.1.0"
- }
-}
-{
- "name": "C,
- "version": "0.0.1"
-}
-A@0.1.0
-└─┬ B@0.0.1
- └── C@0.0.1
-A@0.1.0
-└─┬ B@0.0.2
- └── C@0.0.1
-# npm shrinkwrap
-{
- "name": "A",
- "dependencies": {
- "B": {
- "version": "0.0.1",
- "dependencies": {
- "C": { "version": "0.1.0" }
- }
- }
- }
-}Using shrinkwrapped packages
-Building shrinkwrapped packages
-
-
-
-
-Why not just check
-node_modules into git?What if an author republishes an existing version of a package?
-Final thoughts
-
-Dave Pacheco blogs at dtrace.org.
-
-Shrinkwrapping packages
+
+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.
+{
+ "name": "A",
+ "version": "0.1.0",
+ "dependencies": {
+ "B": "<0.1.0"
+ }
+}
+{
+ "name": "B",
+ "version": "0.0.1",
+ "dependencies": {
+ "C": "<0.1.0"
+ }
+}
+{
+ "name": "C,
+ "version": "0.0.1"
+}
+A@0.1.0
+└─┬ B@0.0.1
+ └── C@0.0.1
+A@0.1.0
+└─┬ B@0.0.2
+ └── C@0.0.1
+# npm shrinkwrap
+{
+ "name": "A",
+ "dependencies": {
+ "B": {
+ "version": "0.0.1",
+ "dependencies": {
+ "C": { "version": "0.1.0" }
+ }
+ }
+ }
+}Using shrinkwrapped packages
+Building shrinkwrapped packages
+
+
+
+
+Why not just check
+node_modules into git?What if an author republishes an existing version of a package?
+Final thoughts
+
+Dave Pacheco blogs at dtrace.org.
+
+bundle that a lot of people liked. bundle let you install your dependencies locally in your project, but even still, it was basically a hack that never really worked very reliably.Two paths
-
-
-
-{prefix}/lib/node_modules, and puts executable files in {prefix}/bin, where {prefix} is usually something like /usr/local. It also installs man pages in {prefix}/share/man, if they’re supplied../node_modules, executables go in ./node_modules/.bin/, and man pages aren’t installed at all.Which to choose
-
-global config, which is aliased to the -g command line switch.
-
-require('whatever'), then install it locally, at the root of your project.PATH environment variable.When you can't choose
-
-
-
-npm link coffee-script or npm link express (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.npm link in a future installment.)Slight exception: It’s not always the cwd.
-
-
-
-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.redis into ~/projects/foo/node_modules/redis. Sort of like how git will work anywhere within a git repository, npm will work anywhere within a package, defined by having a node_modules folder.Test runners and stuff
-
-scripts.test command uses a command-line program installed by one of your dependencies, not to worry. npm makes ./node_modules/.bin the first entry in the PATH environment variable when running any lifecycle scripts, so this will work fine, even if your program is not globally installed:
-
-{ "name" : "my-program"
-, "version" : "1.2.3"
-, "dependencies": { "express": "*", "coffee-script": "*" }
-, "devDependencies": { "vows": "*" }
-, "scripts":
- { "test": "vows test/*.js"
+bundle that a lot of people liked. bundle let you install your dependencies locally in your project, but even still, it was basically a hack that never really worked very reliably.Two paths
+
+
+
+{prefix}/lib/node_modules, and puts executable files in {prefix}/bin, where {prefix} is usually something like /usr/local. It also installs man pages in {prefix}/share/man, if they’re supplied../node_modules, executables go in ./node_modules/.bin/, and man pages aren’t installed at all.Which to choose
+
+global config, which is aliased to the -g command line switch.
+
+require('whatever'), then install it locally, at the root of your project.PATH environment variable.When you can't choose
+
+
+
+npm link coffee-script or npm link express (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.npm link in a future installment.)Slight exception: It’s not always the cwd.
+
+
+
+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.redis into ~/projects/foo/node_modules/redis. Sort of like how git will work anywhere within a git repository, npm will work anywhere within a package, defined by having a node_modules folder.Test runners and stuff
+
+scripts.test command uses a command-line program installed by one of your dependencies, not to worry. npm makes ./node_modules/.bin the first entry in the PATH environment variable when running any lifecycle scripts, so this will work fine, even if your program is not globally installed:
+
+
diff --git a/doc/blog/npm/npm-1-0-link.md b/doc/blog/npm/npm-1-0-link.md
index bb0d2f808..9e5c3c8e7 100644
--- a/doc/blog/npm/npm-1-0-link.md
+++ b/doc/blog/npm/npm-1-0-link.md
@@ -5,110 +5,110 @@ status: publish
category: npm
slug: npm-1-0-link
-{ "name" : "my-program"
+, "version" : "1.2.3"
+, "dependencies": { "express": "*", "coffee-script": "*" }
+, "devDependencies": { "vows": "*" }
+, "scripts":
+ { "test": "vows test/*.js"
, "preinstall": "cake build" } }link. 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.
-
-prefix/lib/node/.npm/my-package/1.3.6/package
-
-
-prefix/lib/node/my-package@1.3.6 -> ./.npm/my-package/1.3.6/package
-A better way
-
-
-
-
-require() it.
-
-Link devel → global
-
-
-
-cd ~/dev/js/node-tap # go into the project dir
-npm link # create symlinks into {prefix}
-/usr/local as my install prefix, I end up with a symlink from /usr/local/lib/node_modules/tap pointing to ~/dev/js/node-tap, and the executable linked to /usr/local/bin/tap.prefix rather than /usr/local.)Link global → local
-
-npm link pkg where pkg is the name of the package that you want to install.
-
-cd ~/dev/js/node-glob # go to the project that uses the thing.
-npm link tap # link the global thing into my project.
-~/dev/js/node-tap, they’ll be immediately reflected in ~/dev/js/node-glob/node_modules/tap.Link to stuff you don’t build
-
-
-
-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.
-Caveat: Not For Real Servers
-
-Caveat 2: Sorry, Windows!
-
-wontfix.Aside: Credit where Credit’s Due
-
-link. 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.
+
+prefix/lib/node/.npm/my-package/1.3.6/package
+
+
+prefix/lib/node/my-package@1.3.6 -> ./.npm/my-package/1.3.6/package
+A better way
+
+
+
+
+require() it.
+
+Link devel → global
+
+
+
+cd ~/dev/js/node-tap # go into the project dir
+npm link # create symlinks into {prefix}
+/usr/local as my install prefix, I end up with a symlink from /usr/local/lib/node_modules/tap pointing to ~/dev/js/node-tap, and the executable linked to /usr/local/bin/tap.prefix rather than /usr/local.)Link global → local
+
+npm link pkg where pkg is the name of the package that you want to install.
+
+cd ~/dev/js/node-glob # go to the project that uses the thing.
+npm link tap # link the global thing into my project.
+~/dev/js/node-tap, they’ll be immediately reflected in ~/dev/js/node-glob/node_modules/tap.Link to stuff you don’t build
+
+
+
+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.
+Caveat: Not For Real Servers
+
+Caveat 2: Sorry, Windows!
+
+wontfix.Aside: Credit where Credit’s Due
+
+
-
-Installing it
-
-
-
-curl http://npmjs.org/install.sh | sh
-
-curl http://npmjs.org/install.sh | clean=yes sh
-
-curl http://npmjs.org/install.sh | clean=no sh Code Freeze
-
-
+
+Installing it
+
+
+
+curl http://npmjs.org/install.sh | sh
+
+curl http://npmjs.org/install.sh | clean=yes sh
+
+curl http://npmjs.org/install.sh | clean=no sh Code Freeze
+
+ls command was a combination of both searching the registry as well as reporting on what you have installed.node_modules folder and installing locally by default, there are different things that you want to view.ls command was split into two different parts. search 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 ls shows a tree view of the packages that are installed locally.
-
-$ 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 extraneous
- ├─┬ connect@1.1.0
- │ ├── qs@0.0.7
- │ └── mime@1.2.1
- ├── mime@1.2.1
- └── qs@0.0.7
-npm install semver ronn express in the npm source directory. Since express isn’t actually a dependency of npm, it shows up with that “extraneous” marker.
-
-$ 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 extraneous
- ├── UNMET DEPENDENCY connect >= 1.1.0 < 2.0.0
- ├── mime@1.2.1
- └── qs@0.0.7
-
-
-$ 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
---long option to (shorthand: -l) to spit out more info:
-
-$ 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 extraneous
- │ ./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::::
-
-
+$ 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
-ls command was a combination of both searching the registry as well as reporting on what you have installed.node_modules folder and installing locally by default, there are different things that you want to view.ls command was split into two different parts. search 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 ls shows a tree view of the packages that are installed locally.
+
+$ 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 extraneous
+ ├─┬ connect@1.1.0
+ │ ├── qs@0.0.7
+ │ └── mime@1.2.1
+ ├── mime@1.2.1
+ └── qs@0.0.7
+npm install semver ronn express in the npm source directory. Since express isn’t actually a dependency of npm, it shows up with that “extraneous” marker.
+
+$ 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 extraneous
+ ├── UNMET DEPENDENCY connect >= 1.1.0 < 2.0.0
+ ├── mime@1.2.1
+ └── qs@0.0.7
+
+
+$ 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
+--long option to (shorthand: -l) to spit out more info:
+
+$ 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 extraneous
+ │ ./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::::
+
+
$ 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
+-> flags are indications that the package is link-installed, which will be covered in the next installment.
-
-Download: http://nodejs.org/dist/node-v0.4.10.tar.gz
-Website: http://nodejs.org/docs/v0.4.10
+2011.07.19, Version 0.4.10 (stable)
+
+
+Download: http://nodejs.org/dist/node-v0.4.10.tar.gz
+Website: http://nodejs.org/docs/v0.4.10
Documentation: http://nodejs.org/docs/v0.4.10/api
diff --git a/doc/blog/release/node-v0-4-11.md b/doc/blog/release/node-v0-4-11.md
index eca36d3ac..0bcbc37f5 100644
--- a/doc/blog/release/node-v0-4-11.md
+++ b/doc/blog/release/node-v0-4-11.md
@@ -6,34 +6,34 @@ status: publish
category: release
slug: node-v0-4-11
-2011.08.17, Version 0.4.11 (stable)
-
-
-
-
-
-Download: http://nodejs.org/dist/node-v0.4.11.tar.gz
-
-Website: http://nodejs.org/docs/v0.4.11/
-
+2011.08.17, Version 0.4.11 (stable)
+
+
+
+
+
+Download: http://nodejs.org/dist/node-v0.4.11.tar.gz
+
+Website: http://nodejs.org/docs/v0.4.11/
+
Documentation: http://nodejs.org/docs/v0.4.11/api/
diff --git a/doc/blog/release/node-v0-4-12.md b/doc/blog/release/node-v0-4-12.md
index 0e9aedd70..8eb53d1fe 100644
--- a/doc/blog/release/node-v0-4-12.md
+++ b/doc/blog/release/node-v0-4-12.md
@@ -6,24 +6,24 @@ status: publish
category: release
slug: node-v0-4-12
-2011.09.15, Version 0.4.12 (stable)
-
-
-
-
-
-
-Download: http://nodejs.org/dist/node-v0.4.12.tar.gz
-
-Website: http://nodejs.org/docs/v0.4.12/
-
+2011.09.15, Version 0.4.12 (stable)
+
+
+
+
+
+
+Download: http://nodejs.org/dist/node-v0.4.12.tar.gz
+
+Website: http://nodejs.org/docs/v0.4.12/
+
Documentation: http://nodejs.org/docs/v0.4.12/api/
diff --git a/doc/blog/release/node-v0-4-3.md b/doc/blog/release/node-v0-4-3.md
index e7672f849..10a3a5b29 100644
--- a/doc/blog/release/node-v0-4-3.md
+++ b/doc/blog/release/node-v0-4-3.md
@@ -6,28 +6,28 @@ status: publish
category: release
slug: node-v0-4-3
-2011.03.18, Version 0.4.3 (stable)
-
-
-
-
-
-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
-
-Announcement
-
+2011.03.18, Version 0.4.3 (stable)
+
+
+
+
+
+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
+
+Announcement
+
commit
diff --git a/doc/blog/release/node-v0-4-4.md b/doc/blog/release/node-v0-4-4.md
index 6c911cceb..417d73c54 100644
--- a/doc/blog/release/node-v0-4-4.md
+++ b/doc/blog/release/node-v0-4-4.md
@@ -6,22 +6,22 @@ status: publish
category: release
slug: node-v0-4-4
-2011.03.26, Version 0.4.4 (stable)
-
-
-
-
-
-Download: http://nodejs.org/dist/node-v0.4.4.tar.gz
-
-Website: http://nodejs.org/docs/v0.4.4
-
-Documentation: http://nodejs.org/docs/v0.4.4/api
-
+2011.03.26, Version 0.4.4 (stable)
+
+
+
+
+
+Download: http://nodejs.org/dist/node-v0.4.4.tar.gz
+
+Website: http://nodejs.org/docs/v0.4.4
+
+Documentation: http://nodejs.org/docs/v0.4.4/api
+
announcement
diff --git a/doc/blog/release/node-v0-4-5.md b/doc/blog/release/node-v0-4-5.md
index a27c56cc7..6935de062 100644
--- a/doc/blog/release/node-v0-4-5.md
+++ b/doc/blog/release/node-v0-4-5.md
@@ -6,24 +6,24 @@ status: publish
category: release
slug: node-v0-4-5
-2011.04.01, Version 0.4.5 (stable)
-
-
-
-
-
-Download: http://nodejs.org/dist/node-v0.4.5.tar.gz
-
-Website: http://nodejs.org/docs/v0.4.5
-
-Documentation: http://nodejs.org/docs/v0.4.5/api
-
-
+2011.04.01, Version 0.4.5 (stable)
+
+
+
+
+
+Download: http://nodejs.org/dist/node-v0.4.5.tar.gz
+
+Website: http://nodejs.org/docs/v0.4.5
+
+Documentation: http://nodejs.org/docs/v0.4.5/api
+
+
announcement
diff --git a/doc/blog/release/node-v0-4-6.md b/doc/blog/release/node-v0-4-6.md
index 0e4e88712..964f3a2e9 100644
--- a/doc/blog/release/node-v0-4-6.md
+++ b/doc/blog/release/node-v0-4-6.md
@@ -6,22 +6,22 @@ status: publish
category: release
slug: node-v0-4-6
-2011.04.13, Version 0.4.6 (stable)
-
-
-Download: http://nodejs.org/dist/node-v0.4.6.tar.gz
-
-Website: http://nodejs.org/docs/v0.4.6/
-
+2011.04.13, Version 0.4.6 (stable)
+
+
+Download: http://nodejs.org/dist/node-v0.4.6.tar.gz
+
+Website: http://nodejs.org/docs/v0.4.6/
+
Documentation: http://nodejs.org/docs/v0.4.6/api/
diff --git a/doc/blog/release/node-v0-4-7.md b/doc/blog/release/node-v0-4-7.md
index 38816c813..44e2715dc 100644
--- a/doc/blog/release/node-v0-4-7.md
+++ b/doc/blog/release/node-v0-4-7.md
@@ -6,18 +6,18 @@ status: publish
category: release
slug: node-v0-4-7
-2011.04.22, Version 0.4.7 (stable)
-
-
-
-Download: http://nodejs.org/dist/node-v0.4.7.tar.gz
-
-Website: http://nodejs.org/docs/v0.4.7/
-
+2011.04.22, Version 0.4.7 (stable)
+
+
+
+Download: http://nodejs.org/dist/node-v0.4.7.tar.gz
+
+Website: http://nodejs.org/docs/v0.4.7/
+
Documentation: http://nodejs.org/docs/v0.4.7/api
diff --git a/doc/blog/release/node-v0-4-8.md b/doc/blog/release/node-v0-4-8.md
index b7859edec..a25aedf60 100644
--- a/doc/blog/release/node-v0-4-8.md
+++ b/doc/blog/release/node-v0-4-8.md
@@ -6,50 +6,50 @@ status: publish
category: release
slug: node-v0-4-8
-2011.05.20, Version 0.4.8 (stable)
-
-* #974 Properly report traceless errors (isaacs)
-
-* #983 Better JSON.parse error detection in REPL (isaacs)
-
-* #836 Agent socket errors bubble up to req only if req exists
-
-* #1041 Fix event listener leak check timing (koichik)
-
-* #1038 Fix dns.resolve() with 'PTR' throws Error: Unknown type "PTR"
- (koichik)
-
-* #1073 Share SSL context between server connections (Fedor Indutny)
-
-* Disable compression with OpenSSL. Improves memory perf.
-
-* Implement os.totalmem() and os.freemem() for SunOS (Alexandre Marangone)
-
-* Fix a special characters in URL regression (isaacs)
-
-* Fix idle timeouts in HTTPS (Felix Geisendörfer)
-
-* SlowBuffer.write() with 'ucs2' throws ReferenceError. (koichik)
-
-* http.ServerRequest 'close' sometimes gets an error argument
- (Felix Geisendörfer)
-
-* Doc improvements
-
-* cleartextstream.destroy() should close(2) the socket. Previously was being
- mapped to a shutdown(2) syscall.
-
-* No longer compile out asserts and debug statements in normal build.
-
-* Debugger improvements.
-
-* Upgrade V8 to 3.1.8.16.
-
-
-
-
-Website: http://nodejs.org/docs/v0.4.8/
-
-Download: http://nodejs.org/dist/node-v0.4.8.tar.gz
-
+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: http://nodejs.org/docs/v0.4.8/
+
+Download: http://nodejs.org/dist/node-v0.4.8.tar.gz
+
Documentation: http://nodejs.org/docs/v0.4.8/api/
diff --git a/doc/blog/release/node-v0-4-9.md b/doc/blog/release/node-v0-4-9.md
index e2eccf2e0..8b71bd962 100644
--- a/doc/blog/release/node-v0-4-9.md
+++ b/doc/blog/release/node-v0-4-9.md
@@ -6,25 +6,25 @@ status: publish
category: release
slug: node-v0-4-9
-2011.06.29, Version 0.4.9 (stable)
-
-
-
-Download: http://nodejs.org/dist/node-v0.4.9.tar.gz
-
-Website: http://nodejs.org/docs/v0.4.9
-
+2011.06.29, Version 0.4.9 (stable)
+
+
+
+Download: http://nodejs.org/dist/node-v0.4.9.tar.gz
+
+Website: http://nodejs.org/docs/v0.4.9
+
Documentation: http://nodejs.org/docs/v0.4.9/api
diff --git a/doc/blog/release/node-v0-5-0-unstable.md b/doc/blog/release/node-v0-5-0-unstable.md
index 883b9a7f3..68ff2d117 100644
--- a/doc/blog/release/node-v0-5-0-unstable.md
+++ b/doc/blog/release/node-v0-5-0-unstable.md
@@ -6,34 +6,34 @@ status: publish
category: release
slug: node-v0-5-0-unstable
-2011.07.05, Version 0.5.0 (unstable)
-
---use-uv to enable.
---use-uv to enable.
+
-
-
-
-
-Download: http://nodejs.org/dist/v0.5.1/node-v0.5.1.tar.gz
-
-Windows Build: http://nodejs.org/dist/v0.5.1/node.exe
-
-Documentation: http://nodejs.org/dist/v0.5.1/docs/api/
-
+2011.07.14, Version 0.5.1 (unstable)
+
+
+
+
+
+Download: http://nodejs.org/dist/v0.5.1/node-v0.5.1.tar.gz
+
+Windows Build: http://nodejs.org/dist/v0.5.1/node.exe
+
+Documentation: http://nodejs.org/dist/v0.5.1/docs/api/
+
Website: http://nodejs.org/dist/v0.5.1/docs
diff --git a/doc/blog/release/node-v0-5-10.md b/doc/blog/release/node-v0-5-10.md
index 47fb92642..305813ecf 100644
--- a/doc/blog/release/node-v0-5-10.md
+++ b/doc/blog/release/node-v0-5-10.md
@@ -6,36 +6,36 @@ status: publish
category: release
slug: node-v0-5-10
-2011.10.21, Version 0.5.10 (unstable)
-
-
-
-
-Download: http://nodejs.org/dist/v0.5.10/node-v0.5.10.tar.gz
-
-Windows Executable: http://nodejs.org/dist/v0.5.10/node.exe
-
-Website: http://nodejs.org/docs/v0.5.10/
-
+2011.10.21, Version 0.5.10 (unstable)
+
+
+
+
+Download: http://nodejs.org/dist/v0.5.10/node-v0.5.10.tar.gz
+
+Windows Executable: http://nodejs.org/dist/v0.5.10/node.exe
+
+Website: http://nodejs.org/docs/v0.5.10/
+
Documentation: http://nodejs.org/docs/v0.5.10/api/
diff --git a/doc/blog/release/node-v0-5-2.md b/doc/blog/release/node-v0-5-2.md
index c44690f34..e87fda36f 100644
--- a/doc/blog/release/node-v0-5-2.md
+++ b/doc/blog/release/node-v0-5-2.md
@@ -6,22 +6,22 @@ status: publish
category: release
slug: node-v0-5-2
-2011.07.22, Version 0.5.2 (unstable)
-
-
-Download: http://nodejs.org/dist/v0.5.2/node-v0.5.2.tar.gz
-
-Windows Executable: http://nodejs.org/dist/v0.5.2/node.exe
-
-Website: http://nodejs.org/dist/v0.5.2/docs/
-
+2011.07.22, Version 0.5.2 (unstable)
+
+
+Download: http://nodejs.org/dist/v0.5.2/node-v0.5.2.tar.gz
+
+Windows Executable: http://nodejs.org/dist/v0.5.2/node.exe
+
+Website: http://nodejs.org/dist/v0.5.2/docs/
+
Documentation: http://nodejs.org/dist/v0.5.2/docs/api
diff --git a/doc/blog/release/node-v0-5-3.md b/doc/blog/release/node-v0-5-3.md
index f84a955f5..0b9e7b83b 100644
--- a/doc/blog/release/node-v0-5-3.md
+++ b/doc/blog/release/node-v0-5-3.md
@@ -6,48 +6,48 @@ status: publish
category: release
slug: node-v0-5-3
-2011.08.01, Version 0.5.3 (unstable)
-
-
-
-
-
-Download: http://nodejs.org/dist/v0.5.3/node-v0.5.3.tar.gz
-
-Windows Executable: http://nodejs.org/dist/v0.5.3/node.exe
-
-Website: http://nodejs.org/dist/v0.5.3/docs
-
+2011.08.01, Version 0.5.3 (unstable)
+
+--use-http2 will enable it. make test-http2 will run the tests for the new implementation. (Mikeal Rogers)
-
-
+
+
+
+Download: http://nodejs.org/dist/v0.5.3/node-v0.5.3.tar.gz
+
+Windows Executable: http://nodejs.org/dist/v0.5.3/node.exe
+
+Website: http://nodejs.org/dist/v0.5.3/docs
+
Documentation: http://nodejs.org/dist/v0.5.3/docs/api
diff --git a/doc/blog/release/node-v0-5-4.md b/doc/blog/release/node-v0-5-4.md
index 2dd02e12a..9f5f4e28a 100644
--- a/doc/blog/release/node-v0-5-4.md
+++ b/doc/blog/release/node-v0-5-4.md
@@ -6,31 +6,31 @@ status: publish
category: release
slug: node-v0-5-4
-2011.08.12, Version 0.5.4 (unstable)
-
---use-http2 will enable it. make test-http2 will run the tests for the new implementation. (Mikeal Rogers)
+
+
-
-
-Download: http://nodejs.org/dist/v0.5.4/node-v0.5.4.tar.gz
-
-Windows Executable: http://nodejs.org/dist/v0.5.4/node.exe
-
-Website: http://nodejs.org/dist/v0.5.4/docs
-
+2011.08.12, Version 0.5.4 (unstable)
+
+--use-http1
-
-
+
+
+Download: http://nodejs.org/dist/v0.5.4/node-v0.5.4.tar.gz
+
+Windows Executable: http://nodejs.org/dist/v0.5.4/node.exe
+
+Website: http://nodejs.org/dist/v0.5.4/docs
+
Documentation: http://nodejs.org/dist/v0.5.4/docs/api
diff --git a/doc/blog/release/node-v0-5-5.md b/doc/blog/release/node-v0-5-5.md
index 886fac90e..683fed49c 100644
--- a/doc/blog/release/node-v0-5-5.md
+++ b/doc/blog/release/node-v0-5-5.md
@@ -6,35 +6,35 @@ status: publish
category: release
slug: node-v0-5-5
---use-http1
+
+
-
- (Antranig Basman)
Download: http://nodejs.org/dist/node-v0.5.5.tar.gz
-Windows Executable: http://nodejs.org/dist/v0.5.5/node.exe
-Website: http://nodejs.org/docs/v0.5.5/
-Documentation: http://nodejs.org/docs/v0.5.5/api/
-2011.08.26, Version 0.5.5 (unstable)
+Download: http://nodejs.org/dist/node-v0.5.5.tar.gz
+Windows Executable: http://nodejs.org/dist/v0.5.5/node.exe
+Website: http://nodejs.org/docs/v0.5.5/
+Documentation: http://nodejs.org/docs/v0.5.5/api/
+.exe has a bug that results in incompatibility with Windows XP and Server 2003. This has been reported in issue #1592 and fixed. A new binary was made that is compatibile with the older Windows: http://nodejs.org/dist/v0.5.5/node-186364e.exe.
diff --git a/doc/blog/release/node-v0-5-6.md b/doc/blog/release/node-v0-5-6.md
index ca1a392b0..452878c30 100644
--- a/doc/blog/release/node-v0-5-6.md
+++ b/doc/blog/release/node-v0-5-6.md
@@ -6,44 +6,44 @@ status: publish
category: release
slug: node-v0-5-6
-2011.09.08, Version 0.5.6 (unstable)
-| v0.4.12 (linux) | v0.6.0 (linux) | |
|---|---|---|
| http_simple.js /bytes/1024 | 5461 r/s | 6263 r/s |
| io.js read | 19.75 mB/s | 26.63 mB/s |
| io.js write | 21.60 mB/s | 17.40 mB/s |
| startup.js | 74.7 ms | 49.6 ms |
| v0.4.12 (windows) | v0.6.0 (windows) | |
|---|---|---|
| http_simple.js /bytes/1024 | 3858 r/s | 5823 r/s |
| io.js read | 12.41 mB/s | 26.51 mB/s |
| io.js write | 12.61 mB/s | 33.58 mB/s |
| startup.js | 152.81 ms | 52.04 ms |
| v0.4.12 (linux) | v0.6.0 (linux) | |
|---|---|---|
| http_simple.js /bytes/1024 | 5461 r/s | 6263 r/s |
| io.js read | 19.75 mB/s | 26.63 mB/s |
| io.js write | 21.60 mB/s | 17.40 mB/s |
| startup.js | 74.7 ms | 49.6 ms |
| v0.4.12 (windows) | v0.6.0 (windows) | |
|---|---|---|
| http_simple.js /bytes/1024 | 3858 r/s | 5823 r/s |
| io.js read | 12.41 mB/s | 26.51 mB/s |
| io.js write | 12.61 mB/s | 33.58 mB/s |
| startup.js | 152.81 ms | 52.04 ms |
2012.02.02, Version 0.6.10 (stable)
- -Update V8 to 3.6.6.20
Add npm msysgit bash shim to msi installer (isaacs)
buffers: fix intermittent out of bounds error (Ben Noordhuis)
buffers: honor length argument in base64 decoder (Ben Noordhuis)
windows: Fix path.exists regression (Bert Belder)
Make QueryString.parse run faster (Philip Tellis)
http: avoid freeing http-parser objects too early (koichik)
timers: add v0.4 compatibility hack (Ben Noordhuis)
Proper EPERM error code support (Igor Zinkovsky, Brandon Philips)
dgram: Implement udp multicast methods on windows (Bert Belder)
Source Code: http://nodejs.org/dist/v0.6.10/node-v0.6.10.tar.gz
- -Windows Installer: http://nodejs.org/dist/v0.6.10/node-v0.6.10.msi
- -Macintosh Installer: http://nodejs.org/dist/v0.6.10/node-v0.6.10.pkg
- -Website: http://nodejs.org/docs/v0.6.10/
- +2012.02.02, Version 0.6.10 (stable)
+ +Update V8 to 3.6.6.20
Add npm msysgit bash shim to msi installer (isaacs)
buffers: fix intermittent out of bounds error (Ben Noordhuis)
buffers: honor length argument in base64 decoder (Ben Noordhuis)
windows: Fix path.exists regression (Bert Belder)
Make QueryString.parse run faster (Philip Tellis)
http: avoid freeing http-parser objects too early (koichik)
timers: add v0.4 compatibility hack (Ben Noordhuis)
Proper EPERM error code support (Igor Zinkovsky, Brandon Philips)
dgram: Implement udp multicast methods on windows (Bert Belder)
Source Code: http://nodejs.org/dist/v0.6.10/node-v0.6.10.tar.gz
+ +Windows Installer: http://nodejs.org/dist/v0.6.10/node-v0.6.10.msi
+ +Macintosh Installer: http://nodejs.org/dist/v0.6.10/node-v0.6.10.pkg
+ +Website: http://nodejs.org/docs/v0.6.10/
+Documentation: http://nodejs.org/docs/v0.6.10/api/
diff --git a/doc/blog/release/node-v0-6-2.md b/doc/blog/release/node-v0-6-2.md index b405268bc..9a75dcb16 100644 --- a/doc/blog/release/node-v0-6-2.md +++ b/doc/blog/release/node-v0-6-2.md @@ -6,22 +6,22 @@ status: publish category: release slug: node-v0-6-2 -2011.11.18, Version 0.6.2 (stable)
-Source Code: http://nodejs.org/dist/v0.6.2/node-v0.6.2.tar.gz
-Windows Installer: http://nodejs.org/dist/v0.6.2/node-v0.6.2.msi
-Macintosh Installer: http://nodejs.org/dist/v0.6.2/node-v0.6.2.pkg
-Website: http://nodejs.org/docs/v0.6.2/
+2011.11.18, Version 0.6.2 (stable)
+Source Code: http://nodejs.org/dist/v0.6.2/node-v0.6.2.tar.gz
+Windows Installer: http://nodejs.org/dist/v0.6.2/node-v0.6.2.msi
+Macintosh Installer: http://nodejs.org/dist/v0.6.2/node-v0.6.2.pkg
+Website: http://nodejs.org/docs/v0.6.2/
Documentation: http://nodejs.org/docs/v0.6.2/api/
diff --git a/doc/blog/release/node-v0-6-3.md b/doc/blog/release/node-v0-6-3.md index 559c3d352..e61c5f714 100644 --- a/doc/blog/release/node-v0-6-3.md +++ b/doc/blog/release/node-v0-6-3.md @@ -6,25 +6,25 @@ status: publish category: release slug: node-v0-6-3 -2011.11.25, Version 0.6.3 (stable) -2012.01.06, Version 0.6.7 (stable)
- -V8 hash collision fix (Breaks MIPS) (Bert Belder, Erik Corry)
Upgrade V8 to 3.6.6.15
Upgrade npm to 1.1.0-beta-10 (isaacs)
many doc updates (Ben Noordhuis, Jeremy Martin, koichik, Dave Irvine, -Seong-Rak Choi, Shannen, Adam Malcontenti-Wilson, koichik)
Fix segfault in node_http_parser.cc
dgram, timers: fix memory leaks (Ben Noordhuis, Yoshihiro Kikuchi)
repl: fix repl.start not passing the ignoreUndefined arg (Damon Oehlman)
#1980: Socket.pause null reference when called on a closed Stream (koichik)
#2263: XMLHttpRequest piped in a writable file stream hang (koichik)
#2069: http resource leak (koichik)
buffer.readInt global pollution fix (Phil Sung)
timers: fix performance regression (Ben Noordhuis)
#2308, #2246: node swallows openssl error on request (koichik)
#2114: timers: remove _idleTimeout from item in .unenroll() (James Hartig)
#2379: debugger: Request backtrace w/o refs (Fedor Indutny)
simple DTrace ustack helper (Dave Pacheco)
crypto: rewrite HexDecode without snprintf (Roman Shtylman)
crypto: don’t ignore DH init errors (Ben Noordhuis)
Source Code: http://nodejs.org/dist/v0.6.7/node-v0.6.7.tar.gz
- -Windows Installer: http://nodejs.org/dist/v0.6.7/node-v0.6.7.msi
- -Macintosh Installer: http://nodejs.org/dist/v0.6.7/node-v0.6.7.pkg
- -Website: http://nodejs.org/docs/v0.6.7/
- +2012.01.06, Version 0.6.7 (stable)
+ +V8 hash collision fix (Breaks MIPS) (Bert Belder, Erik Corry)
Upgrade V8 to 3.6.6.15
Upgrade npm to 1.1.0-beta-10 (isaacs)
many doc updates (Ben Noordhuis, Jeremy Martin, koichik, Dave Irvine, +Seong-Rak Choi, Shannen, Adam Malcontenti-Wilson, koichik)
Fix segfault in node_http_parser.cc
dgram, timers: fix memory leaks (Ben Noordhuis, Yoshihiro Kikuchi)
repl: fix repl.start not passing the ignoreUndefined arg (Damon Oehlman)
#1980: Socket.pause null reference when called on a closed Stream (koichik)
#2263: XMLHttpRequest piped in a writable file stream hang (koichik)
#2069: http resource leak (koichik)
buffer.readInt global pollution fix (Phil Sung)
timers: fix performance regression (Ben Noordhuis)
#2308, #2246: node swallows openssl error on request (koichik)
#2114: timers: remove _idleTimeout from item in .unenroll() (James Hartig)
#2379: debugger: Request backtrace w/o refs (Fedor Indutny)
simple DTrace ustack helper (Dave Pacheco)
crypto: rewrite HexDecode without snprintf (Roman Shtylman)
crypto: don’t ignore DH init errors (Ben Noordhuis)
Source Code: http://nodejs.org/dist/v0.6.7/node-v0.6.7.tar.gz
+ +Windows Installer: http://nodejs.org/dist/v0.6.7/node-v0.6.7.msi
+ +Macintosh Installer: http://nodejs.org/dist/v0.6.7/node-v0.6.7.pkg
+ +Website: http://nodejs.org/docs/v0.6.7/
+Documentation: http://nodejs.org/docs/v0.6.7/api/
diff --git a/doc/blog/release/node-v0-6-8.md b/doc/blog/release/node-v0-6-8.md index 55de31eb6..81f7ace94 100644 --- a/doc/blog/release/node-v0-6-8.md +++ b/doc/blog/release/node-v0-6-8.md @@ -6,26 +6,26 @@ status: publish category: release slug: node-v0-6-8 -2012.01.19, Version 0.6.8 (stable)
- -Update V8 to 3.6.6.19
Numeric key hash collision fix for V8 (Erik Corry, Fedor Indutny)
Add missing TTY key translations for F1-F5 on Windows (Brandon Benvie)
path.extname bugfix with . and .. paths (Bert Belder)
cluster: don't always kill the master on uncaughtException (Ben Noordhuis)
Update npm to 1.1.0-2 (isaacs)
typed arrays: set class name (Ben Noordhuis)
zlib binding cleanup (isaacs, Bert Belder)
dgram: use slab memory allocator (Michael Bernstein)
fix segfault #2473
#2521 60% improvement in fs.stat on Windows (Igor Zinkovsky)
Source Code: http://nodejs.org/dist/v0.6.8/node-v0.6.8.tar.gz
- -Windows Installer: http://nodejs.org/dist/v0.6.8/node-v0.6.8.msi
- -Macintosh Installer: http://nodejs.org/dist/v0.6.8/node-v0.6.8.pkg
- -Website: http://nodejs.org/docs/v0.6.8/
- +2012.01.19, Version 0.6.8 (stable)
+ +Update V8 to 3.6.6.19
Numeric key hash collision fix for V8 (Erik Corry, Fedor Indutny)
Add missing TTY key translations for F1-F5 on Windows (Brandon Benvie)
path.extname bugfix with . and .. paths (Bert Belder)
cluster: don't always kill the master on uncaughtException (Ben Noordhuis)
Update npm to 1.1.0-2 (isaacs)
typed arrays: set class name (Ben Noordhuis)
zlib binding cleanup (isaacs, Bert Belder)
dgram: use slab memory allocator (Michael Bernstein)
fix segfault #2473
#2521 60% improvement in fs.stat on Windows (Igor Zinkovsky)
Source Code: http://nodejs.org/dist/v0.6.8/node-v0.6.8.tar.gz
+ +Windows Installer: http://nodejs.org/dist/v0.6.8/node-v0.6.8.msi
+ +Macintosh Installer: http://nodejs.org/dist/v0.6.8/node-v0.6.8.pkg
+ +Website: http://nodejs.org/docs/v0.6.8/
+Documentation: http://nodejs.org/docs/v0.6.8/api/
diff --git a/doc/blog/release/node-v0-6-9.md b/doc/blog/release/node-v0-6-9.md index 05d992feb..6e95bfdd7 100644 --- a/doc/blog/release/node-v0-6-9.md +++ b/doc/blog/release/node-v0-6-9.md @@ -6,25 +6,25 @@ status: publish category: release slug: node-v0-6-9 -2012.01.27, Version 0.6.9 (stable)
- -dgram: Bring back missing functionality for Unix (Dan VerWeire, -Roman Shtylman, Ben Noordhuis)
-- Note: Windows UDP support not yet complete.
http: Fix parser memory leak (koichik)
zlib: Fix #2365 crashes on invalid input (Nicolas LaCasse)
module: fix --debug-brk on symlinked scripts (Fedor Indutny)
Documentation Restyling (Matthew Fitzsimmons)
Update npm to 1.1.0-3 (isaacs)
Windows: fix regression in stat() calls to C:\ (Bert Belder)
Source Code: http://nodejs.org/dist/v0.6.9/node-v0.6.9.tar.gz
- -Windows Installer: http://nodejs.org/dist/v0.6.9/node-v0.6.9.msi
- -Macintosh Installer: http://nodejs.org/dist/v0.6.9/node-v0.6.9.pkg
- -Website: http://nodejs.org/docs/v0.6.9/
- +2012.01.27, Version 0.6.9 (stable)
+ +dgram: Bring back missing functionality for Unix (Dan VerWeire, +Roman Shtylman, Ben Noordhuis)
+- Note: Windows UDP support not yet complete.
http: Fix parser memory leak (koichik)
zlib: Fix #2365 crashes on invalid input (Nicolas LaCasse)
module: fix --debug-brk on symlinked scripts (Fedor Indutny)
Documentation Restyling (Matthew Fitzsimmons)
Update npm to 1.1.0-3 (isaacs)
Windows: fix regression in stat() calls to C:\ (Bert Belder)
Source Code: http://nodejs.org/dist/v0.6.9/node-v0.6.9.tar.gz
+ +Windows Installer: http://nodejs.org/dist/v0.6.9/node-v0.6.9.msi
+ +Macintosh Installer: http://nodejs.org/dist/v0.6.9/node-v0.6.9.pkg
+ +Website: http://nodejs.org/docs/v0.6.9/
+Documentation: http://nodejs.org/docs/v0.6.9/api/
diff --git a/doc/blog/release/node-v0-7-0-unstable.md b/doc/blog/release/node-v0-7-0-unstable.md index 3036b9228..2bf3ad59c 100644 --- a/doc/blog/release/node-v0-7-0-unstable.md +++ b/doc/blog/release/node-v0-7-0-unstable.md @@ -6,24 +6,24 @@ status: publish category: release slug: node-v0-7-0-unstable -This is the first release in the unstable v0.7 series. Almost all users will want to remain using the stable v0.6 releases. - -2012.01.16, Version 0.7.0 (unstable) -2012.01.23, Version 0.7.1 (unstable)
- -Update V8 to 3.8.8
Install node-waf by default (Fedor Indutny)
crypto: Add ability to turn off PKCS padding (Ingmar Runge)
v8: implement VirtualMemory class on SunOS (Ben Noordhuis)
Add cluster.setupMaster (Andreas Madsen)
move path.exists* to fs.exists* (Maciej Małecki)
typed arrays: set class name (Ben Noordhuis)
libuv bug fixes (Igor Zinkovsky, Ben Noordhuis, Dan VerWeire)
Source: http://nodejs.org/dist/v0.7.1/node-v0.7.1.tar.gz
- -Windows Installer: http://nodejs.org/dist/v0.7.1/node-v0.7.1.msi
- -Macintosh Installer: http://nodejs.org/dist/v0.7.1/node-v0.7.1.pkg
- -Website: http://nodejs.org/docs/v0.7.1/
- +2012.01.23, Version 0.7.1 (unstable)
+ +Update V8 to 3.8.8
Install node-waf by default (Fedor Indutny)
crypto: Add ability to turn off PKCS padding (Ingmar Runge)
v8: implement VirtualMemory class on SunOS (Ben Noordhuis)
Add cluster.setupMaster (Andreas Madsen)
move path.exists* to fs.exists* (Maciej Małecki)
typed arrays: set class name (Ben Noordhuis)
libuv bug fixes (Igor Zinkovsky, Ben Noordhuis, Dan VerWeire)
Source: http://nodejs.org/dist/v0.7.1/node-v0.7.1.tar.gz
+ +Windows Installer: http://nodejs.org/dist/v0.7.1/node-v0.7.1.msi
+ +Macintosh Installer: http://nodejs.org/dist/v0.7.1/node-v0.7.1.pkg
+ +Website: http://nodejs.org/docs/v0.7.1/
+Documentation: http://nodejs.org/docs/v0.7.1/api/
diff --git a/doc/blog/release/node-v0-7-2-unstable.md b/doc/blog/release/node-v0-7-2-unstable.md index d5c1f8fb8..e25e1b442 100644 --- a/doc/blog/release/node-v0-7-2-unstable.md +++ b/doc/blog/release/node-v0-7-2-unstable.md @@ -6,27 +6,27 @@ status: publish category: release slug: node-v0-7-2-unstable -2012.02.01, Version 0.7.2 (unstable)
- -Update V8 to 3.8.9
Support for sharing streams across Isolates (Igor Zinkovsky)
#2636 - Fix case where http_parsers are freed too early (koichik)
url: Support for IPv6 addresses in URLs (Åukasz Walukiewicz)
child_process: Add disconnect() method to child processes (Andreas Madsen)
fs: add O_EXCL support, exclusive open file (Ben Noordhuis)
fs: more specific error messages (Tj Holowaychuk)
tty: emit 'unknown' key event if key sequence not found (Dan VerWeire, Nathan Rajlich)
build: compile release build too if BUILDTYPE=Debug (Ben Noordhuis)
module: fix --debug-brk on symlinked scripts (Fedor Indutny)
zlib: fix Failed to set dictionary issue (Fedor Indutny)
waf: predict target arch for OS X (Fedor Indutny)
Source Code: http://nodejs.org/dist/v0.7.2/node-v0.7.2.tar.gz
- -Windows Installer: http://nodejs.org/dist/v0.7.2/node-v0.7.2.msi
- -Macintosh Installer: http://nodejs.org/dist/v0.7.2/node-v0.7.2.pkg
- -Website: http://nodejs.org/docs/v0.7.2/
- +2012.02.01, Version 0.7.2 (unstable)
+ +Update V8 to 3.8.9
Support for sharing streams across Isolates (Igor Zinkovsky)
#2636 - Fix case where http_parsers are freed too early (koichik)
url: Support for IPv6 addresses in URLs (Åukasz Walukiewicz)
child_process: Add disconnect() method to child processes (Andreas Madsen)
fs: add O_EXCL support, exclusive open file (Ben Noordhuis)
fs: more specific error messages (Tj Holowaychuk)
tty: emit 'unknown' key event if key sequence not found (Dan VerWeire, Nathan Rajlich)
build: compile release build too if BUILDTYPE=Debug (Ben Noordhuis)
module: fix --debug-brk on symlinked scripts (Fedor Indutny)
zlib: fix Failed to set dictionary issue (Fedor Indutny)
waf: predict target arch for OS X (Fedor Indutny)
Source Code: http://nodejs.org/dist/v0.7.2/node-v0.7.2.tar.gz
+ +Windows Installer: http://nodejs.org/dist/v0.7.2/node-v0.7.2.msi
+ +Macintosh Installer: http://nodejs.org/dist/v0.7.2/node-v0.7.2.pkg
+ +Website: http://nodejs.org/docs/v0.7.2/
+Documentation: http://nodejs.org/docs/v0.7.2/api/
diff --git a/doc/blog/release/node-v0-7-3.md b/doc/blog/release/node-v0-7-3.md index a0d93df12..e4942bd68 100644 --- a/doc/blog/release/node-v0-7-3.md +++ b/doc/blog/release/node-v0-7-3.md @@ -6,34 +6,34 @@ status: publish category: release slug: node-v0-7-3 -2012.02.07, Version 0.7.3 (unstable) - -
-Upgrade V8 to 3.9.2
-Revert support for isolates. (Ben Noordhuis)
-cluster: Cleanup docs, event handling, and process.disconnect (Andreas Madsen)
-gyp_addon: link with node.lib on Windows (Nathan Rajlich)
-http: fix case where http-parser is freed twice (koichik)
-Windows: disable RTTI and exceptions (Bert Belder)
-Source Code: http://nodejs.org/dist/v0.7.3/node-v0.7.3.tar.gz - -
-Windows Installer: http://nodejs.org/dist/v0.7.3/node-v0.7.3.msi - -
-Macintosh Installer: http://nodejs.org/dist/v0.7.3/node-v0.7.3.pkg - -
-Website: http://nodejs.org/docs/v0.7.3/ - -
-Documentation: http://nodejs.org/docs/v0.7.3/api/ +
2012.02.07, Version 0.7.3 (unstable) + +
+Upgrade V8 to 3.9.2
+Revert support for isolates. (Ben Noordhuis)
+cluster: Cleanup docs, event handling, and process.disconnect (Andreas Madsen)
+gyp_addon: link with node.lib on Windows (Nathan Rajlich)
+http: fix case where http-parser is freed twice (koichik)
+Windows: disable RTTI and exceptions (Bert Belder)
+Source Code: http://nodejs.org/dist/v0.7.3/node-v0.7.3.tar.gz + +
+Windows Installer: http://nodejs.org/dist/v0.7.3/node-v0.7.3.msi + +
+Macintosh Installer: http://nodejs.org/dist/v0.7.3/node-v0.7.3.pkg + +
+Website: http://nodejs.org/docs/v0.7.3/ + +
+Documentation: http://nodejs.org/docs/v0.7.3/api/
diff --git a/doc/blog/release/node-version-0-6-19-stable.md b/doc/blog/release/node-version-0-6-19-stable.md index 3a29556c5..cb8febe35 100644 --- a/doc/blog/release/node-version-0-6-19-stable.md +++ b/doc/blog/release/node-version-0-6-19-stable.md @@ -6,56 +6,56 @@ status: publish category: release slug: node-version-0-6-19-stable -2012.06.06 Version 0.6.19 (stable) - -
-npm: upgrade to 1.1.24
-fs: no end emit after createReadStream.pause() (Andreas Madsen)
-vm: cleanup module memory leakage (Marcel Laverdet)
-unix: fix loop starvation under high network load (Ben Noordhuis)
-unix: remove abort() in ev_unref() (Ben Noordhuis)
-windows/tty: never report error after forcibly aborting line-buffered read (Bert Belder)
-windows: skip GetFileAttributes call when opening a file (Bert Belder)
-Source Code: http://nodejs.org/dist/v0.6.19/node-v0.6.19.tar.gz - -
-Windows Installer: http://nodejs.org/dist/v0.6.19/node-v0.6.19.msi - -
-Windows x64 Files: http://nodejs.org/dist/v0.6.19/x64/ - -
-Macintosh Installer (Universal): http://nodejs.org/dist/v0.6.19/node-v0.6.19.pkg - -
-Other release files: http://nodejs.org/dist/v0.6.19/ - -
-Website: http://nodejs.org/docs/v0.6.19/ - -
-Documentation: http://nodejs.org/docs/v0.6.19/api/ -
- -Shasums:
-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 +2012.06.06 Version 0.6.19 (stable) + +
+
npm: upgrade to 1.1.24
+fs: no end emit after createReadStream.pause() (Andreas Madsen)
+vm: cleanup module memory leakage (Marcel Laverdet)
+unix: fix loop starvation under high network load (Ben Noordhuis)
+unix: remove abort() in ev_unref() (Ben Noordhuis)
+windows/tty: never report error after forcibly aborting line-buffered read (Bert Belder)
+windows: skip GetFileAttributes call when opening a file (Bert Belder)
+Source Code: http://nodejs.org/dist/v0.6.19/node-v0.6.19.tar.gz + +
+Windows Installer: http://nodejs.org/dist/v0.6.19/node-v0.6.19.msi + +
+Windows x64 Files: http://nodejs.org/dist/v0.6.19/x64/ + +
+Macintosh Installer (Universal): http://nodejs.org/dist/v0.6.19/node-v0.6.19.pkg + +
+Other release files: http://nodejs.org/dist/v0.6.19/ + +
+Website: http://nodejs.org/docs/v0.6.19/ + +
+Documentation: http://nodejs.org/docs/v0.6.19/api/ +
+ +Shasums:
+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.pdbdiff --git a/doc/blog/release/node-version-0-7-9-unstable.md b/doc/blog/release/node-version-0-7-9-unstable.md index cb077d625..74076c04c 100644 --- a/doc/blog/release/node-version-0-7-9-unstable.md +++ b/doc/blog/release/node-version-0-7-9-unstable.md @@ -6,68 +6,68 @@ status: publish category: release slug: node-version-0-7-9-unstable -
2012.05.28, Version 0.7.9 (unstable) - -
-Upgrade V8 to 3.11.1
-Upgrade npm to 1.1.23
-uv: rework reference counting scheme (Ben Noordhuis)
-uv: add interface for joining external event loops (Bert Belder)
-repl, readline: Handle Ctrl+Z and SIGCONT better (Nathan Rajlich)
-fs: 64bit offsets for fs calls (Igor Zinkovsky)
-fs: add sync open flags 'rs' and 'rs+' (Kevin Bowman)
-windows: enable creating directory junctions with fs.symlink (Igor Zinkovsky, Bert Belder)
-windows: fix fs.lstat to properly detect symlinks. (Igor Zinkovsky)
-Fix #3270 Escape url.parse delims (isaacs)
-http: make http.get() accept a URL (Adam Malcontenti-Wilson)
-Cleanup vm module memory leakage (Marcel Laverdet)
-Optimize writing strings with Socket.write (Bert Belder)
-add support for CESU-8 and UTF-16LE encodings (koichik)
-path: add path.sep to get the path separator. (Yi, EungJun)
-net, http: add backlog parameter to .listen() (Erik Dubbelboer)
-debugger: support mirroring Date objects (Fedor Indutny)
-addon: add AtExit() function (Ben Noordhuis)
-net: signal localAddress bind failure in connect (Brian Schroeder)
-util: handle non-string return value in .inspect() (Alex Kocharin)
-Source Code: http://nodejs.org/dist/v0.7.9/node-v0.7.9.tar.gz - -
-Windows Installer: http://nodejs.org/dist/v0.7.9/node-v0.7.9.msi - -
-Windows x64 Files: http://nodejs.org/dist/v0.7.9/x64/ - -
-Macintosh Installer (Universal): http://nodejs.org/dist/v0.7.9/node-v0.7.9.pkg - -
-Other release files: http://nodejs.org/dist/v0.7.9/ - -
-Website: http://nodejs.org/docs/v0.7.9/ - -
-Documentation: http://nodejs.org/docs/v0.7.9/api/ +
2012.05.28, Version 0.7.9 (unstable) + +
+Upgrade V8 to 3.11.1
+Upgrade npm to 1.1.23
+uv: rework reference counting scheme (Ben Noordhuis)
+uv: add interface for joining external event loops (Bert Belder)
+repl, readline: Handle Ctrl+Z and SIGCONT better (Nathan Rajlich)
+fs: 64bit offsets for fs calls (Igor Zinkovsky)
+fs: add sync open flags 'rs' and 'rs+' (Kevin Bowman)
+windows: enable creating directory junctions with fs.symlink (Igor Zinkovsky, Bert Belder)
+windows: fix fs.lstat to properly detect symlinks. (Igor Zinkovsky)
+Fix #3270 Escape url.parse delims (isaacs)
+http: make http.get() accept a URL (Adam Malcontenti-Wilson)
+Cleanup vm module memory leakage (Marcel Laverdet)
+Optimize writing strings with Socket.write (Bert Belder)
+add support for CESU-8 and UTF-16LE encodings (koichik)
+path: add path.sep to get the path separator. (Yi, EungJun)
+net, http: add backlog parameter to .listen() (Erik Dubbelboer)
+debugger: support mirroring Date objects (Fedor Indutny)
+addon: add AtExit() function (Ben Noordhuis)
+net: signal localAddress bind failure in connect (Brian Schroeder)
+util: handle non-string return value in .inspect() (Alex Kocharin)
+Source Code: http://nodejs.org/dist/v0.7.9/node-v0.7.9.tar.gz + +
+Windows Installer: http://nodejs.org/dist/v0.7.9/node-v0.7.9.msi + +
+Windows x64 Files: http://nodejs.org/dist/v0.7.9/x64/ + +
+Macintosh Installer (Universal): http://nodejs.org/dist/v0.7.9/node-v0.7.9.pkg + +
+Other release files: http://nodejs.org/dist/v0.7.9/ + +
+Website: http://nodejs.org/docs/v0.7.9/ + +
+Documentation: http://nodejs.org/docs/v0.7.9/api/
diff --git a/doc/blog/release/version-0-6-11-stable.md b/doc/blog/release/version-0-6-11-stable.md index d57068f27..15fbe337c 100644 --- a/doc/blog/release/version-0-6-11-stable.md +++ b/doc/blog/release/version-0-6-11-stable.md @@ -6,59 +6,59 @@ status: publish category: release slug: version-0-6-11-stable -2012.02.17 Version 0.6.11 (stable) - -
-http: allow multiple WebSocket RFC6455 headers (Einar Otto Stangvik)
-http: allow multiple WWW-Authenticate headers (Ben Noordhuis)
-windows: support unicode argv and environment variables (Bert Belder)
-tls: mitigate session renegotiation attacks (Ben Noordhuis)
-tcp, pipe: don't assert on uv_accept() errors (Ben Noordhuis)
-tls: Allow establishing secure connection on the existing socket (koichik)
-dgram: handle close of dgram socket before DNS lookup completes (Seth Fitzsimmons)
-windows: Support half-duplex pipes (Igor Zinkovsky)
-build: disable omit-frame-pointer on solaris systems (Dave Pacheco)
-debugger: fix --debug-brk (Ben Noordhuis)
-net: fix large file downloads failing (koichik)
-fs: fix ReadStream failure to read from existing fd (Christopher Jeffrey)
-net: destroy socket on DNS error (Stefan Rusu)
-dtrace: add missing translator (Dave Pacheco)
-unix: don't flush tty on switch to raw mode (Ben Noordhuis)
-windows: reset brightness when reverting to default text color (Bert Belder)
-npm: update to 1.1.1
- -- Update which, fstream, mkdirp, request, and rimraf
- Fix #2123 Set path properly for lifecycle scripts on windows
- Mark the root as seen, so we don't recurse into it. Fixes #1838. (Martin Cooper)
Source Code: http://nodejs.org/dist/v0.6.11/node-v0.6.11.tar.gz - -
-Windows Installer: http://nodejs.org/dist/v0.6.11/node-v0.6.11.msi - -
-Macintosh Installer: http://nodejs.org/dist/v0.6.11/node-v0.6.11.pkg - -
-Website: http://nodejs.org/docs/v0.6.11/ - -
-Documentation: http://nodejs.org/docs/v0.6.11/api/ +
2012.02.17 Version 0.6.11 (stable) + +
+http: allow multiple WebSocket RFC6455 headers (Einar Otto Stangvik)
+http: allow multiple WWW-Authenticate headers (Ben Noordhuis)
+windows: support unicode argv and environment variables (Bert Belder)
+tls: mitigate session renegotiation attacks (Ben Noordhuis)
+tcp, pipe: don't assert on uv_accept() errors (Ben Noordhuis)
+tls: Allow establishing secure connection on the existing socket (koichik)
+dgram: handle close of dgram socket before DNS lookup completes (Seth Fitzsimmons)
+windows: Support half-duplex pipes (Igor Zinkovsky)
+build: disable omit-frame-pointer on solaris systems (Dave Pacheco)
+debugger: fix --debug-brk (Ben Noordhuis)
+net: fix large file downloads failing (koichik)
+fs: fix ReadStream failure to read from existing fd (Christopher Jeffrey)
+net: destroy socket on DNS error (Stefan Rusu)
+dtrace: add missing translator (Dave Pacheco)
+unix: don't flush tty on switch to raw mode (Ben Noordhuis)
+windows: reset brightness when reverting to default text color (Bert Belder)
+npm: update to 1.1.1
+ +- Update which, fstream, mkdirp, request, and rimraf
- Fix #2123 Set path properly for lifecycle scripts on windows
- Mark the root as seen, so we don't recurse into it. Fixes #1838. (Martin Cooper)
Source Code: http://nodejs.org/dist/v0.6.11/node-v0.6.11.tar.gz + +
+Windows Installer: http://nodejs.org/dist/v0.6.11/node-v0.6.11.msi + +
+Macintosh Installer: http://nodejs.org/dist/v0.6.11/node-v0.6.11.pkg + +
+Website: http://nodejs.org/docs/v0.6.11/ + +
+Documentation: http://nodejs.org/docs/v0.6.11/api/
diff --git a/doc/blog/release/version-0-6-12-stable.md b/doc/blog/release/version-0-6-12-stable.md index bd20ef7da..3e5acd61c 100644 --- a/doc/blog/release/version-0-6-12-stable.md +++ b/doc/blog/release/version-0-6-12-stable.md @@ -6,61 +6,61 @@ status: publish category: release slug: version-0-6-12-stable -2012.03.02 Version 0.6.12 (stable) - -
-Upgrade V8 to 3.6.6.24
-dtrace ustack helper improvements (Dave Pacheco)
-API Documentation refactor (isaacs)
-#2827 net: fix race write() before and after connect() (koichik)
-#2554 #2567 throw if fs args for 'start' or 'end' are strings (AJ ONeal)
-punycode: Update to v1.0.0 (Mathias Bynens)
-Make a fat binary for the OS X pkg (isaacs)
-Fix hang on accessing process.stdin (isaacs)
-repl: make tab completion work on non-objects (Nathan Rajlich)
-Fix fs.watch on OS X (Ben Noordhuis)
-Fix #2515 nested setTimeouts cause premature process exit (Ben Noordhuis)
-windows: fix time conversion in stat (Igor Zinkovsky)
-windows: fs: handle EOF in read (Brandon Philips)
-windows: avoid IOCP short-circuit on non-ifs lsps (Igor Zinkovsky)
-Upgrade npm to 1.1.4 (isaacs)
-
-- windows fixes
-- Bundle nested bundleDependencies properly
-- install: support --save with url install targets
-- shrinkwrap: behave properly with url-installed modules
-- support installing uncompressed tars or single file modules from urls etc.
-- don't run make clean on rebuild
-- support HTTPS-over-HTTP proxy tunneling
-
Source Code: http://nodejs.org/dist/v0.6.12/node-v0.6.12.tar.gz - -
-Windows Installer: http://nodejs.org/dist/v0.6.12/node-v0.6.12.msi - -
-Macintosh Installer: http://nodejs.org/dist/v0.6.12/node-v0.6.12.pkg - -
-Website: http://nodejs.org/docs/v0.6.12/ - -
-Documentation: http://nodejs.org/docs/v0.6.12/api/ +
2012.03.02 Version 0.6.12 (stable) + +
+Upgrade V8 to 3.6.6.24
+dtrace ustack helper improvements (Dave Pacheco)
+API Documentation refactor (isaacs)
+#2827 net: fix race write() before and after connect() (koichik)
+#2554 #2567 throw if fs args for 'start' or 'end' are strings (AJ ONeal)
+punycode: Update to v1.0.0 (Mathias Bynens)
+Make a fat binary for the OS X pkg (isaacs)
+Fix hang on accessing process.stdin (isaacs)
+repl: make tab completion work on non-objects (Nathan Rajlich)
+Fix fs.watch on OS X (Ben Noordhuis)
+Fix #2515 nested setTimeouts cause premature process exit (Ben Noordhuis)
+windows: fix time conversion in stat (Igor Zinkovsky)
+windows: fs: handle EOF in read (Brandon Philips)
+windows: avoid IOCP short-circuit on non-ifs lsps (Igor Zinkovsky)
+Upgrade npm to 1.1.4 (isaacs)
+
+- windows fixes
+- Bundle nested bundleDependencies properly
+- install: support --save with url install targets
+- shrinkwrap: behave properly with url-installed modules
+- support installing uncompressed tars or single file modules from urls etc.
+- don't run make clean on rebuild
+- support HTTPS-over-HTTP proxy tunneling
+
Source Code: http://nodejs.org/dist/v0.6.12/node-v0.6.12.tar.gz + +
+Windows Installer: http://nodejs.org/dist/v0.6.12/node-v0.6.12.msi + +
+Macintosh Installer: http://nodejs.org/dist/v0.6.12/node-v0.6.12.pkg + +
+Website: http://nodejs.org/docs/v0.6.12/ + +
+Documentation: http://nodejs.org/docs/v0.6.12/api/
diff --git a/doc/blog/release/version-0-6-13-stable.md b/doc/blog/release/version-0-6-13-stable.md index 2561c1df4..356c0ae7d 100644 --- a/doc/blog/release/version-0-6-13-stable.md +++ b/doc/blog/release/version-0-6-13-stable.md @@ -6,45 +6,45 @@ status: publish category: release slug: version-0-6-13-stable -2012.03.15 Version 0.6.13 (stable) - -
-Windows: Many libuv test fixes (Bert Belder)
-Windows: avoid uv_guess_handle crash in when fd < 0 (Bert Belder)
-Map EBUSY and ENOTEMPTY errors (Bert Belder)
-Windows: include syscall in fs errors (Bert Belder)
-Fix fs.watch ENOSYS on Linux kernel version mismatch (Ben Noordhuis)
-Update npm to 1.1.9
-
-- upgrade node-gyp to 0.3.5 (Nathan Rajlich)
-- Fix isaacs/npm#2249 Add cache-max and cache-min configs
-- Properly redirect across https/http registry requests
-- log config usage if undefined key in set function (Kris Windham)
-- Add support for os/cpu fields in package.json (Adam Blackburn)
-- Automatically node-gyp packages containing a binding.gyp
-- Fix failures unpacking in UNC shares
-- Never create un-listable directories
-- Handle cases where an optionalDependency fails to build
-
Source Code: http://nodejs.org/dist/v0.6.13/node-v0.6.13.tar.gz - -
-Windows Installer: http://nodejs.org/dist/v0.6.13/node-v0.6.13.msi - -
-Macintosh Installer: http://nodejs.org/dist/v0.6.13/node-v0.6.13.pkg - -
-Website: http://nodejs.org/docs/v0.6.13/ - -
-Documentation: http://nodejs.org/docs/v0.6.13/api/ +
2012.03.15 Version 0.6.13 (stable) + +
+Windows: Many libuv test fixes (Bert Belder)
+Windows: avoid uv_guess_handle crash in when fd < 0 (Bert Belder)
+Map EBUSY and ENOTEMPTY errors (Bert Belder)
+Windows: include syscall in fs errors (Bert Belder)
+Fix fs.watch ENOSYS on Linux kernel version mismatch (Ben Noordhuis)
+Update npm to 1.1.9
+
+- upgrade node-gyp to 0.3.5 (Nathan Rajlich)
+- Fix isaacs/npm#2249 Add cache-max and cache-min configs
+- Properly redirect across https/http registry requests
+- log config usage if undefined key in set function (Kris Windham)
+- Add support for os/cpu fields in package.json (Adam Blackburn)
+- Automatically node-gyp packages containing a binding.gyp
+- Fix failures unpacking in UNC shares
+- Never create un-listable directories
+- Handle cases where an optionalDependency fails to build
+
Source Code: http://nodejs.org/dist/v0.6.13/node-v0.6.13.tar.gz + +
+Windows Installer: http://nodejs.org/dist/v0.6.13/node-v0.6.13.msi + +
+Macintosh Installer: http://nodejs.org/dist/v0.6.13/node-v0.6.13.pkg + +
+Website: http://nodejs.org/docs/v0.6.13/ + +
+Documentation: http://nodejs.org/docs/v0.6.13/api/
diff --git a/doc/blog/release/version-0-6-14-stable.md b/doc/blog/release/version-0-6-14-stable.md index ba5183414..4f33a2697 100644 --- a/doc/blog/release/version-0-6-14-stable.md +++ b/doc/blog/release/version-0-6-14-stable.md @@ -6,50 +6,50 @@ status: publish category: release slug: version-0-6-14-stable -2012.03.22 Version 0.6.14 (stable) - -
-net: don't crash when queued write fails (Igor Zinkovsky)
-sunos: fix EMFILE on process.memoryUsage() (Bryan Cantrill)
-crypto: fix compile-time error with openssl 0.9.7e (Ben Noordhuis)
-unix: ignore ECONNABORTED errors from accept() (Ben Noordhuis)
-Add UV_ENOSPC and mappings to it (Bert Belder)
-http-parser: Fix response body is not read (koichik)
-Upgrade npm to 1.1.12
-
-- upgrade node-gyp to 0.3.7
-- work around AV-locked directories on Windows
-- Fix isaacs/npm#2293 Don't try to 'uninstall' /
-- Exclude symbolic links from packages.
-- Fix isaacs/npm#2275 Spurious 'unresolvable cycle' error.
-- Exclude/include dot files as if they were normal files
-
Source Code: http://nodejs.org/dist/v0.6.14/node-v0.6.14.tar.gz - -
-Windows Installer: http://nodejs.org/dist/v0.6.14/node-v0.6.14.msi - -
-Windows x64 Files: http://nodejs.org/dist/v0.6.14/x64/ - -
-Macintosh Installer (Universal): http://nodejs.org/dist/v0.6.14/node-v0.6.14.pkg - -
-Other release files: http://nodejs.org/dist/v0.6.14/ - -
-Website: http://nodejs.org/docs/v0.6.14/ - -
-Documentation: http://nodejs.org/docs/v0.6.14/api/ +
2012.03.22 Version 0.6.14 (stable) + +
+net: don't crash when queued write fails (Igor Zinkovsky)
+sunos: fix EMFILE on process.memoryUsage() (Bryan Cantrill)
+crypto: fix compile-time error with openssl 0.9.7e (Ben Noordhuis)
+unix: ignore ECONNABORTED errors from accept() (Ben Noordhuis)
+Add UV_ENOSPC and mappings to it (Bert Belder)
+http-parser: Fix response body is not read (koichik)
+Upgrade npm to 1.1.12
+
+- upgrade node-gyp to 0.3.7
+- work around AV-locked directories on Windows
+- Fix isaacs/npm#2293 Don't try to 'uninstall' /
+- Exclude symbolic links from packages.
+- Fix isaacs/npm#2275 Spurious 'unresolvable cycle' error.
+- Exclude/include dot files as if they were normal files
+
Source Code: http://nodejs.org/dist/v0.6.14/node-v0.6.14.tar.gz + +
+Windows Installer: http://nodejs.org/dist/v0.6.14/node-v0.6.14.msi + +
+Windows x64 Files: http://nodejs.org/dist/v0.6.14/x64/ + +
+Macintosh Installer (Universal): http://nodejs.org/dist/v0.6.14/node-v0.6.14.pkg + +
+Other release files: http://nodejs.org/dist/v0.6.14/ + +
+Website: http://nodejs.org/docs/v0.6.14/ + +
+Documentation: http://nodejs.org/docs/v0.6.14/api/
diff --git a/doc/blog/release/version-0-6-15-stable.md b/doc/blog/release/version-0-6-15-stable.md index e6f0502f7..4196876fe 100644 --- a/doc/blog/release/version-0-6-15-stable.md +++ b/doc/blog/release/version-0-6-15-stable.md @@ -6,48 +6,48 @@ status: publish category: release slug: version-0-6-15-stable -2012.04.09 Version 0.6.15 (stable) - -
-Update npm to 1.1.16
-Show licenses in binary installers.
-unix: add uv_fs_read64, uv_fs_write64 and uv_fs_ftruncate64 (Ben Noordhuis)
-add 64bit offset fs functions (Igor Zinkovsky)
-windows: don't report ENOTSOCK when attempting to bind an udp handle twice (Bert Belder)
-windows: backport pipe-connect-to-file fixes from master (Bert Belder)
-windows: never call fs event callbacks after closing the watcher (Bert Belder)
-fs.readFile: don't make the callback before the fd is closed (Bert Belder)
-windows: use 64bit offsets for uv_fs apis (Igor Zinkovsky)
-Fix #2061: segmentation fault on OS X due to stat size mismatch (Ben Noordhuis)
-Source Code: http://nodejs.org/dist/v0.6.15/node-v0.6.15.tar.gz - -
-Windows Installer: http://nodejs.org/dist/v0.6.15/node-v0.6.15.msi - -
-Windows x64 Files: http://nodejs.org/dist/v0.6.15/x64/ - -
-Macintosh Installer (Universal): http://nodejs.org/dist/v0.6.15/node-v0.6.15.pkg - -
-Other release files: http://nodejs.org/dist/v0.6.15/ - -
-Website: http://nodejs.org/docs/v0.6.15/ - -
-Documentation: http://nodejs.org/docs/v0.6.15/api/ +
2012.04.09 Version 0.6.15 (stable) + +
+Update npm to 1.1.16
+Show licenses in binary installers.
+unix: add uv_fs_read64, uv_fs_write64 and uv_fs_ftruncate64 (Ben Noordhuis)
+add 64bit offset fs functions (Igor Zinkovsky)
+windows: don't report ENOTSOCK when attempting to bind an udp handle twice (Bert Belder)
+windows: backport pipe-connect-to-file fixes from master (Bert Belder)
+windows: never call fs event callbacks after closing the watcher (Bert Belder)
+fs.readFile: don't make the callback before the fd is closed (Bert Belder)
+windows: use 64bit offsets for uv_fs apis (Igor Zinkovsky)
+Fix #2061: segmentation fault on OS X due to stat size mismatch (Ben Noordhuis)
+Source Code: http://nodejs.org/dist/v0.6.15/node-v0.6.15.tar.gz + +
+Windows Installer: http://nodejs.org/dist/v0.6.15/node-v0.6.15.msi + +
+Windows x64 Files: http://nodejs.org/dist/v0.6.15/x64/ + +
+Macintosh Installer (Universal): http://nodejs.org/dist/v0.6.15/node-v0.6.15.pkg + +
+Other release files: http://nodejs.org/dist/v0.6.15/ + +
+Website: http://nodejs.org/docs/v0.6.15/ + +
+Documentation: http://nodejs.org/docs/v0.6.15/api/
diff --git a/doc/blog/release/version-0-6-16-stable.md b/doc/blog/release/version-0-6-16-stable.md index 69f8b3170..980296c1a 100644 --- a/doc/blog/release/version-0-6-16-stable.md +++ b/doc/blog/release/version-0-6-16-stable.md @@ -6,54 +6,54 @@ status: publish category: release slug: version-0-6-16-stable -2012.04.30 Version 0.6.16 (stable) - -
-Upgrade V8 to 3.6.6.25
-Upgrade npm to 1.1.18
-Windows: add mappings for UV_ENOENT (Bert Belder)
-linux: add IN_MOVE_SELF to inotify event mask (Ben Noordhuis)
-unix: call pipe handle connection cb on accept() error (Ben Noordhuis)
-unix: handle EWOULDBLOCK (Ben Noordhuis)
-map EWOULDBLOCK to UV_EAGAIN (Ben Noordhuis)
-Map ENOMEM to UV_ENOMEM (isaacs)
-Child process: support the gid and uid options (Bert Belder)
test: cluster: add worker death event test (Ben Noordhuis)
-typo in node_http_parser (isaacs)
-http_parser: Eat CRLF between requests, even on connection:close. (Ben Noordhuis)
-don't check return value of unsetenv (Ben Noordhuis)
-Source Code: http://nodejs.org/dist/v0.6.16/node-v0.6.16.tar.gz - -
-Windows Installer: http://nodejs.org/dist/v0.6.16/node-v0.6.16.msi - -
-Windows x64 Files: http://nodejs.org/dist/v0.6.16/x64/ - -
-Macintosh Installer (Universal): http://nodejs.org/dist/v0.6.16/node-v0.6.16.pkg - -
-Other release files: http://nodejs.org/dist/v0.6.16/ - -
-Website: http://nodejs.org/docs/v0.6.16/ - -
-Documentation: http://nodejs.org/docs/v0.6.16/api/ +
2012.04.30 Version 0.6.16 (stable) + +
+Upgrade V8 to 3.6.6.25
+Upgrade npm to 1.1.18
+Windows: add mappings for UV_ENOENT (Bert Belder)
+linux: add IN_MOVE_SELF to inotify event mask (Ben Noordhuis)
+unix: call pipe handle connection cb on accept() error (Ben Noordhuis)
+unix: handle EWOULDBLOCK (Ben Noordhuis)
+map EWOULDBLOCK to UV_EAGAIN (Ben Noordhuis)
+Map ENOMEM to UV_ENOMEM (isaacs)
+Child process: support the gid and uid options (Bert Belder)
test: cluster: add worker death event test (Ben Noordhuis)
+typo in node_http_parser (isaacs)
+http_parser: Eat CRLF between requests, even on connection:close. (Ben Noordhuis)
+don't check return value of unsetenv (Ben Noordhuis)
+Source Code: http://nodejs.org/dist/v0.6.16/node-v0.6.16.tar.gz + +
+Windows Installer: http://nodejs.org/dist/v0.6.16/node-v0.6.16.msi + +
+Windows x64 Files: http://nodejs.org/dist/v0.6.16/x64/ + +
+Macintosh Installer (Universal): http://nodejs.org/dist/v0.6.16/node-v0.6.16.pkg + +
+Other release files: http://nodejs.org/dist/v0.6.16/ + +
+Website: http://nodejs.org/docs/v0.6.16/ + +
+Documentation: http://nodejs.org/docs/v0.6.16/api/
diff --git a/doc/blog/release/version-0-6-17-stable.md b/doc/blog/release/version-0-6-17-stable.md index 3512e1df2..321244354 100644 --- a/doc/blog/release/version-0-6-17-stable.md +++ b/doc/blog/release/version-0-6-17-stable.md @@ -6,42 +6,42 @@ status: publish category: release slug: version-0-6-17-stable -2012.05.04 Version 0.6.17 (stable) - -
-Upgrade npm to 1.1.21
-uv: Add support for EROFS errors (Ben Noordhuis, Maciej Małecki)
-uv: Add support for EIO and ENOSPC errors (Fedor Indutny)
-windows: Add support for EXDEV errors (Bert Belder)
-http: Fix client memory leaks (isaacs, Vincent Voyer)
-fs: fix file descriptor leak in sync functions (Ben Noordhuis)
-fs: fix ReadStream / WriteStream double close bug (Ben Noordhuis)
-Source Code: http://nodejs.org/dist/v0.6.17/node-v0.6.17.tar.gz - -
-Windows Installer: http://nodejs.org/dist/v0.6.17/node-v0.6.17.msi - -
-Windows x64 Files: http://nodejs.org/dist/v0.6.17/x64/ - -
-Macintosh Installer (Universal): http://nodejs.org/dist/v0.6.17/node-v0.6.17.pkg - -
-Other release files: http://nodejs.org/dist/v0.6.17/ - -
-Website: http://nodejs.org/docs/v0.6.17/ - -
-Documentation: http://nodejs.org/docs/v0.6.17/api/ +
2012.05.04 Version 0.6.17 (stable) + +
+Upgrade npm to 1.1.21
+uv: Add support for EROFS errors (Ben Noordhuis, Maciej Małecki)
+uv: Add support for EIO and ENOSPC errors (Fedor Indutny)
+windows: Add support for EXDEV errors (Bert Belder)
+http: Fix client memory leaks (isaacs, Vincent Voyer)
+fs: fix file descriptor leak in sync functions (Ben Noordhuis)
+fs: fix ReadStream / WriteStream double close bug (Ben Noordhuis)
+Source Code: http://nodejs.org/dist/v0.6.17/node-v0.6.17.tar.gz + +
+Windows Installer: http://nodejs.org/dist/v0.6.17/node-v0.6.17.msi + +
+Windows x64 Files: http://nodejs.org/dist/v0.6.17/x64/ + +
+Macintosh Installer (Universal): http://nodejs.org/dist/v0.6.17/node-v0.6.17.pkg + +
+Other release files: http://nodejs.org/dist/v0.6.17/ + +
+Website: http://nodejs.org/docs/v0.6.17/ + +
+Documentation: http://nodejs.org/docs/v0.6.17/api/
diff --git a/doc/blog/release/version-0-6-18-stable.md b/doc/blog/release/version-0-6-18-stable.md index 0cf179bfc..fe0c1f166 100644 --- a/doc/blog/release/version-0-6-18-stable.md +++ b/doc/blog/release/version-0-6-18-stable.md @@ -6,54 +6,54 @@ status: publish category: release slug: version-0-6-18-stable -2012.05.15 Version 0.6.18 (stable) - -
-windows: skip GetFileAttributes call when opening a file (Bert Belder)
-crypto: add PKCS12/PFX support (Sambasiva Suda)
-#3240: child_process: delete NODE_CHANNEL_FD from env in spawn (Ben Noordhuis)
-windows: add test for path.normalize with UNC paths (Bert Belder)
-windows: make path.normalize convert all slashes to backslashes (Bert Belder)
-fs: Automatically close FSWatcher on error (Bert Belder)
-#3258: fs.ReadStream.pause() emits duplicate data event (koichik)
-pipe_wrap: don't assert() on pipe accept errors (Ben Noordhuis)
-Better exception output for module load and process.nextTick (Felix Geisendörfer)
-zlib: fix error reporting (Ben Noordhuis)
-http: Don't destroy on timeout (isaacs)
-#3231: http: Don't try to emit error on a null'ed req object (isaacs)
-#3236: http: Refactor ClientRequest.onSocket (isaacs)
-Source Code: http://nodejs.org/dist/v0.6.18/node-v0.6.18.tar.gz - -
-Windows Installer: http://nodejs.org/dist/v0.6.18/node-v0.6.18.msi - -
-Windows x64 Files: http://nodejs.org/dist/v0.6.18/x64/ - -
-Macintosh Installer (Universal): http://nodejs.org/dist/v0.6.18/node-v0.6.18.pkg - -
-Other release files: http://nodejs.org/dist/v0.6.18/ - -
-Website: http://nodejs.org/docs/v0.6.18/ - -
-Documentation: http://nodejs.org/docs/v0.6.18/api/ +
2012.05.15 Version 0.6.18 (stable) + +
+windows: skip GetFileAttributes call when opening a file (Bert Belder)
+crypto: add PKCS12/PFX support (Sambasiva Suda)
+#3240: child_process: delete NODE_CHANNEL_FD from env in spawn (Ben Noordhuis)
+windows: add test for path.normalize with UNC paths (Bert Belder)
+windows: make path.normalize convert all slashes to backslashes (Bert Belder)
+fs: Automatically close FSWatcher on error (Bert Belder)
+#3258: fs.ReadStream.pause() emits duplicate data event (koichik)
+pipe_wrap: don't assert() on pipe accept errors (Ben Noordhuis)
+Better exception output for module load and process.nextTick (Felix Geisendörfer)
+zlib: fix error reporting (Ben Noordhuis)
+http: Don't destroy on timeout (isaacs)
+#3231: http: Don't try to emit error on a null'ed req object (isaacs)
+#3236: http: Refactor ClientRequest.onSocket (isaacs)
+Source Code: http://nodejs.org/dist/v0.6.18/node-v0.6.18.tar.gz + +
+Windows Installer: http://nodejs.org/dist/v0.6.18/node-v0.6.18.msi + +
+Windows x64 Files: http://nodejs.org/dist/v0.6.18/x64/ + +
+Macintosh Installer (Universal): http://nodejs.org/dist/v0.6.18/node-v0.6.18.pkg + +
+Other release files: http://nodejs.org/dist/v0.6.18/ + +
+Website: http://nodejs.org/docs/v0.6.18/ + +
+Documentation: http://nodejs.org/docs/v0.6.18/api/
diff --git a/doc/blog/release/version-0-7-10-unstable.md b/doc/blog/release/version-0-7-10-unstable.md index 3e1491114..9ecfb01f1 100644 --- a/doc/blog/release/version-0-7-10-unstable.md +++ b/doc/blog/release/version-0-7-10-unstable.md @@ -6,81 +6,81 @@ status: publish category: release slug: version-0-7-10-unstable -2012.06.11, Version 0.7.10 (unstable) - -
-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. - -
-The major changes are detailed in -https://github.com/joyent/node/wiki/API-changes-between-v0.6-and-v0.8 - -
-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. - - -
-Roll V8 back to 3.9.24.31
-build: x64 target should always pass -m64 (Robert Mustacchi)
-add NODE_EXTERN to node::Start (Joel Brandt)
-repl: Warn about running npm commands (isaacs)
-slab_allocator: fix crash in dtor if V8 is dead (Ben Noordhuis)
-slab_allocator: fix leak of Persistent handles (Shigeki Ohtsu)
-windows/msi: add node.js prompt to startmenu (Jeroen Janssen)
-windows/msi: fix adding node to PATH (Jeroen Janssen)
-windows/msi: add start menu links when installing (Jeroen Janssen)
-windows: don't install x64 version into the 'program files (x86)' folder (Matt Gollob)
-domain: Fix #3379 domain.intercept no longer passes error arg to cb (Marc Harter)
-fs: make callbacks run in global context (Ben Noordhuis)
-fs: enable fs.realpath on windows (isaacs)
-child_process: expose UV_PROCESS_DETACHED as options.detached (Charlie McConnell)
-child_process: new stdio API for .spawn() method (Fedor Indutny)
-child_process: spawn().ref() and spawn().unref() (Fedor Indutny)
-Upgrade npm to 1.1.25
-Source Code: http://nodejs.org/dist/v0.7.10/node-v0.7.10.tar.gz - -
-Windows Installer: http://nodejs.org/dist/v0.7.10/node-v0.7.10.msi - -
-Windows x64 Files: http://nodejs.org/dist/v0.7.10/x64/ - -
-Macintosh Installer (Universal): http://nodejs.org/dist/v0.7.10/node-v0.7.10.pkg - -
-Other release files: http://nodejs.org/dist/v0.7.10/ - -
-Website: http://nodejs.org/docs/v0.7.10/ - -
-Documentation: http://nodejs.org/docs/v0.7.10/api/ +
2012.06.11, Version 0.7.10 (unstable) + +
+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. + +
+The major changes are detailed in +https://github.com/joyent/node/wiki/API-changes-between-v0.6-and-v0.8 + +
+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. + + +
+Roll V8 back to 3.9.24.31
+build: x64 target should always pass -m64 (Robert Mustacchi)
+add NODE_EXTERN to node::Start (Joel Brandt)
+repl: Warn about running npm commands (isaacs)
+slab_allocator: fix crash in dtor if V8 is dead (Ben Noordhuis)
+slab_allocator: fix leak of Persistent handles (Shigeki Ohtsu)
+windows/msi: add node.js prompt to startmenu (Jeroen Janssen)
+windows/msi: fix adding node to PATH (Jeroen Janssen)
+windows/msi: add start menu links when installing (Jeroen Janssen)
+windows: don't install x64 version into the 'program files (x86)' folder (Matt Gollob)
+domain: Fix #3379 domain.intercept no longer passes error arg to cb (Marc Harter)
+fs: make callbacks run in global context (Ben Noordhuis)
+fs: enable fs.realpath on windows (isaacs)
+child_process: expose UV_PROCESS_DETACHED as options.detached (Charlie McConnell)
+child_process: new stdio API for .spawn() method (Fedor Indutny)
+child_process: spawn().ref() and spawn().unref() (Fedor Indutny)
+Upgrade npm to 1.1.25
+Source Code: http://nodejs.org/dist/v0.7.10/node-v0.7.10.tar.gz + +
+Windows Installer: http://nodejs.org/dist/v0.7.10/node-v0.7.10.msi + +
+Windows x64 Files: http://nodejs.org/dist/v0.7.10/x64/ + +
+Macintosh Installer (Universal): http://nodejs.org/dist/v0.7.10/node-v0.7.10.pkg + +
+Other release files: http://nodejs.org/dist/v0.7.10/ + +
+Website: http://nodejs.org/docs/v0.7.10/ + +
+Documentation: http://nodejs.org/docs/v0.7.10/api/
diff --git a/doc/blog/release/version-0-7-11-unstable.md b/doc/blog/release/version-0-7-11-unstable.md index e8fd71a4e..28c2f6813 100644 --- a/doc/blog/release/version-0-7-11-unstable.md +++ b/doc/blog/release/version-0-7-11-unstable.md @@ -6,75 +6,75 @@ status: publish category: release slug: version-0-7-11-unstable -This is the most stable 0.7 release yet. Please try it out. - -
-Version 0.8 will be out very soon. You can follow the remaining issues -on the github issue tracker. - -
-https://github.com/joyent/node/issues?milestone=10&state=open - -
-2012.06.15, Version 0.7.11 (unstable) - -
-V8: Upgrade to v3.11.10
-npm: Upgrade to 1.1.26
-doc: Improve cross-linking in API docs markdown (Ben Kelly)
-Fix #3425: removeAllListeners should delete array (Reid Burke)
-cluster: don't silently drop messages when the write queue gets big (Bert Belder)
-Add Buffer.concat method (isaacs)
-windows: make symlinks tolerant to forward slashes (Bert Belder)
-build: Add node.d and node.1 to installer (isaacs)
-cluster: rename worker.unqiueID to worker.id (Andreas Madsen)
-Windows: Enable ETW events on Windows for existing DTrace probes. (Igor Zinkovsky)
-test: bundle node-weak in test/gc so that it doesn't need to be downloaded (Nathan Rajlich)
-Make many tests pass on Windows (Bert Belder)
-Fix #3388 Support listening on file descriptors (isaacs)
-Fix #3407 Add os.tmpDir() (isaacs)
-Unbreak the snapshotted build on Windows (Bert Belder)
-Clean up child_process.kill throws (Bert Belder)
-crypto: make cipher/decipher accept buffer args (Ben Noordhuis)
-Source Code: http://nodejs.org/dist/v0.7.11/node-v0.7.11.tar.gz - -
-Macintosh Installer (Universal): http://nodejs.org/dist/v0.7.11/node-v0.7.11.pkg - -
-Windows Installer: http://nodejs.org/dist/v0.7.11/node-v0.7.11-x86.msi - -
-Windows x64 Installer: http://nodejs.org/dist/v0.7.11/node-v0.7.11-x64.msi - -
-Windows x64 Files: http://nodejs.org/dist/v0.7.11/x64/ - -
-Other release files: http://nodejs.org/dist/v0.7.11/ - -
-Website: http://nodejs.org/docs/v0.7.11/ - -
-Documentation: http://nodejs.org/docs/v0.7.11/api/ +
This is the most stable 0.7 release yet. Please try it out. + +
+Version 0.8 will be out very soon. You can follow the remaining issues +on the github issue tracker. + +
+https://github.com/joyent/node/issues?milestone=10&state=open + +
+2012.06.15, Version 0.7.11 (unstable) + +
+V8: Upgrade to v3.11.10
+npm: Upgrade to 1.1.26
+doc: Improve cross-linking in API docs markdown (Ben Kelly)
+Fix #3425: removeAllListeners should delete array (Reid Burke)
+cluster: don't silently drop messages when the write queue gets big (Bert Belder)
+Add Buffer.concat method (isaacs)
+windows: make symlinks tolerant to forward slashes (Bert Belder)
+build: Add node.d and node.1 to installer (isaacs)
+cluster: rename worker.unqiueID to worker.id (Andreas Madsen)
+Windows: Enable ETW events on Windows for existing DTrace probes. (Igor Zinkovsky)
+test: bundle node-weak in test/gc so that it doesn't need to be downloaded (Nathan Rajlich)
+Make many tests pass on Windows (Bert Belder)
+Fix #3388 Support listening on file descriptors (isaacs)
+Fix #3407 Add os.tmpDir() (isaacs)
+Unbreak the snapshotted build on Windows (Bert Belder)
+Clean up child_process.kill throws (Bert Belder)
+crypto: make cipher/decipher accept buffer args (Ben Noordhuis)
+Source Code: http://nodejs.org/dist/v0.7.11/node-v0.7.11.tar.gz + +
+Macintosh Installer (Universal): http://nodejs.org/dist/v0.7.11/node-v0.7.11.pkg + +
+Windows Installer: http://nodejs.org/dist/v0.7.11/node-v0.7.11-x86.msi + +
+Windows x64 Installer: http://nodejs.org/dist/v0.7.11/node-v0.7.11-x64.msi + +
+Windows x64 Files: http://nodejs.org/dist/v0.7.11/x64/ + +
+Other release files: http://nodejs.org/dist/v0.7.11/ + +
+Website: http://nodejs.org/docs/v0.7.11/ + +
+Documentation: http://nodejs.org/docs/v0.7.11/api/
diff --git a/doc/blog/release/version-0-7-12.md b/doc/blog/release/version-0-7-12.md index 91e571d2e..c9c448de6 100644 --- a/doc/blog/release/version-0-7-12.md +++ b/doc/blog/release/version-0-7-12.md @@ -6,51 +6,51 @@ status: publish category: release slug: version-0-7-12 -2012.06.19, Version 0.7.12 (unstable)
-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.
-As with other even-numbered Node releases before it, the v0.8.x releases will maintain API and binary compatibility.
-The major changes between v0.6 and v0.8 are detailed in https://github.com/joyent/node/wiki/API-changes-between-v0.6-and-v0.8
-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.
-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.
-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.
-npm: Upgrade to 1.1.30
- Improved 'npm init'
- Fix the 'cb never called' error from 'oudated' and 'update'
- Add --save-bundle|-B config
- Fix isaacs/npm#2465: Make npm script and windows shims cygwin-aware
- Fix isaacs/npm#2452 Use --save(-dev|-optional) in npm rm
- logstream option to replace removed logfd (Rod Vagg)
- Read default descriptions from README.md files
Shims to support deprecated ev_* and eio_* methods (Ben Noordhuis)
#3118 net.Socket: Delay pause/resume until after connect (isaacs)
-#3465 Add ./configure --no-ifaddrs flag (isaacs)
-child_process: add .stdin stream to forks (Fedor Indutny)
-build: fix make install DESTDIR=/path (Ben Noordhuis)
tls: fix off-by-one error in renegotiation check (Ben Noordhuis)
-crypto: Fix diffie-hellman key generation UTF-8 errors (Fedor Indutny)
-node: change the constructor name of process from EventEmitter to process (Andreas Madsen)
-net: Prevent property access throws during close (Reid Burke)
-querystring: improved speed and code cleanup (Felix Böhm)
-sunos: fix assertion errors breaking fs.watch() (Fedor Indutny)
-unix: stat: detect sub-second changes (Ben Noordhuis)
-add stat() based file watcher (Ben Noordhuis)
-Source Code: http://nodejs.org/dist/v0.7.12/node-v0.7.12.tar.gz
-Macintosh Installer (Universal): http://nodejs.org/dist/v0.7.12/node-v0.7.12.pkg
-Windows Installer: http://nodejs.org/dist/v0.7.12/node-v0.7.12-x86.msi
-Windows x64 Installer: http://nodejs.org/dist/v0.7.12/x64/node-v0.7.12-x64.msi
-Windows x64 Files: http://nodejs.org/dist/v0.7.12/x64/
-Other release files: http://nodejs.org/dist/v0.7.12/
-Website: http://nodejs.org/docs/v0.7.12/
-Documentation: http://nodejs.org/docs/v0.7.12/api/
- -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 +2012.06.19, Version 0.7.12 (unstable)
+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.
+As with other even-numbered Node releases before it, the v0.8.x releases will maintain API and binary compatibility.
+The major changes between v0.6 and v0.8 are detailed in https://github.com/joyent/node/wiki/API-changes-between-v0.6-and-v0.8
+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.
+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.
+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.
+
npm: Upgrade to 1.1.30
- Improved 'npm init'
- Fix the 'cb never called' error from 'oudated' and 'update'
- Add --save-bundle|-B config
- Fix isaacs/npm#2465: Make npm script and windows shims cygwin-aware
- Fix isaacs/npm#2452 Use --save(-dev|-optional) in npm rm
- logstream option to replace removed logfd (Rod Vagg)
- Read default descriptions from README.md files
Shims to support deprecated ev_* and eio_* methods (Ben Noordhuis)
#3118 net.Socket: Delay pause/resume until after connect (isaacs)
+#3465 Add ./configure --no-ifaddrs flag (isaacs)
+child_process: add .stdin stream to forks (Fedor Indutny)
+build: fix make install DESTDIR=/path (Ben Noordhuis)
tls: fix off-by-one error in renegotiation check (Ben Noordhuis)
+crypto: Fix diffie-hellman key generation UTF-8 errors (Fedor Indutny)
+node: change the constructor name of process from EventEmitter to process (Andreas Madsen)
+net: Prevent property access throws during close (Reid Burke)
+querystring: improved speed and code cleanup (Felix Böhm)
+sunos: fix assertion errors breaking fs.watch() (Fedor Indutny)
+unix: stat: detect sub-second changes (Ben Noordhuis)
+add stat() based file watcher (Ben Noordhuis)
+Source Code: http://nodejs.org/dist/v0.7.12/node-v0.7.12.tar.gz
+Macintosh Installer (Universal): http://nodejs.org/dist/v0.7.12/node-v0.7.12.pkg
+Windows Installer: http://nodejs.org/dist/v0.7.12/node-v0.7.12-x86.msi
+Windows x64 Installer: http://nodejs.org/dist/v0.7.12/x64/node-v0.7.12-x64.msi
+Windows x64 Files: http://nodejs.org/dist/v0.7.12/x64/
+Other release files: http://nodejs.org/dist/v0.7.12/
+Website: http://nodejs.org/docs/v0.7.12/
+Documentation: http://nodejs.org/docs/v0.7.12/api/
+ +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.pdbdiff --git a/doc/blog/release/version-0-7-4-unstable.md b/doc/blog/release/version-0-7-4-unstable.md index 01bc92ae5..38d6615c0 100644 --- a/doc/blog/release/version-0-7-4-unstable.md +++ b/doc/blog/release/version-0-7-4-unstable.md @@ -6,45 +6,45 @@ status: publish category: release slug: version-0-7-4-unstable -
2012.02.14, Version 0.7.4 (unstable) - -
-Upgrade V8 to 3.9.5
-Upgrade npm to 1.1.1
-build: Detect host_arch better (Karl Skomski)
-debugger: export debug_port to process (Fedor Indutny)
api docs: CSS bug fixes (isaacs)
-build: use -fPIC for native addons on UNIX (Nathan Rajlich)
-Re-add top-level v8::Locker (Marcel Laverdet)
-Move images out of the dist tarballs (isaacs)
-libuv: Remove uv_export and uv_import (Ben Noordhuis)
-build: Support x64 build on Windows (Igor Zinkovsky)
-Source Code: http://nodejs.org/dist/v0.7.4/node-v0.7.4.tar.gz - -
-Windows Installer: http://nodejs.org/dist/v0.7.4/node-v0.7.4.msi - -
-Macintosh Installer: http://nodejs.org/dist/v0.7.4/node-v0.7.4.pkg - -
-Other release files: http://nodejs.org/dist/v0.7.4/ - -
-Website: http://nodejs.org/docs/v0.7.4/ - -
-Documentation: http://nodejs.org/docs/v0.7.4/api/ +
2012.02.14, Version 0.7.4 (unstable) + +
+Upgrade V8 to 3.9.5
+Upgrade npm to 1.1.1
+build: Detect host_arch better (Karl Skomski)
+debugger: export debug_port to process (Fedor Indutny)
api docs: CSS bug fixes (isaacs)
+build: use -fPIC for native addons on UNIX (Nathan Rajlich)
+Re-add top-level v8::Locker (Marcel Laverdet)
+Move images out of the dist tarballs (isaacs)
+libuv: Remove uv_export and uv_import (Ben Noordhuis)
+build: Support x64 build on Windows (Igor Zinkovsky)
+Source Code: http://nodejs.org/dist/v0.7.4/node-v0.7.4.tar.gz + +
+Windows Installer: http://nodejs.org/dist/v0.7.4/node-v0.7.4.msi + +
+Macintosh Installer: http://nodejs.org/dist/v0.7.4/node-v0.7.4.pkg + +
+Other release files: http://nodejs.org/dist/v0.7.4/ + +
+Website: http://nodejs.org/docs/v0.7.4/ + +
+Documentation: http://nodejs.org/docs/v0.7.4/api/
diff --git a/doc/blog/release/version-0-7-5-unstable.md b/doc/blog/release/version-0-7-5-unstable.md index bc1e6047d..b493cde89 100644 --- a/doc/blog/release/version-0-7-5-unstable.md +++ b/doc/blog/release/version-0-7-5-unstable.md @@ -6,57 +6,57 @@ status: publish category: release slug: version-0-7-5-unstable -2012.02.23, Version 0.7.5 (unstable) - -
-startup speed improvements (Maciej Małecki)
-crypto: add function getDiffieHellman() (Tomasz Buchert)
-buffer: support decoding of URL-safe base64 (Ben Noordhuis)
-Make QueryString.parse() even faster (Brian White)
-url: decode url entities in auth section (Ben Noordhuis)
-http: support PURGE request method (Ben Noordhuis)
-http: Generate Date headers on responses (Mark Nottingham)
-Fix #2762: Add callback to close function. (Mikeal Rogers)
-dgram: fix out-of-bound memory read (Ben Noordhuis)
-repl: add automatic loading of built-in libs (Brandon Benvie)
-repl: remove double calls where possible (Fedor Indutny)
-Readline improvements. Related: #2737 #2756 (Colton Baker)
-build: disable -fomit-frame-pointer on solaris (Dave Pacheco)
-build: arch detection improvements (Nathan Rajlich)
-build: Make a fat binary for the OS X make pkg. (Nathan Rajlich)
jslint src/ and lib/ on 'make test' (isaacs)
-Source Code: http://nodejs.org/dist/v0.7.5/node-v0.7.5.tar.gz - -
-Windows Installer: http://nodejs.org/dist/v0.7.5/node-v0.7.5.msi - -
-Macintosh Installer: http://nodejs.org/dist/v0.7.5/node-v0.7.5.pkg - -
-Other release files: http://nodejs.org/dist/v0.7.5/ - -
-Website: http://nodejs.org/docs/v0.7.5/ - -
-Documentation: http://nodejs.org/docs/v0.7.5/api/ +
2012.02.23, Version 0.7.5 (unstable) + +
+startup speed improvements (Maciej Małecki)
+crypto: add function getDiffieHellman() (Tomasz Buchert)
+buffer: support decoding of URL-safe base64 (Ben Noordhuis)
+Make QueryString.parse() even faster (Brian White)
+url: decode url entities in auth section (Ben Noordhuis)
+http: support PURGE request method (Ben Noordhuis)
+http: Generate Date headers on responses (Mark Nottingham)
+Fix #2762: Add callback to close function. (Mikeal Rogers)
+dgram: fix out-of-bound memory read (Ben Noordhuis)
+repl: add automatic loading of built-in libs (Brandon Benvie)
+repl: remove double calls where possible (Fedor Indutny)
+Readline improvements. Related: #2737 #2756 (Colton Baker)
+build: disable -fomit-frame-pointer on solaris (Dave Pacheco)
+build: arch detection improvements (Nathan Rajlich)
+build: Make a fat binary for the OS X make pkg. (Nathan Rajlich)
jslint src/ and lib/ on 'make test' (isaacs)
+Source Code: http://nodejs.org/dist/v0.7.5/node-v0.7.5.tar.gz + +
+Windows Installer: http://nodejs.org/dist/v0.7.5/node-v0.7.5.msi + +
+Macintosh Installer: http://nodejs.org/dist/v0.7.5/node-v0.7.5.pkg + +
+Other release files: http://nodejs.org/dist/v0.7.5/ + +
+Website: http://nodejs.org/docs/v0.7.5/ + +
+Documentation: http://nodejs.org/docs/v0.7.5/api/
diff --git a/doc/blog/release/version-0-7-6-unstable.md b/doc/blog/release/version-0-7-6-unstable.md index ecf67f3ea..342c792a0 100644 --- a/doc/blog/release/version-0-7-6-unstable.md +++ b/doc/blog/release/version-0-7-6-unstable.md @@ -6,67 +6,67 @@ status: publish category: release slug: version-0-7-6-unstable -2012.03.13, Version 0.7.6 (unstable) - -
-Upgrade v8 to 3.9.17
-Upgrade npm to 1.1.8
-
-- Add support for os/cpu fields in package.json (Adam Blackburn)
-- Automatically node-gyp packages containing a binding.gyp
-- Fix failures unpacking in UNC shares
-- Never create un-listable directories
-- Handle cases where an optionalDependency fails to build
-
events: newListener emit correct fn when using 'once' (Roly Fentanes)
-url: Ignore empty port component (Åukasz Walukiewicz)
-module: replace 'children' array (isaacs)
-tls: parse multiple values of a key in ssl certificate (Sambasiva Suda)
-cluster: support passing of named pipes (Ben Noordhuis)
-Windows: include syscall in fs errors (Bert Belder)
-http: #2888 Emit end event only once (Igor Zinkovsky)
-readline: add multiline support (Rlidwka)
-process: add process.hrtime() (Nathan Rajlich)
net, http, https: add localAddress option (Dmitry Nizovtsev)
-addon improvements (Nathan Rajlich)
-build improvements (Ben Noordhuis, Sadique Ali, T.C. Hollingsworth, Nathan Rajlich)
-add support for "SEARCH" request methods (Nathan Rajlich)
-expose the zlib and http_parser version in process.versions (Nathan Rajlich)
-Source Code: http://nodejs.org/dist/v0.7.6/node-v0.7.6.tar.gz - -
-Windows Installer: http://nodejs.org/dist/v0.7.6/node-v0.7.6.msi - -
-Windows x64 Files: http://nodejs.org/dist/v0.7.6/x64/ - -
-Macintosh Installer (Universal): http://nodejs.org/dist/v0.7.6/node-v0.7.6.pkg - -
-Other release files: http://nodejs.org/dist/v0.7.6/ - -
-Website: http://nodejs.org/docs/v0.7.6/ - -
-Documentation: http://nodejs.org/docs/v0.7.6/api/ +
2012.03.13, Version 0.7.6 (unstable) + +
+Upgrade v8 to 3.9.17
+Upgrade npm to 1.1.8
+
+- Add support for os/cpu fields in package.json (Adam Blackburn)
+- Automatically node-gyp packages containing a binding.gyp
+- Fix failures unpacking in UNC shares
+- Never create un-listable directories
+- Handle cases where an optionalDependency fails to build
+
events: newListener emit correct fn when using 'once' (Roly Fentanes)
+url: Ignore empty port component (Åukasz Walukiewicz)
+module: replace 'children' array (isaacs)
+tls: parse multiple values of a key in ssl certificate (Sambasiva Suda)
+cluster: support passing of named pipes (Ben Noordhuis)
+Windows: include syscall in fs errors (Bert Belder)
+http: #2888 Emit end event only once (Igor Zinkovsky)
+readline: add multiline support (Rlidwka)
+process: add process.hrtime() (Nathan Rajlich)
net, http, https: add localAddress option (Dmitry Nizovtsev)
+addon improvements (Nathan Rajlich)
+build improvements (Ben Noordhuis, Sadique Ali, T.C. Hollingsworth, Nathan Rajlich)
+add support for "SEARCH" request methods (Nathan Rajlich)
+expose the zlib and http_parser version in process.versions (Nathan Rajlich)
+Source Code: http://nodejs.org/dist/v0.7.6/node-v0.7.6.tar.gz + +
+Windows Installer: http://nodejs.org/dist/v0.7.6/node-v0.7.6.msi + +
+Windows x64 Files: http://nodejs.org/dist/v0.7.6/x64/ + +
+Macintosh Installer (Universal): http://nodejs.org/dist/v0.7.6/node-v0.7.6.pkg + +
+Other release files: http://nodejs.org/dist/v0.7.6/ + +
+Website: http://nodejs.org/docs/v0.7.6/ + +
+Documentation: http://nodejs.org/docs/v0.7.6/api/
diff --git a/doc/blog/release/version-0-7-7-unstable.md b/doc/blog/release/version-0-7-7-unstable.md index 6cdcc2312..4ba17658a 100644 --- a/doc/blog/release/version-0-7-7-unstable.md +++ b/doc/blog/release/version-0-7-7-unstable.md @@ -6,66 +6,66 @@ status: publish category: release slug: version-0-7-7-unstable -2012.03.30, Version 0.7.7 (unstable) - -
-Upgrade V8 to 3.9.24.7
-Upgrade npm to 1.1.15
-Handle Emoji characters properly (Erik Corry, Bert Belder)
-readline: migrate ansi/vt100 logic from tty to readline (Nathan Rajlich)
-readline: Fix multiline handling (Alex Kocharin)
-add a -i/--interactive flag to force the REPL (Nathan Rajlich)
-debugger: add breakOnException command (Fedor Indutny)
-cluster: kill workers when master dies (Andreas Madsen)
-cluster: add graceful disconnect support (Andreas Madsen)
-child_process: Separate 'close' event from 'exit' (Charlie McConnell)
-typed arrays: add Uint8ClampedArray (Mikael Bourges-Sevenier)
-buffer: Fix byte alignment issues (Ben Noordhuis, Erik Lundin)
-tls: fix CryptoStream.setKeepAlive() (Shigeki Ohtsu)
-Expose http parse error codes (Felix Geisendörfer)
-events: don't delete the listeners array (Ben Noordhuis, Nathan Rajlich)
-process: add process.config to view node's ./configure settings (Nathan Rajlich)
-process: process.execArgv to see node's arguments (Micheil Smith)
-process: fix process.title setter (Ben Noordhuis)
-timers: handle negative or non-numeric timeout values (Ben Noordhuis)
-Source Code: http://nodejs.org/dist/v0.7.7/node-v0.7.7.tar.gz - -
-Windows Installer: http://nodejs.org/dist/v0.7.7/node-v0.7.7.msi - -
-Windows x64 Files: http://nodejs.org/dist/v0.7.7/x64/ - -
-Macintosh Installer (Universal): http://nodejs.org/dist/v0.7.7/node-v0.7.7.pkg - -
-Other release files: http://nodejs.org/dist/v0.7.7/ - -
-Website: http://nodejs.org/docs/v0.7.7/ - -
-Documentation: http://nodejs.org/docs/v0.7.7/api/ +
2012.03.30, Version 0.7.7 (unstable) + +
+Upgrade V8 to 3.9.24.7
+Upgrade npm to 1.1.15
+Handle Emoji characters properly (Erik Corry, Bert Belder)
+readline: migrate ansi/vt100 logic from tty to readline (Nathan Rajlich)
+readline: Fix multiline handling (Alex Kocharin)
+add a -i/--interactive flag to force the REPL (Nathan Rajlich)
+debugger: add breakOnException command (Fedor Indutny)
+cluster: kill workers when master dies (Andreas Madsen)
+cluster: add graceful disconnect support (Andreas Madsen)
+child_process: Separate 'close' event from 'exit' (Charlie McConnell)
+typed arrays: add Uint8ClampedArray (Mikael Bourges-Sevenier)
+buffer: Fix byte alignment issues (Ben Noordhuis, Erik Lundin)
+tls: fix CryptoStream.setKeepAlive() (Shigeki Ohtsu)
+Expose http parse error codes (Felix Geisendörfer)
+events: don't delete the listeners array (Ben Noordhuis, Nathan Rajlich)
+process: add process.config to view node's ./configure settings (Nathan Rajlich)
+process: process.execArgv to see node's arguments (Micheil Smith)
+process: fix process.title setter (Ben Noordhuis)
+timers: handle negative or non-numeric timeout values (Ben Noordhuis)
+Source Code: http://nodejs.org/dist/v0.7.7/node-v0.7.7.tar.gz + +
+Windows Installer: http://nodejs.org/dist/v0.7.7/node-v0.7.7.msi + +
+Windows x64 Files: http://nodejs.org/dist/v0.7.7/x64/ + +
+Macintosh Installer (Universal): http://nodejs.org/dist/v0.7.7/node-v0.7.7.pkg + +
+Other release files: http://nodejs.org/dist/v0.7.7/ + +
+Website: http://nodejs.org/docs/v0.7.7/ + +
+Documentation: http://nodejs.org/docs/v0.7.7/api/
diff --git a/doc/blog/release/version-0-7-8-unstable.md b/doc/blog/release/version-0-7-8-unstable.md index 8e87a9007..9c829fa6a 100644 --- a/doc/blog/release/version-0-7-8-unstable.md +++ b/doc/blog/release/version-0-7-8-unstable.md @@ -6,66 +6,66 @@ status: publish category: release slug: version-0-7-8-unstable -2012.04.18, Version 0.7.8, (unstable) - -
-Upgrade V8 to 3.9.24.9
-Upgrade OpenSSL to 1.0.0f
-Upgrade npm to 1.1.18
-Show licenses in Binary installers
-Domains (isaacs)
-readline: rename "end" to "close" (Nathan Rajlich)
-tcp: make getsockname() return address family as string (Shigeki Ohtsu)
-http, https: fix .setTimeout() (ssuda)
-os: add cross platform EOL character (Mustansir Golawala)
-typed arrays: unexport SizeOfArrayElementForType() (Aaron Jacobs)
-net: honor 'enable' flag in .setNoDelay() (Ben Noordhuis)
-child_process: emit error when .kill fails (Andreas Madsen)
-gyp: fix 'argument list too long' build error (Ben Noordhuis)
-fs.WriteStream: Handle modifications to fs.open (isaacs)
-repl, readline: Handle newlines better (Nathan Rajlich, Nathan Friedly)
-build: target OSX 10.5 when building on darwin (Nathan Rajlich)
-Fix #3052 Handle errors properly in zlib (isaacs)
-build: add support for DTrace and postmortem (Dave Pacheco)
-core: add reusable Slab allocator (Ben Noordhuis)
-Source Code: http://nodejs.org/dist/v0.7.8/node-v0.7.8.tar.gz - -
-Windows Installer: http://nodejs.org/dist/v0.7.8/node-v0.7.8.msi - -
-Windows x64 Files: http://nodejs.org/dist/v0.7.8/x64/ - -
-Macintosh Installer (Universal): http://nodejs.org/dist/v0.7.8/node-v0.7.8.pkg - -
-Other release files: http://nodejs.org/dist/v0.7.8/ - -
-Website: http://nodejs.org/docs/v0.7.8/ - -
-Documentation: http://nodejs.org/docs/v0.7.8/api/ +
2012.04.18, Version 0.7.8, (unstable) + +
+Upgrade V8 to 3.9.24.9
+Upgrade OpenSSL to 1.0.0f
+Upgrade npm to 1.1.18
+Show licenses in Binary installers
+Domains (isaacs)
+readline: rename "end" to "close" (Nathan Rajlich)
+tcp: make getsockname() return address family as string (Shigeki Ohtsu)
+http, https: fix .setTimeout() (ssuda)
+os: add cross platform EOL character (Mustansir Golawala)
+typed arrays: unexport SizeOfArrayElementForType() (Aaron Jacobs)
+net: honor 'enable' flag in .setNoDelay() (Ben Noordhuis)
+child_process: emit error when .kill fails (Andreas Madsen)
+gyp: fix 'argument list too long' build error (Ben Noordhuis)
+fs.WriteStream: Handle modifications to fs.open (isaacs)
+repl, readline: Handle newlines better (Nathan Rajlich, Nathan Friedly)
+build: target OSX 10.5 when building on darwin (Nathan Rajlich)
+Fix #3052 Handle errors properly in zlib (isaacs)
+build: add support for DTrace and postmortem (Dave Pacheco)
+core: add reusable Slab allocator (Ben Noordhuis)
+Source Code: http://nodejs.org/dist/v0.7.8/node-v0.7.8.tar.gz + +
+Windows Installer: http://nodejs.org/dist/v0.7.8/node-v0.7.8.msi + +
+Windows x64 Files: http://nodejs.org/dist/v0.7.8/x64/ + +
+Macintosh Installer (Universal): http://nodejs.org/dist/v0.7.8/node-v0.7.8.pkg + +
+Other release files: http://nodejs.org/dist/v0.7.8/ + +
+Website: http://nodejs.org/docs/v0.7.8/ + +
+Documentation: http://nodejs.org/docs/v0.7.8/api/
diff --git a/doc/blog/video/bryan-cantrill-instrumenting-the-real-time-web.md b/doc/blog/video/bryan-cantrill-instrumenting-the-real-time-web.md index 0c26cb7a4..fa982135d 100644 --- a/doc/blog/video/bryan-cantrill-instrumenting-the-real-time-web.md +++ b/doc/blog/video/bryan-cantrill-instrumenting-the-real-time-web.md @@ -5,15 +5,15 @@ status: publish 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. - -This talk was given at Velocity Conf in 2011. - -