This repository has been archived by the owner on Apr 6, 2023. It is now read-only.
Update npm-shrinkwrap and shrinkwrap file so this module is installable #23
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
…uild shrinkwrap file. NPM 2 has been shipping with Node.js since v0.11.14 in late 2014, so it seems save to move up to shrinkwrap 200.x, which is for NPM 2+. Fixes aymericbeaumet#22.
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 updates npm-shrinkwrap to the latest (v200.5.1), which installs fine and is also compatible with NPM 2+. It also uses that version to rebuild the shrinkwrap file to only include non-dev dependencies, so consumers of this module (or a dependent of this module) don’t need to know they have to
npm install --no-shrinkwrap, especially when the reason for that is a sub (or sub-sub-sub) dependency.Since it only affects how shrinkwapping works and all tests still pass fine, this ought to be pretty safe.
Also fixes #22.