Biome as a single linter and formatter

Biome (successor spirit to Rome) bundles formatter + linter in a Rust binary—fast enough to run on every keystroke in large repos. Tradeoff: plugin ecosystem is smaller than ESLint’s decades of community rules.

Speed and developer UX#

biome check --write formats and fixes safe issues in one pass. CI benefits from sub-second cold starts compared to loading hundreds of ESLint plugins.

Migration#

Start with biome migrate eslint / prettier helpers, then tighten rules incrementally. Keep type-aware checks on TypeScript-ESLint if Biome rules do not cover your policies yet—running both temporarily is acceptable.

Monorepos#

biome.json supports overrides per directory—mirror package boundaries (stricter in apps/web, looser in legacy/).

Summary#

Biome wins on latency and simplicity; ESLint wins on depth of rules. Pick Biome when speed and unified formatting are top priorities and your rule set fits; hybrid until parity catches up.