Support yarn v2

[oliversalzburg]

In a repository using yarn 2, vsce package will fail trying to enumerate dependencies:

 ERROR  Command failed: yarn list --prod --json

To reproduce, in an extension repository, use:

yarn set version berry
yarn install
vsce package

[joaomoreno]

What does yarn list --prod --json return?

Can I clone your repo and try it out?

[oliversalzburg]

It returns Usage Error: Couldn't find a script named "list"., as it's not a valid yarn2 command: https://yarnpkg.com/cli/

My reproduction should work in any extension repository, but I created a fresh one that should showcase it perfectly: https://github.com/oliversalzburg/vsce-yarn2-support

[SheepReaper]

Likewise, yarn 2 omits the run command since it's not needed. Yarn 2 is not meant to be installed globally (yet) If there is yarn available in global, then it's probably v1. I don't know if vscode is running an embedded yarn or global yarn, but ordinarily yarn v1 checks if yarn 2 (or any yarn) is installed in the repository and runs it instead.

In my case, running an npm script from the side panel results in this:

The terminal process "C:\Program Files\PowerShell\7\pwsh.exe -Command yarn run dev" terminated with exit code: 1.

Which is incorrect, it should just be yarn dev

[jewlexx]

I had the same issue, here was my temporary fix, although it can be annoying,

1. Optional: Checkout a new temp branch so that package-lock.json and other npm files to carry over
2. Run npm i
3. Run vsce package --no-yarn

[latipun7]

just info, as of now yarn list still not implemented in yarn berry: https://yarnpkg.com/getting-started/migration#not-implemented-yet

[SchoofsKelvin]

Not the cleanest/best solution, but this is how I circumvented this issue:

• Configure your .yarnrc.yml with a lockfileFilename different from yarn.lock
• Run vsce with the --yarn parameter (since it won't detect Yarn using the yarn.lock anymore)

This will make vsce skip its whole process of looking at your dependencies and partially including node_modules in the packaged extension. Skipping this process also skips its internal yarn list (and because of --yarn also npm ls) which prevents this error from happening.

The only issue with this is that vsce might bundle some items in node_modules if it isn't in .vscodeignore or something similar. You'd lose that "bundling" of course (which you would lose anyway if using Yarn PnP), but if your extension doesn't have any dependencies or you bundle it using e.g. Webpack, this is a non-issue.

Of course, having vsce support Yarn 2 natively is still better.

[itspngu]

With the freeze of yarn v1 this should perhaps be re-prioritized.

[YXL76]

With the freeze of yarn v1 this should perhaps be re-prioritized.

See #439. I think yarn v2 is supported.