I am shocked by how good and comprehensive the bun docs & ecosystem is.

Its so well contained I never need to look outside its ecosystem for basic components. It's a true "Batteries Included" runtime.

▲

Retr0id 4 hours ago | parent | next [-]

Last time I read the bun docs I spotted an off-by-one bug in sample code, so I opened a github issue. An AI bot responded, confirming the issue, and opened a PR to fix it - A simple "+ 1" added in the right place. Two other AI bots reviewed the PR, which went on for several rounds of "improvements". Last time I checked, neither the issue nor the PR received any human attention (actually I just checked again, and the PR has been closed by stalebot).

▲

Aurornis 4 hours ago | parent | next [-]

> (actually I just checked again, and the PR has been closed by stalebot).

Can you provide the link?

▲

Delgan 4 hours ago | parent | next [-]

I, too, was curious to see it in practice.

Here is the ticket opened by @retr0id: https://github.com/oven-sh/bun/issues/28030

And here is the swarm of bots / LLMs / agents that open, review and bikeshed the PR before it's closed by the stalebot: https://github.com/oven-sh/bun/pull/28031

It's hilarious. But also a little sad.

▲

Retr0id 3 hours ago | parent | next [-]

Yup, that's the one.

	▲	Phelinofist 2 hours ago \| parent [-]
		That's pure comedy

▲

dgellow an hour ago | parent | prev | next [-]

Ok, you didn’t lie, it’s extremely funny, the stalebot at the end is such a good punchline!

▲

skeledrew an hour ago | parent | prev [-]

Why sad?

▲

tomjakubowski 2 hours ago | parent | prev [-]

Here's a trivial docs issue I opened, where I had a similar experience:

https://github.com/oven-sh/bun/issues/31233

The difference is that the PRs to fix that problem were already open when I created the issue. I was unaware of them (I only searched for duplicate issues, not PRs addressing the problem). The robobun comment implies there are 5 open PRs addressing it, but I could only find two. They still haven't been merged, a month later.

https://github.com/oven-sh/bun/pull/30677 <-- later rolled up into:

https://github.com/oven-sh/bun/pull/30747

▲

asxndu 3 hours ago | parent | prev [-]

Was the bug actualy soved?

	▲	masklinn 2 hours ago \| parent [-]
		No, it was closed as stale.

▲

jvidalv 4 hours ago | parent | prev | next [-]

Bun is so good that can’t be used as server and only as local script runner.

https://discord.com/channels/876711213126520882/148058965798...

Leaks memory left and right. And the core team seems unable to fix it.

▲

fg137 3 hours ago | parent | prev [-]

Yet I rarely hear about it being used in production systems and replacing Node.js.

▲

tomjakubowski 2 hours ago | parent | next [-]

From what I've heard there are two main use cases:

- People use bun as an all-in-one frontend web bundler. Personally, I just use esbuild (and webpack, if I'm working on a system using its module federation, like Jupyterlab). My understanding is bun has a machine-translated port of esbuild (ported to Zig, then to Rust) built into it.

- Claude Code runs on bun.

The second point has to be why Anthropic acquired them.

▲

doodlesdev 2 hours ago | parent | prev | next [-]

It famously is extremely memory leaky, with the core team having no idea how to fix it. With the new AI-automated unsafe Rust migration, this piece of slop may never actually become production-ready.

▲

egorfine an hour ago | parent | prev [-]

I run it in production for multiple systems.

Ready to migrate back to node once the slop version is out.

▲

dgellow an hour ago | parent [-]

Why not deno?

	▲	egorfine 24 minutes ago \| parent [-]
		I'm not sure deno has a future.