feat: add bun support to package manager component

[MohamedH1998]

Summary

Add bun support to package manager component

Screenshots (optional)

Documentation checklist

• Is there a changelog entry (guidelines)? If you don't add one for something awesome and new (however small) — how will our customers find out? Changelogs are automatically posted to RSS feeds, the Discord, and X.
• The change adheres to the documentation style guide.
• If a larger change - such as adding a new page- an issue has been opened in relation to any incorrect or out of date information that this PR fixes.
• Files which have changed name or location have been allocated redirects.

[github-actions]

This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:

Pattern	Owners
*.ts	@cloudflare/content-engineering, @kodster28

[github-actions]

Preview URL: https://c2f60a0e.preview.developers.cloudflare.com
Preview Branch URL: https://feat-add-bun-to-pkm.preview.developers.cloudflare.com

[Cherry]

Is Bun actively supported in wrangler (etc.)? This was intentionally removed in the past as it's caused issues in wrangler, c3 and others: #22525

Other ref: cloudflare/workers-sdk#8889

[threepointone]

for package management, it should work just fine there. for wrangler dev, we should be using node when the cli is started up, if not that's a bug.

[threepointone]

tbh even if it fails with bun, we should file bugs there, we're friends and they should be able to fix it

[Cherry]

Agreed bugs should be filed and fixed, but I believe this component is used by more than just package management today, like for actual deploy/dev commands, such as:

• https://feat-add-bun-to-pkm.preview.developers.cloudflare.com/workers/framework-guides/automatic-configuration/
• https://feat-add-bun-to-pkm.preview.developers.cloudflare.com/workers/development-testing/environment-variables/#basic-setup

etc.

which could/will have various issues with Bun and are very much not supported as per: https://x.com/MattieTK/status/2037810746868822458

• Running "wrangler pages deploy" via Bun.spawnSync searches for Node instead of bun oven-sh/bun#7703
• Cloudflare Wrangler Crashes Bun oven-sh/bun#10464
• Vite dev server not starting with @cloudflare/vite-plugin and Bun ^1.3 oven-sh/bun#24229
• bunx silently swallows command exit codes/errors oven-sh/bun#26674

Perhaps this should only show bun if the type isn't set to create, exec, run, etc. and any other non-package management commands? I'd argue it's still pretty confusing from a UX and education standpoint to show bun commands at all until it works across the board though personally.

[threepointone]

Passed them on to the team!

[MattieTK]

@MohamedH1998 I agree it would be good to expand the component to not show the following commands in bun if that is the prop delivered

Perhaps this should only show bun if the type isn't set to create, exec, run, etc.

Bun is a great package manager so I appreciate the value in doing this, but we don't want folks to run into problems using bun as their script runner.

[MattIPv4]

I'd argue it's still pretty confusing from a UX and education standpoint to show bun commands at all until it works across the board though personally.

Just want to ++ this, adding any bun commands to the docs, when it doesn't work with everything, seems like a pretty confusing message to be sending to new users who won't understand this nuance... they'll start using bun because some docs commands have it, and then run into commands that don't work...

[threepointone]

it's now been scoped to only add/install, so I think it's ready to go?