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 away from Yarn 1 #28146

Open
dbkr opened this issue Oct 3, 2024 · 0 comments
Open

Migrate away from Yarn 1 #28146

dbkr opened this issue Oct 3, 2024 · 0 comments
Labels
A-Developer-Experience T-Task Tasks for the team like planning

Comments

@dbkr
Copy link
Member

dbkr commented Oct 3, 2024

Your use case

Somehow I don't think we had an issue for migrating away from yarn 1. Here is one.

We could upgrade to yarn n although I don't really see the point: it's about as much effort to move to something better. npm is fine nowadays. I believe pnpm is also fine, although doesn't tend to come as standard on github actions runners etc.

Opinions welcome on what to move to.

Have you considered any alternatives?

No response

Additional context

No response

@dbkr dbkr added the T-Task Tasks for the team like planning label Oct 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Developer-Experience T-Task Tasks for the team like planning
Projects
None yet
Development

No branches or pull requests

1 participant