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

Add support for yarn@v1 for the javascript backend #18526

Closed
tobni opened this issue Mar 18, 2023 · 0 comments · Fixed by #18928
Closed

Add support for yarn@v1 for the javascript backend #18526

tobni opened this issue Mar 18, 2023 · 0 comments · Fixed by #18928
Labels
backend: JavaScript JavaScript backend-related issues enhancement

Comments

@tobni
Copy link
Contributor

tobni commented Mar 18, 2023

Is your feature request related to a problem? Please describe.
Some users might prefer yarn over npm, most likely because they're migrating a codebase.

Describe the solution you'd like
Users can pick a default package manager for the project in the nodejs subsystem. Users can also choose a particular package manager for different package_json targets (a nodejs resolve should require the same one for all, though).

Describe alternatives you've considered
Only support npm. Will make some adopters shy away

Additional context
Blocked on #18525

@huonw huonw added the backend: JavaScript JavaScript backend-related issues label Mar 18, 2023
stuhood pushed a commit that referenced this issue May 15, 2023
Uses corepack to enable support for using the `yarn` v1 package manager.
V2 onward is not supported at this time.

Fixes #18526
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend: JavaScript JavaScript backend-related issues enhancement
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants