This repository has been archived by the owner on Jul 3, 2019. It is now read-only.
bring back the .gitignore -> .npmignore logic 'cause it wasn't supposed to go #113
Conversation
This file contains 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
pacote@5 dropped support for a Very Legacy™ thing where npm would, on extract, rename .gitignore to .npmignore if there was not already an .npmignore. This was primarily to support the use case where folks would use npm install on github release tarballs. Ref: npm/npm#5658 BREAKING CHANGE: this reverts a previous change to disable this feature.
zkat
force-pushed
the
zkat/revive-ignore-juggling
branch
from
05f331e
to
969a1a1
Compare
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.
No description provided.