[nodejs] Re: Best practice for Node module interface

2013-07-15 Thread Martin Jagusch
To pick up this discussion again, I'm currently evaluating the best/easiest interface for a open source project I'm working. And would really like to hear your opinions about the following examples: // 1 var kite = require('kitemetrics'); var server = new kite.Server(); var router = new

[nodejs] Re: Best practice for Node module interface

2013-07-15 Thread Vaughan
I prefer: `var foo = new module.Foo()` although I prefer to use CoffeeScript's object destructuring assignment: ``` {Foo} = require 'module' foo = new Foo ``` or ``` moduleA = require 'module-a' foo = new moduleA.Foo ``` 1. Using the `new` keyword clearly indicates the creation of an object

Re: [nodejs] Re: Best practice for Node module interface

2013-07-15 Thread Aria Stewart
On July 15, 2013 at 2:47:39 PM, Martin Jagusch (m...@mj.io) wrote: To pick up this discussion again, I'm currently evaluating the best/easiest interface for a open source project I'm working. And would really like to hear your opinions about the following examples: // 1 var kite =

Re: [nodejs] Re: Best practice for Node module interface

2013-07-15 Thread Jake Verbaten
without understanding the server - router and server - dealer relationship I recommend ```js var Router = require(kitemetrics/router) var Dealer = require(kitemetrics/dealer) var dealer = Dealer() dealer.listen(5560) var router = Router() router.listen(5559) ``` note `new` is optional, one

[nodejs] Re: Best practice for Node module interface

2013-07-13 Thread Gagle
If the module exposes only one thing var fn = require (module); If the module exposes various things var m = require (module); m.a() m.b() var fn = m.createFn() //or create() or whatever you want -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: