If $NODE_PATH ends with a colon, require will act unexpected#1487
Closed
chrisyip wants to merge 1 commit intonodejs:masterfrom
Closed
If $NODE_PATH ends with a colon, require will act unexpected#1487chrisyip wants to merge 1 commit intonodejs:masterfrom
$NODE_PATH ends with a colon, require will act unexpected#1487chrisyip wants to merge 1 commit intonodejs:masterfrom
Conversation
Contributor
|
LGTM PS: where is the CI? |
Contributor
Author
Member
|
@chrisyip for now, collaborators of io.js has access to start a CI run for you. Our ambition is to improve this so all PR's at some point gets testing. Btw -- when forking and doing PR's, it's always good to create a new branch for your work instead of using master. CI run here: https://jenkins-iojs.nodesource.com/job/iojs+any-pr+multi/567/ |
Contributor
Author
|
OK, I will create a new branch and make a PR again. Sorry for the trouble. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Here is a repo that explains the difference: https://github.com/chrisyip/NODE_PATH_DEMO.
After separation,
nodePathwill become[ '/usr/local/lib/node_modules', '' ](in the above case).I know node should not take the responsibility for env variables, but since
''is meaningless, I suggest to remove''fromnodePathbefore using it.