This repository has been archived by the owner on Apr 1, 2022. It is now read-only.
Analyses-725: Uses safe lookup for yarn.lock #369
Merged
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.
Overview
Uses safe lookup, to address scenarios when, yarn v1 has deep dependencies (ex: @f/sub-dep, e.g.) from resolved dependency (eg: @f/a@0.0.1, typically file or remote sourced) which are not specified at root level:
Acceptance criteria
Testing plan
Test against yarn lock file provided in: fossas/team-analysis#725
Before
After
Risks
N/A
References
Closes fossas/team-analysis#725
Checklist
docs/
.Changelog.md
if this change is externally facing. If this PR did not mark a release, I added my changes into an# Unreleased
section at the top.