-
Notifications
You must be signed in to change notification settings - Fork 672
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate from Yarn v1 #1971
Comments
Yeah, I'm not sure what the best practice is these days. Yarn v2 seems like it was never embraced, but I use npm 7 at work & it's not great either. I hear good things about https://turborepo.com/ but haven't seen it being used in open source projects yet. |
I'm having the same dilemma on my stack. Going away from Yarn would also mean dropping yarn workspaces. |
We just switched to pnpm + Turborepo at work, now that Turbo is open source this seems to be the direction folks are heading in. |
BOOM you did it @hasparus |
Yarn 1 seems to be... less maintained than it used to be and bugs start to cause problems in Theme UI maintenance.
See Yarn's bug report template and yarnpkg/yarn#7734 (comment).
I'm not a huge fan of
npm@7
, though I'm not very opinionated here. I'd givepnpm
a shot.The text was updated successfully, but these errors were encountered: