assign require in node, instead of global #2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
in node.js you must assign the return value of the require statement.
That was all.
This is a huge win in node.js because we totally escape dependency hell.
Each module is wrapped in a closure, and then assigned to a variable where it is used,
I wrote a blog post about the strengths of node's module system here
http://dominictarr.com/post/25516279897/why-you-should-never-write-a-package-manager