Skip to content

Frameworks

victorkane edited this page Jun 19, 2011 · 1 revision

Although initially we were going with node only, without using express or grasshopper, etc., doing all the routing, etc., using custom modules, the decision was made to adopt the healthy principle of code re-use, standing on connect and express. That way we have community standard methods for auth, and many other things.

App packaging

For packaging our app, and the presence of package.json in our source root (originally marked as private when generated by express executable and then edited as additional dependencies are added) see this Express google group discussion: Should we use package.json for websites?

See Express quick start for our very initial code generation.

MVC considerations

An MVC approach: https://github.com/jasonmelgoza/express-blog/blob/master/app.js

An MVC approach is included in the Express example apps.

Available node modules and packages

In general, when searching for modules and packages, see Joyent's Wiki: https://github.com/joyent/node/wiki/modules

Also see NPM search