Unvendor Yarn; favor Corepack for installation #243
Conversation
According to the Yarn documentation, Yarn no longer needs to be bundled with a project, but rather, installing Yarn ought to be done using [Corepack](https://yarnpkg.com/corepack), which is shipped in modern Node versions. This commit removes the Yarn binary from the repo and updates the installation instructions in the README to match.
|
Looks like corepack support is still pending in |
|
Devs will still need to run |
* ci: run `corepack enable` as part of prepare * chore(ci): do redundant setup-node step before checkout to enable yarn v4 before deps install - makes nodejs version `lts/*` explicit in ci workflow
There was a problem hiding this comment.
I kind of dislike the hacks we have to do here. It makes the GitHub workflow files longer and more complicated than they need to be. It's true Corepack is the recommended way to install Yarn, but it doesn't mean that the yarnPath method is deprecated. So I'm inclined to not do this and keep the current way. Then again, the downside to the current approach is that projects are obligated to use the same version of Yarn as in the template, which doesn't seem completely necessary either. Sigh...
Agreed. I still find it less ugly and less objectively bad than redundantly checking in the entire minified yarn cjs file without additional integrity-checking in every repo... |
|
Yeah, that's true. Okay, I'm convinced. ✅ |
|
@mcmire ping |
According to the Yarn documentation, Yarn no longer needs to be bundled with a project, but rather, installing Yarn ought to be done using Corepack, which is shipped in modern Node versions. This commit removes the Yarn binary from the repo and updates the installation instructions in the README to match.
Examples
(None)