-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
support yarn version 2 #36
Comments
It looks like parsing yarn2 is possible with the And here is how to test the lockfile version If using an external library is an option, https://github.com/snyk/nodejs-lockfile-parser can parse lockfiles in several formats including yarn2. |
Are there any plans to fix this? |
The external lockfiles parser would be okay if it's relatively clean and simple (and well maintained)! |
Sooooo, first off, I have a great coworker who is also interested in this. He is going to contribute a disabled, failing test that tests against yarn 2 / 3 here first. I'll then have the opportunity to fix it by either consuming a new package (like nodejs-lockfile-parser) or consuming the @yarnpkg/core from v2+ directly. Some implementation notes: We'll need a failing test here: https://github.com/microsoft/workspace-tools/tree/master/src/__tests__ And likely a yarn 2/3 fixture added to: https://github.com/microsoft/workspace-tools/tree/master/src/__fixtures__ |
Projects which use Yarn version 2 are facing caching issue with lage because there is a logical dependency of parsing yarn lock file in workspace-tools. current workspace-tools can only parse lock files of yarn version 1, it breaks for yarn version 2 lock files.
#microsoft/lage#129
The text was updated successfully, but these errors were encountered: