This repository was archived by the owner on Dec 15, 2022. It is now read-only.
Closed
Conversation
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 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.
Requirements
Description of the Change
Reverts most of #832. There's been a few problems with
node-gyp being unable to find dependencies orrebuilding failing on 32-bit Windows, which I think may be resolved if we simply go back to depending on it explicitly. I have, however, updated the dependency to match that of npm@6.2.0.Alternate Designs
#832, which was causing
flaky builds on this repo andrebuild errors downstream in atom/atom.Benefits
Newer node-gyp version (VS2017 support, bugfixes, etc).
Possible Drawbacks
We'll have to remember to update node-gyp each time we update npm.
Verification Process
N/A
Applicable Issues
#832, atom/atom#19189