Description
While yarn v2 has a built-in patch feature, but it involves a lengthy process. To be honest, patch-package is much easier and more convenient to use. Please consider supporting Yarn v2+.
Metadata
Metadata
Assignees
Labels
No labels
Projects
Milestone
Relationships
Development
Participants
Activity
JounQin commentedon Oct 20, 2023
+1 for this, the patch experience of yarn 2+ is bad as pnpm, I love
patch-package's solution.noahm commentedon Nov 9, 2023
I agree,
patch-packagehas a much better UX and I prefer using it over yarn's native patches by far. To that end, I already have mostly working support for yarn 2+ in a fork and I hope to eventually get it into shape for a PR here.JounQin commentedon Dec 19, 2023
@noahm Would you like to share it? Or just raise it as a PR?
noahm commentedon Dec 20, 2023
@JounQin Thanks for reminding me! I just opened #506 with my changes. I wouldn't personally consider it ready to merge until new integration tests were added with more recent yarn versions, but I don't have time to keep working on it for a while. If anybody else wants to help along those lines, it would be appreciated!
feat: support yarn v2+ w/wo corepack enabled
JounQin commentedon Dec 21, 2023
I raised a new PR #507 to fix all my known issues.
feat: support yarn v2+ w/wo corepack enabled
JounQin commentedon Jan 6, 2024
I've just publish my PR #507 as
@unts/patch-package, you can give it a try.feat: support yarn v2+ w/wo corepack enabled
feat: support yarn v2+ w/wo corepack enabled