[Documentation] Provide a baseline infrastructure description for development

[cwatsonc]

[Documentation] Provide a baseline infrastructure description for development

[cwatsonc]

@richardaum the issue is discussed on the "rationales" link on the main issue -- [email protected] is about to be orphaned for support -- the yarn team is poised to update to 3.x.x in the next 6 months and will ensure that fact.

The risk of staying on orphaned versions outweighs any risk of moving forward. @ProspectPyxis agrees with that in comments but was thinking moving to an alternative pnpm -- that has a bigger risk of than an upgrade of our existing tooling. As is mentioned in the rationale -- many of the improvements are initially OPTIONAL and don't require immediate adoption -- it's a much more graceful jump than ripping and replacing with an untested alternative IMO

See Also yarn 2 migration and rationales
See Also alternative package managers

[cwatsonc]

created PR #1013

[richardaum]

Yarn 2 is a radical shift in build behavior and structure

Yes, it is, definetely. And I think in that case the costs overcome the benefits. I mean, Yarn 1 is doing a good job here, right?