If $NODE_PATH
ends with a colon, require
will act unexpected
#1487
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,
nodePath
will 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''
fromnodePath
before using it.