-
-
Notifications
You must be signed in to change notification settings - Fork 301
Add support for yarn v2+ #496
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
+1 for this, the patch experience of yarn 2+ is bad as pnpm, I love |
I agree, |
@noahm Would you like to share it? Or just raise it as a PR? |
@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! |
I raised a new PR #507 to fix all my known issues. |
I've just publish my PR #507 as |
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+.
The text was updated successfully, but these errors were encountered: