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 packageManager bun to angular.json schema #26837

Closed
MickL opened this issue Jan 10, 2024 · 3 comments · Fixed by #26962
Closed

Add packageManager bun to angular.json schema #26837

MickL opened this issue Jan 10, 2024 · 3 comments · Fixed by #26962
Labels
area: @angular/cli area: @schematics/angular feature: votes required Feature request which is currently still in the voting phase feature Issue that requests a new feature

Comments

@MickL
Copy link

MickL commented Jan 10, 2024

Command

add, new

Description

Currently accepted package managers:

"npm",
"cnpm",
"yarn",
"pnpm"

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

@angular-robot angular-robot bot added the feature: votes required Feature request which is currently still in the voting phase label Jan 11, 2024
Copy link
Contributor

angular-robot bot commented Jan 11, 2024

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.

@MickL
Copy link
Author

MickL commented Jan 11, 2024

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.

alan-agius4 added a commit to alan-agius4/angular-cli that referenced this issue Jan 25, 2024
This commit adds support to using `bun` as a package manager.

Closes angular#26837
alan-agius4 added a commit to alan-agius4/angular-cli that referenced this issue Jan 25, 2024
This commit adds support to using `bun` as a package manager.

Closes angular#26837
alan-agius4 added a commit to alan-agius4/angular-cli that referenced this issue Jan 25, 2024
This commit adds support to using `bun` as a package manager.

Closes angular#26837
alan-agius4 added a commit to alan-agius4/angular-cli that referenced this issue Jan 25, 2024
This commit adds support to use `bun` as a package manager.

Closes angular#26837
alan-agius4 added a commit to alan-agius4/angular-cli that referenced this issue Jan 25, 2024
This commit adds support to use `bun` as a package manager.

Closes angular#26837
alan-agius4 added a commit to alan-agius4/angular-cli that referenced this issue Jan 25, 2024
This commit adds support to use `bun` as a package manager.

Closes angular#26837
alan-agius4 added a commit that referenced this issue Jan 25, 2024
This commit adds support to use `bun` as a package manager.

Closes #26837
alan-agius4 added a commit that referenced this issue Jan 25, 2024
This commit adds support to use `bun` as a package manager.

Closes #26837
alan-agius4 added a commit that referenced this issue Jan 25, 2024
This commit adds support to use `bun` as a package manager.

Closes #26837
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Feb 25, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area: @angular/cli area: @schematics/angular feature: votes required Feature request which is currently still in the voting phase feature Issue that requests a new feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants