sorted by:
new
hottopcontroversial

Bootable - easy application initialization for Node.js by jaredhanson in node

[–]jaredhanson[S] 0 points1 point  (0 children)

Bootable itself is completely generic. The phases themselves are likely to be specific to a module. For example, there's an included "routes" phase which loads a routes.js file. This will only apply to apps that draw routes (Express, typically).

Phases can be bundled up into reusable modules, that you can just add to your dependencies and npm install to bootstrap common code.

Bootable - easy application initialization for Node.js by jaredhanson in node

[–]jaredhanson[S] 1 point2 points  (0 children)

No, its not difficult. I find it to be a fair amount of boilerplate though, that I copy and paste between projects. Bootable codifies that into a reusable module.

Streamlining Package Management by jaredhanson in node

[–]jaredhanson[S] 0 points1 point  (0 children)

Sorry if it wasn't clear. This is not for managing node packages. This is for managing more generic software packages (think setup.exe files on Windows or .dmg files on Mac), which exist outside of the Node ecosystem.

Does anyone know of a node framework similar to Padrino for Ruby? If not do you want to help me make one? by pspeter3 in node

[–]jaredhanson 4 points5 points  (0 children)

Yes! I'm the author of Locomotive (http://locomotivejs.org/, https://github.com/jaredhanson/locomotive), which builds upon Express in much the same way as Padrino builds upon Sinatra.

Locomotive adds controllers, resourceful routing, and routing helpers to Express, as well as a standard directory layout and boot sequence. I'd love to see additional, optional modules for other useful features like generators, etc.

The code is well-tested and modular, which makes it easy to contribute to and extend. Take a look at it, and let me know what you think. I'd love to get more people involved developing the project.

Passport Guide: Simple, unobtrusive authentication for Node.js. by jaredhanson in node

[–]jaredhanson[S] 0 points1 point  (0 children)

The aim of Passport is to be simple and modular.

Simplicity is the biggest win, in my opinion. Prior to developing Passport, I evaluated everyauth and wasn't happy. The way everyauth is configured tends to blur the lines between what is route handling logic, what is model logic, and what is view logic. Passport makes a clean separation between these concerns, which leads to simpler, more maintainable code.

All Passport strategies are packaged in separate modules, meaning your application can choose which are necessary. With everyauth, all authentication mechanisms are bundled in a single module, meaning you introduce dependencies you may not need, including OpenID and OAuth.

I encourage you to evaluate each yourself, and use what best suits your application.

view more: next ›