Personally I prefer the module.exports at the end approach... easier to visualize.

@dcousens then, let's back to this code. What do you think about export right after require?

@fanatid can't stand it.
I follow these three rules which lead to the result I typically have:

• No use before declaration
• No repeated declarations
• Prefer named functions
• Group hackish/lame/ugly code for easy removal one day

Moving the exports to the top breaks my first rule.
The current implementation breaks my second rule, and removing the function name makes it an anonymous function (ew).
The previous implementation met all these rules.

Ideally, ES Next's export style syntax would be available... until then, I use the module.exports = {} at EOF.

Thoughts?

@dcousens thanks for published your rules, it's really helpful.
I'm ok with them, do you need PR for module.export or you do this yourself?
Can you publish new version after this?