This page is deprecated. Feel free to add to it, but be advised that it is, at best, a faded relic of Node modules that were written before npm was a dominant force in the Node.js ecosystem. It is not all that useful any more. If you are a newcomer, it can be handy to at least get a starting point.
node blog 2013.12.31, Version 0.11.10 (Unstable) http_parser: update to 2.2uv: Upgrade to v0.11.17v8: Upgrade to 126.96.36.199buffer: optimize writeInt* methods (Paul Loyd)child_process: better error handling (Alexis Campailla)cluster: do not synchronously emit 'setup' event (Sam Roberts)cluster: restore backwards compatibility and various fixes (Sam Roberts)crypto: remove unnecessary OpenSSL_add_all_digests (Yorkie)crypto: support GCM authenticated encryption mode. (Ingmar Runge)dns: add resolveSoa and 'SOA' rrtype (Tuğrul Topuz)events: move EE c'tor guts to EventEmitter.init (Bert Belder)http: DELETE shouldn't default to chunked encoding (Lalit Kapoor)http: parse the status message in a http response.
An example: Webserver This simple web server written in Node responds with "Hello World" for every request. To run the server, put the code into a file example.js and execute it with the node program from the command line: % node example.js Server running at http://127.0.0.1:1337/ Here is an example of a simple TCP server which listens on port 1337 and echoes whatever you send it:
By Tim Caswell Generators vs Fibers Both ES6 generators and node-fibers can be used to block a coroutine while waiting on some I/O without blocking the entire process. This means that you can wait for an I/O result within your code but still have the performance benefits of the single-threaded, non-blocking I/O model you all know and love.