13 appearances on the backlist front page in the last 30 days.
we rolled out the rust port of bun to claude code internally last night (not on the public builds yet) I don’t want to jinx it but nobody reported any issues yet and it’s been a day
They don’t compete - I use them together. For example /loop 30m get all the tests to pass. For each review comment, run a triage workflow that writes fixes, and runs 2 adversarial reviews per fix, then applies and pushes
Bun is using continuous parser fuzzing plus minimized repros routed to Claude, turning crash discovery into a mostly automated repair pipeline
A lot of automated crash reports on Windows have anti-cheat DLLs in the stack trace. Very hard for us to do anything about it. Chrome has a hardcoded list of these where they basically ignore crash reports from.
We’re treating this codebase like it’s under way more scrutiny than before, because it is. A year ago, rewriting an entire 700k LOC codebase in a new language in 6 days was impossible. Today, it doesn’t sound like it should work. And yet,
Bun in Rust is better than the original, and it’s going to keep getting better. We fixed a lot of bugs inherited from the original. We’re fuzzing a lot more.
today was lint errors https:// github.com/oven-sh/bun/pu ll/31116 …
not sure yet if strict enough. there’re probably more we should add? probably will also want some custom ones.
also some performance things
across about 100 open PRs, robobun/claude is gradually realizing we ported bun to rust and rewriting them XML parser is one of those PRs
The Rust port let TOML and YAML parsers recurse beyond the old test’s expected stack-overflow point, exposing a subtle benchmark/test assumption
PathString is a direct port from Zig. All usages of it point to strings with static lifetimes (stored in .bss section of the executable and never freed) or stack-local.
Bun’s rewritten component now passes the project’s test suite on Linux, Windows, and macOS across x64 and arm64, and may close roughly 200 GitHub issues