Yarn v3+ support and performance

[JamieMagee]

Currently, Component Detection explicitly supports Yarn v1 and v2. We've had some customer reports of poor performance of our yarn detection.

Unfortunately, yarn support has gotten a little more complex recently. Yarn v1 is now considered yarn 'classic'. Yarn 2 and 3 are a complete rewrite of yarn (and are sometimes called 'berry'). The lockfile version has incremented a lot.

Yarn version	lockfile version
1+	1
2.0.0-rc.2	2
2.0.0-rc.5	3
2.0.0-rc.15	4
3.1.0-rc.12	5
3.2.0-rc.12	6
4.0.0-rc.1	7
4.0.0-rc.47	8

We need to evaluate whether or not these lockfile changes are relevant to Component Detection, and the performance of our yarn detection for large projects in general.

AB#2099326

[lvivski]

Hi @JamieMagee, I see you had several PRs already merged. Can Component Detection already be used with new Yarn versions?

[MLoughry]

As of testing it on Wednesday, I was still hitting the 6-minute timeout: https://outlookweb.visualstudio.com/Outlook%20Web/_build/results?buildId=1264416&view=logs&j=ca395085-040a-526b-2ce8-bdc85f692774&t=3a7260a1-afda-5883-4f64-f6a170823839

[melotic]

Hi @JamieMagee, I see you had several PRs already merged. Can Component Detection already be used with new Yarn versions?

This was for infrastructure to support V3. We do not have a specific detector for it yet.

[lvivski]

@melotic is there anything we can do to help with the development? Yarn@3 is over 3 times faster at our scale than v1. We would really like to be able to migrate to Yarn@3.

[melotic]

@melotic is there anything we can do to help with the development? Yarn@3 is over 3 times faster at our scale than v1. We would really like to be able to migrate to Yarn@3.

We're currently planning work to prioritize this in this quarter

[lvivski]

Hey @melotic, is there any update on this issue?

[grvillic]

@lvivski - Yarn V3 was already merged and enabled by default in the detector. Please give it a go and let us know if you see any issues with it. See release v4.0.8.