Implement RFC 0014: Enable Support for Yarn Berry

[thitch97]

Context

RFC
Exploration

This buildpack should be re-written such that it supports a codepath for installing application dependencies using Yarn Berry.

Details

• API: The buildpack should require node and yarn during build and should provide either node_modules OR yarn_pkgs.

• The logic for installing dependencies with Yarn Classic should be kept as separate as possible from that of Yarn Berry; preferably as separate packages.

Acceptance Criteria

Given an application which uses Yarn Berry to manage its dependencies:

• when pack build is run with the yarn-install buildpack, it should pass detection and build successfully.
• The required dependencies should be installed in the resulting container.

[jwhitcraft]

Any update on this?

[loewenstein-sap]

I am wondering as well, what the state of this is. It looks pretty old and the PR looks devastatingly large. @thitch97 are you actively working on this?

[thitch97]

@jwhitcraft @loewenstein-sap Hi folks, I'm no longer actively working on this and I think it is past time for me to unblock the track. I've closed out the PR but I've left the branch intact for now in case there are any useful insights to glean from the admittedly large changeset. I'd be happy to see someone else try their hand at implementing the RFC if they feel inclined to do so!

[loewenstein-sap]

@paketo-buildpacks/nodejs-maintainers Is Yarn berry support on anyone's agenda?
@paketo-buildpacks/steering-committee If the current Node maintainers do not see this on their agenda, what would be the process? Would we deprecate the RFC? Or do we have any other means to make this transparent to anyone interested?