Skip to content
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

Closed
hasparus opened this issue Oct 7, 2021 · 5 comments
Closed

Migrate from Yarn v1 #1971

hasparus opened this issue Oct 7, 2021 · 5 comments
Labels
dependencies Update one or more dependencies version internal Changes only affect the internal API

Comments

@hasparus
Copy link
Member

hasparus commented Oct 7, 2021

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 give pnpm a shot.

@hasparus hasparus added the dependencies Update one or more dependencies version label Oct 7, 2021
@lachlanjc
Copy link
Member

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.

@fcisio
Copy link
Collaborator

fcisio commented Oct 15, 2021

I'm having the same dilemma on my stack. Going away from Yarn would also mean dropping yarn workspaces.
I kinda feel like Yarn v2 could be great, I heard good things. But I have not yet actually used it with anything.

@hasparus
Copy link
Member Author

@lachlanjc
Copy link
Member

We just switched to pnpm + Turborepo at work, now that Turbo is open source this seems to be the direction folks are heading in.

@lachlanjc lachlanjc added the internal Changes only affect the internal API label Dec 30, 2021
@hasparus hasparus changed the title Migrate from of Yarn v1 Migrate from Yarn v1 Jan 3, 2022
@lachlanjc
Copy link
Member

BOOM you did it @hasparus

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Update one or more dependencies version internal Changes only affect the internal API
Projects
None yet
Development

No branches or pull requests

3 participants