feat: detect and scan npm-shrinkwrap.json with precedence over package-lock.json#356
Merged
Merged
Conversation
sonukapoor
force-pushed
the
feature/issue-348-npm-shrinkwrap
branch
from
b19f922 to
5f07903
Compare
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 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.
Adds support for
npm-shrinkwrap.json, matching npm's own resolution order where shrinkwrap takes precedence overpackage-lock.json.The shrinkwrap file uses the identical format as
package-lock.json, so it reuses the existingloadFromPackageLockparser. A new"npm-shrinkwrap"source label is added toScanSourcethroughout the type system, including the exhaustiveLOCKFILE_NAMESrecord insarif.ts.Closes #348