Fix for installing llnode as a global #94
Closed
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.
When
npm explore
is ran with a-g
option the default folder is set tonpm.globalDir
which is the root
$GLOBAL/lib/node_modules
folder containing npm.But when it's ran in local mode it uses path.resolve(npm.prefix, 'node_modules')
See https://github.com/npm/npm/blob/latest/lib/npm.js#L395
This is causing the resolution of node-gyp to fail in global mode.
This patch tests the npm environment variable
npm_config_global
to see if it's a global install and appends the required sub directories to get it to work.Tested on Ubuntu 16.04 with
Fixes: #77