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

[Feat] Add support for yarn berry #18

Closed
hamlim opened this issue Jun 24, 2022 · 0 comments · Fixed by #19
Closed

[Feat] Add support for yarn berry #18

hamlim opened this issue Jun 24, 2022 · 0 comments · Fixed by #19

Comments

@hamlim
Copy link
Collaborator

hamlim commented Jun 24, 2022

Problem Statement

The current behavior with --packageManager yarn defaults to using yarn --silent workspaces info which no longer exists/works with yarn berry (2.0 +). This breaks when adopting the one-version rule in yarn berry monorepos.

Proposed Solution

Introduce a berry packageManager option, that uses yarn workspaces list --json to determine the workspaces in the repo!

Alternatives Considered

Have the default behavior of --packageManager yarn assume yarn berry only and not yarn v1, but this seems overly restrictive if teams want to adopt this package in yarn v1 monorepos.

Additional Context

No response

@finn-orsini finn-orsini mentioned this issue Jun 27, 2022
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant