I'm currently using node-require-directory: http://elegantcode.com/2013/02/01/taking-toddler-steps-with-node-js-express-routing-revisited/
Hope this helps On Tuesday, June 18, 2013 9:21:20 AM UTC+2, Ben wrote: > > Hey folks, > > I've searched the web pretty exhaustively, and it seems like there are > multiple best practices for factoring express routes into separate files. > I'm halfway through porting my code base over to the model described here: > http://rycole.com/2013/01/28/organizing-nodejs-express.html > > When I stumbled upon this: > > http://stackoverflow.com/questions/10306185/nodejs-best-way-to-pass-common-variables-into-separate-modules > > Since i'm using AngularJS on my client i've become familiar with the > dependency injection pattern. This second post above seems to indicate that > this is a great best practice for Node as well. > > I'm leaning towards using DI for tackling my route separation but I wanted > to check to see if there were any major reasons why this wouldnt be a good > idea? > > Thanks! > Ben > -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
