`README.md` should not require developers to install `yarn classic`

[linghengqian]

Problem Description

• README.md should not require developers to install yarn classic. See https://github.com/rancher-sandbox/rancher-desktop/blob/main/README.md?plain=1#L182 .
• In https://github.com/rancher-sandbox/rancher-desktop/blob/main/package.json , "packageManager": "yarn@4.9.4", has already been specified.

Proposed Solution

• README.md should not require developers to install yarn classic.

Additional Information

• Null.

[jandubois]

• In https://github.com/rancher-sandbox/rancher-desktop/blob/main/package.json , "packageManager": "yarn@4.9.4", has already been specified.

Yes, but isn't this a chicken & egg problem: you need a package manager to install it via package.json?

[linghengqian]

Node.js obviously only comes with the npm CLI. Therefore, I think yarn classic should be changed to yarn, and the hyperlink should be removed. This way, all developers will know that they need to install Corepack, since that's required by the Yarn documentation.

npm uninstall -g yarn pnpm
npm install -g corepack
git clone --depth 1 --branch main https://github.com/rancher-sandbox/rancher-desktop.git
cd ./rancher-desktop/
corepack install

[mook-as]

Ugh, corepack was useful because it was shipped with Node.js, but now it's documented as it will not be installed again in the future? At that point we might as well just request people install yarn directly…

As for the actual issue: We probably just forgot to update the docs when we moved from yarn classic to yarn not-classic. (And it was probably me.)

[linghengqian]

I believe only updating the documentation is needed. The installation method can be instructed to follow the yarn documentation, since yarn documentation still uses corepack.

However, it's perfectly reasonable that corepack is no longer built into nodejs starting with nodejs v25; deprecated concepts related to the packageManager field should have been maintained independently. Before the merge at nodejs/package-maintenance#594 , the outdated corepack can continue to be maintained for now, while implementing devEngines will likely take several more years.🤣 See nodejs/corepack#545 . Incidentally, things have come to this point entirely because yarn is the main driving force behind corepack, see https://socket.dev/blog/node-js-takes-steps-towards-removing-corepack . Continuing to maintain corepack would only cause division within the nodejs community.

Also see https://yarn6.netlify.app/concepts/switch/ .

Yarn Switch is very similar in idea to Corepack, except it’s officially maintained by the Yarn team and is designed specifically for Yarn.
Given that the Node.js TSC decided to phase out Corepack into Node.js, we decided to refocus our efforts, and now recommend using Yarn Switch over Corepack when possible.

Are the binaries signed?
The binaries aren’t signed at the moment, but we’re working on it and hope to have that set up before Yarn 6 reaches a stable release.