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.
Opening this to deal with #36 and microsoft/lage#129
Supports parsing yarn2 lockfiles directly. This change omits a portion of the normalization logic from from snyk's similar change.
When snyk is importing the lockfile, they create every possible representation of a dependency and store duplicate entries for each in their internal representation of a package's lockfile. No other parser in workspace-tools does this at present, so I instead opted for normalizing out the protocol from npm: and file: dependencies (to bring it in line with yarn1 lockfiles), and omitting dependencies where there are incongruities between yarn2's locking and pnpm/yarn1's locking (e.g. workspace dependencies).