h5bp/server-configs — Issue #46: Node.js config
Author: klaemo
Created: 2012-03-01 19:44:07+00:00
State: open

Hey,
I want to start a discussion about the node server config as I think there might be room for improvement.

IMO, we have to treat node kinda differently, since it isn't exclusively an http server. That's why, for example, the current node config uses the connect middleware framework (which is an excellent choice).

I think, we should aim to make the node config more boilerplate-y itself.

Here are my suggestions:

1. Use express instead of connect
- why, you might ask? well, connect is a framework to build other frameworks. express is a framework built on top of connect geared towards web developers (the targeted audience of h5bp, in my eyes) and the newest connect doesn't include a router middleware anymore
2. use connect.compress() middlware included in connect 2.0 to enable compression
3. maybe, but only maybe use connect-assetmanager for concatenation and minification of JS and CSS
- that kinda makes h5bp's build system obsolete though. that's why i'm not sure if I like this idea

what do you think?