Skip to content
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.

Enable overriding node-gyp binary #4887

Closed
wants to merge 1 commit into from

Conversation

ackalker
Copy link
Contributor

Enable overriding the node-gyp binary used by npm by specifying a config
option, similar to specifying the python interpreter.

Example usage:

npm install --node-gyp=<path-to-custom-node-gyp>

Enable overriding the node-gyp binary used by npm by specifying
a config option, similar to specifying the python interpreter.

Example usage:

    npm install --node-gyp=<path-to-custom-node-gyp>
@othiym23
Copy link
Contributor

Rebased and landed as 145af65. I created #7479 to capture the need to document this new option, which will probably involve some monkeying with the config tests because the value isn't used within npm itself. This is a topical change, given that it allows people to use unpatched npm with new versions of io.js by pointing at a patched node-gyp. Thanks for putting this together, and thanks for your patience!

@othiym23 othiym23 closed this Feb 27, 2015
@ackalker
Copy link
Contributor Author

You're welcome :-)

@fengmk2
Copy link
Contributor

fengmk2 commented Mar 6, 2015

Great job! We can use pangyp now!

fengmk2 added a commit to fengmk2/node-pre-gyp that referenced this pull request Mar 8, 2015
npm@2.7.0 support custom node-gyp path,
we can use pangyp instead of node-gyp now.

npm/npm#4887
fengmk2 added a commit to fengmk2/node-pre-gyp that referenced this pull request Mar 8, 2015
npm@2.7.0 support custom node-gyp path,
we can use pangyp instead of node-gyp now.

npm/npm#4887
@ackalker ackalker deleted the support-custom-node-gyp branch May 10, 2019 20:49
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants