This repository has been archived by the owner on Aug 11, 2021. It is now read-only.
feat(integrity): add integrity field to publish #157
Merged
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
iarna
approved these changes
Apr 27, 2017
zkat
added a commit
to npm/npm
that referenced
this pull request
Apr 27, 2017
PR-URL: npm/npm-registry-client#157 Credit: @zkat Reviewed-By: @iarna Reviewed-By: @soldair
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.
This adds a
dist.integrityfield to published metadata, alongside the originaldist.shasum. I've already done a test publish over at npm.im/@zkat/integrity-test which you can check out yourself, andpacotehandles it just fine!We can even shove this into
npm@4and it'll start getting used right away :D