This is a follow-up to #8058. We have tested the fix applied for this issue on multiple customer projects. The outcome is that it has improved the results from the Yarn2+ analysis significantly; however, compared to the results reported for Yarn classic, there are still dependencies that are not found.
Here are some concrete numbers:
- In one project, the number of dependencies reported for Yarn2+ went up from 499 to 636, while Yarn classics finds 1028.
- For another project, the number of Yarn2+ dependencies went up from 109 to 493, while Yarn classics finds 685.
I hope that we will be able to provide more details about which packages are missing later.
This is a follow-up to #8058. We have tested the fix applied for this issue on multiple customer projects. The outcome is that it has improved the results from the Yarn2+ analysis significantly; however, compared to the results reported for Yarn classic, there are still dependencies that are not found.
Here are some concrete numbers:
I hope that we will be able to provide more details about which packages are missing later.