Creates an optimised dep-tree version for yarn by reusing package-lock logic
I extracted everything that is shared from package-lock-parser into lock-parser-base
The implications for that ticket is ~220 million nodes for around 900 dependencies
Before this change, yarn projects looks like the right tree while npm projects looks like the left one
What this does
Creates an optimised dep-tree version for yarn by reusing package-lock logic I extracted everything that is shared from
package-lock-parser
intolock-parser-base
The implications for that ticket is ~220 million nodes for around 900 dependencies
Before this change, yarn projects looks like the right tree while npm projects looks like the left one![image](https://user-images.githubusercontent.com/15211590/109222065-4df20700-77c2-11eb-91f9-a2e85c062e51.png)