I Replaced ESLint + Prettier With Biome. Here’s the Benchmark.

One Rust binary. One config file. 25× faster formatting, 20× faster linting. Here's what you actually give up.

For more than a decade the answer to “how do I keep my JavaScript clean?” was the same two-headed reflex: install eslint, install prettier, then spend an afternoon wiring them together so they stop fighting each other.

Add the TypeScript parser, an import plugin, a React plugin, an accessibility plugin, a config to disable the rules Prettier already handles — you end up with a dozen dependencies and four config files just to format and lint code you haven’t written yet.

Biome collapses that entire stack into a single binary.

The benchmark numbers (official, from biomejs.dev)

• ~25× faster than Prettier for formatting
• ~20× faster than ESLint for linting
• A multi-second CI lint step becomes sub-second

It’s written in Rust, runs as a single native binary, parallelizes across cores — no per-file Node.js overhead.

What Biome replaces

One dependency (@biomejs/biome), one config (biome.json): formatter, linter, and import sorter. That's it.

Migration: biome migrate eslint and biome migrate prettier translate most of your existing config automatically. Most teams get to a working biome.json in minutes.

The honest trade-off

ESLint has thousands of community rules. Biome doesn’t cover every one. If you depend on a niche plugin or a custom rule, you may not find an equivalent yet. The common pattern: run Biome for everything it covers, keep a thin ESLint config only for the specific rules it doesn’t.

Full hands-on — benchmark breakdown, real migration steps, what’s missing, and when NOT to switch:

👉 alekseialeinikov.com/en/blog/topics/programming/biome-2026-replace-eslint-prettier-benchmark