This repository was archived by the owner on Nov 16, 2019. It is now read-only.
Open
Conversation
Do not rename multiple *.gyp files to binding.gyp . As a side-effect, no .gyp files will be renamed if binding.gyp is present. Fix: npm/npm#8411
Author
|
cc @othiym23 I'm not exactly sure if this kind of Please let me know what you think about it. |
Contributor
|
Does this accomplish the same thing as #16 does? |
Author
|
No, @kenany. It is a slightly more compatible solution, IMO. It will still rename |
Contributor
|
Ah okay :) |
|
Dupe of #16? |
Author
|
@mikemorris they are different, see #18 (comment) |
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.
3 participants
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.
Do not rename multiple *.gyp files to binding.gyp . As a side-effect, no
.gyp files will be renamed if binding.gyp is present.
Fix: npm/npm#8411