Meet Biome v2: Our snappy new code gardener

TL;DR: We’re retiring ESLint and adopting Biome — a fast, Rust-built tool that lint-checks and formats our code in one go, with new smarts in v2 to catch more issues and reduce config fatigue

What is Biome (and why v2 matters)?

Biome is an all‑in‑one toolchain for JavaScript/TypeScript that combines a linter, a formatter, and an editor‑friendly language server, designed for speed and simplicity thanks to its Rust core. The new v2 release upgrades the brains: type‑aware rules, multi‑file analysis, and an extensible plugin system to grow features without growing your config headaches.

Why we’re swapping ESLint for Biome

• One tool, fewer moving parts: Biome replaces the ESLint + Prettier combo with a unified engine, so less setup, fewer plugins, and fewer mystery conflicts.
• Faster dev feedback: The Rust implementation makes linting/formatting feel snappy, which means tighter feedback loops and happier laptops.
• Formatting you already trust: Biome’s formatter targets high compatibility with Prettier (97%), so your code style won’t do a sudden plot twist.
• Smarter checks in v2: Type‑aware linting and cross‑file analysis help catch real‑world issues that single‑file rules can miss, plus a new plugin system to extend safely over time.

How to think about it (intern‑friendly edition)

• ESLint: a great code spell‑checker that often needs many dictionaries and grammar plugins.
• Biome: a speedy proofreader that also cleans up your writing as you type — and in v2 it learned context, not just spelling, so it catches “their/there/they’re” across chapters, not just sentences.

What changes for us

• Fewer configs to maintain, fewer CI steps to juggle, and a single source of truth for style + correctness — with fast, consistent results across the team.
• Same code style expectations, just enforced and formatted by a unified, Rust‑powered engine that’s kinder to your time and CPU.

And now, the dramatic ending: We’re going Biome. Fewer plugins, faster feedback, smarter rules — because clean code shouldn’t feel like cardio
Dive deeper in the official Biome documentation to get started https://biomejs.dev/guides/getting-started/