fix: Stop checking duplicate yarn@1 entries
yarn@1 lock files seem to be parsed interestingly by it's own parser. If you have an entry like:
lodash@4.17.20, lodash@^4.17.20:
version "4.17.20"
resolved "<url>"
integrity "<hash>"
it will present as an object like:
{
"lodash@4.17.20": <obj>,
"lodash@^4.17.20": <obj>
}
The <obj>
will be a reference to the same object if the multiple keys
have been defined in the line.
Deduplicating the entries of this object will make errors a little less verbose and potentially has performance implications as well (less network requests).
Closes #12 (closed)
Edited by Lukas 'ai-pi' Eipert