Investigate Yarn Berry v3 upgrade

[mrtnzlml]

Seems like it should be possible now. I'd suggest going through the migration guide, open a draft PR, and start modifying the tooling where necessary (src/monorepo-utils/src/getWorkspaceDependencies.js for example). Feel free to open a new discussion for it.

• https://github.com/yarnpkg/berry/releases/tag/%40yarnpkg%2Fcli%2F3.0.0
• https://github.com/yarnpkg/berry/releases/tag/%40yarnpkg/cli/3.1.0
• https://github.com/yarnpkg/berry/releases/tag/%40yarnpkg/cli/3.1.1
• https://github.com/yarnpkg/berry/releases/tag/%40yarnpkg/cli/3.2.0
• https://github.com/yarnpkg/berry/blob/master/CHANGELOG.md
• https://dev.to/arcanis/yarn-3-0-performances-esbuild-better-patches-e07

Please note: we should think about backward compatibility when doing these changes.

Alternatives

• https://docs.npmjs.com/cli/v7/using-npm/workspaces
• https://pnpm.io/

[tbergquist-godaddy]

What is our long-term plan here, is it to stay with yarn-workspaces, or use bazel?

Because bazel does not really supporting yarn workspaces, but might do so in the future. See bazel-contrib/rules_nodejs#266

I am just thinking is it worth it going to yarn berry if we want to migrate to bazel, or will we stay with a dual sort of pipeline until bazel fully supports yarn workspaces?

[mrtnzlml]

I'd say long long term Bazel and before that Yarn. We are not progressing with the Bazel thingy very much so who knows what is the timeline here.