-
Notifications
You must be signed in to change notification settings - Fork 12k
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 packageManager bun
to angular.json schema
#26837
Comments
This feature request is now candidate for our backlog! In the next phase, the community has 60 days to upvote. If the request receives more than 20 upvotes, we'll move it to our consideration list. You can find more details about the feature request process in our documentation. |
Sorry but this voting makes no sense. No one is checking the Github issues for upvoting features. It is common sense to support a package manager that is 33x faster than yarn. |
This commit adds support to using `bun` as a package manager. Closes angular#26837
This commit adds support to using `bun` as a package manager. Closes angular#26837
This commit adds support to using `bun` as a package manager. Closes angular#26837
This commit adds support to use `bun` as a package manager. Closes angular#26837
This commit adds support to use `bun` as a package manager. Closes angular#26837
This commit adds support to use `bun` as a package manager. Closes angular#26837
This commit adds support to use `bun` as a package manager. Closes #26837
This commit adds support to use `bun` as a package manager. Closes #26837
This commit adds support to use `bun` as a package manager. Closes #26837
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Command
add, new
Description
Currently accepted package managers:
Describe the solution you'd like
Add option
bun
. It is a fully npm-compatible package manager and 17x faster than pnpn and 33x fast than yarn.Describe alternatives you've considered
No response
The text was updated successfully, but these errors were encountered: