This repository has been archived by the owner on Mar 5, 2019. It is now read-only.
Node 0.6.x compatibility, fix require paths. #3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mkitt
pushed a commit
that referenced
this pull request
Nov 23, 2011
Node 0.6.x compatibility, fix require paths.
|
Hi Tim. |
|
No worries :D |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Trying to use this with a node 0.6.x project will bork. Updated the package.json using
npm init; this reformatted the commas, which I would suggest keeping since that's the output of the npm tool itself.I also set the paths in the module so they are relative (it's a big no-no to modify require paths)
You may actually want to manually test that the module works, I just made it installable and the tests apparently 100% passing.