Should we move to pnp/yarn 2 for some typescript projects ?

[benoitf]

Is your enhancement related to a problem? Please describe.

yarn 2 comes with pnp and zero-install.

we have some repositories like plugin-registry, dashboard, etc that could be converted to yarnv2/berry

Pro: it could avoid to download all dependencies after cloning the repositories and allow better 'downstreaming' as there would be no 'internet connection required' to grab npm dependencies

cons: it would make .yarn/pnp dependencies committed into the repository, thus making the repository bigger.

note: for che-theia, it's depending on upstream theia

Describe the solution you'd like

Wanted to hear feedback from people.
it's like the vendor/ for go committed or not :-)

Describe alternatives you've considered

We could switch only on downstream repositories

Additional context

[nickboldt]

Having ALL sources already committed to the upstream would make downstreaming WAY simpler as we wouldn't need to:

• copy upstream to downstream, applying branding/transforms as needed
• container build locally to fetch all the deps, using one variant of the Dockerfile (use internet to resolve deps)
• tarball those deps
• commit the tarball into the downstream repo
• container build in Brew, using the fetched deps tarballs, using a second variant of the Dockerfile (build offline, unpacking tarball to get deps)

Instead we would have:

• copy upstream to downstream, applying branding/transforms as needed, including vendored sources / dependencies
• container build in Brew, using the deps already in the repo, using a single variant of the Dockerfile

So 100% in favour of this plan, for node/ts components that become images, and for chectl/crwctl too.

[che-bot]

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

[ericwill]

AFAIK we still face issues with yarn v2 on s390x, so we are not doing this.