Community

Mission statement

Node.js on it’s own is bare bones by design. So if you want to have really fast code you’ll have the option to get just that without added baggage. However, there are also merits to the Python “batteries included” approach. This page is to be used to collect thoughts on libraries needed for application development and pointers to actual code and/or code that can be adapted to work with node’s asynchronous nature.

Libraries

Actual libraries

haml-js	A haml like web-templating language (client side only at the moment, but work on a server side haml implementation is on it’s way)
postgres-js	A PostgreSQL driver
redis-node-client	A Redis client

Wish list

node_mysql	A MySQL driver
node_crypt	Cryptographic routines
node_http	A webserver, i.e. also handling static files like Apache does, etc.
node_extlib	A grab bag of useful extensions to the standard classes
modules	A better way to handle modules. With somewhat bigger projects load/require are just to hard to use
testing	A library that allows easy unit tests. Right now there’s no easy way to easily setup tests that only pass when all the code in callbacks has passed

Idea list

node_dom	W3C DOM Support 1
node_browser	building on node_dom, support jQuery, Dojo, Prototype, etc. server-side 1
node_xrad	A duct taping framework for simulating TBD libraries (for example using node.createProcess to wrap the mysql command-line client, providing minimal MySQL support). In contrast to optimized, lower-level native interfaces, the idea here would be to explore proof-of-concepts and API abstractions earlier rather than later, allowing developers to potentially substitute the “real thing” if/when available.

¹ 2009.07.30 timjs: I have working prototypes of these (mashing up env.js and ajaxslt); not sure how to package up API as a library just yet

Other code

php.js	Implementation of PHP functions in JavaScript
narwhal	Might not work out of the box, but could be used as inspiration
ServerJS	An effort to standardize server side JavaScript