Bun adds built-in bun lint and bun fmt: reads ESLint/Prettier configs, 1,021 rules, 2.9s vs Prettier's 295s CPU on vscode format check
On Oct 12 Bun merged PR #44805, adding native bun lint (1,021 built-in rules, reads ESLint and oxlint configs, type-aware rules included) and bun format/bun fmt (matches Prettier/oxfmt output across JS/TS/CSS/HTML/Vue/YAML/Markdown and more). On vscode's source, Bun reports a format check taking 2.9s of CPU time versus 295s for Prettier 3.9.9. It is in main and the docs, but not yet in the v1.4.3 stable release.
Key Takeaways
bun lintships 1,021 rules: 69,640 ESLint rule-test cases with 0 failures and 27,702 oxlint cases with 0 failures (PR #44805, vendor-reported)bun formaton Prettier 3.9.9's tests/format: 9,728 pass, 5 fail; across 330 real repos it matches oxfmt 0.72 byte-for-byte in 95% of runs (227/240) and Prettier in 77% (57/74)- vscode
src/(10,149 files, 8 cores): format check CPU time 2.9s for bun vs 5.5s oxfmt, 20s Biome 2.5, 295s Prettier 3.9.9; lint recommended 0.25s vs oxlint 0.51s wall - With vscode's own ESLint config (8 plugins, 13,069 files): 15.8s vs ESLint 10's 404s, about 26x (earlier build, being re-measured); with heavy JS plugins the median gain is only 1.7x
- Cost: the linux-x64 binary grows from 85.18MB to 100.09MB (+14.91MB); the latest stable v1.4.3 (Oct 10) does not include it yet