Update snyk parser and added tests for yarn berry #793
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.
I've had a couple of users reach out saying that the manifest dependency tracing does not work for yarn berry.
It appears that yarn2 / lockfile v2 with resolutions is specifically what is not working.
Given a package.json with a resolution like so:
"resolutions": {
"chalk": "^4.1.2"
}
In v1, yarn would list every version of chalk needed by the various dependencies and then specify the resolved version.
In v2, this has been reduced to just the forced version.
Recent versions of https://github.com/snyk/nodejs-lockfile-parser have changed how lockfile v2 is parsed.
I also added tests to verify that the yarn berry lock file format is read successfully, and, changes between v2 lock files are detected as expected.