update to referer-less npm-registry-fetch #29
Merged
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
This drops support for the 'opts.refer' option, and no longer sends a referer header to registry requests.
isaacs
force-pushed
the
isaacs/no-referer
branch
3 times, most recently
from
755beef to
18c13a6
Compare
It's just too flaky and hard to get paths filtered out of the snapshots properly.
isaacs
force-pushed
the
isaacs/no-referer
branch
from
18c13a6 to
cc62545
Compare
Not sure why Darwin on Node v10 is sometimes returning a core node error rather than a reconfigured fetch error, but allow it.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Depends on npm/npm-registry-fetch#25
Land that PR before merging this commit.