| Product | Biome |
| Website | biomejs.dev |
| Category | Code Quality / Toolchain |
| License | MIT / Apache 2.0 |
| Built With | Rust |
What Is Biome?
Biome is a toolchain for web projects. It provides a fast linter (200+ rules), a fast formatter (compatible with Prettier), and import sorting — all in a single Rust binary. One tool replaces ESLint, Prettier, and import-sorter. It supports JavaScript, TypeScript, JSX, TSX, JSON, CSS, and GraphQL.
The speed difference is dramatic. Biome formats a large codebase in milliseconds where Prettier takes seconds. Linting is similarly fast. The Rust implementation processes files in parallel and avoids the overhead of a Node.js runtime. For CI pipelines and large monorepos, the time savings compound.
Key Features
Unified Tool
One configuration file (biome.json), one CLI (biome check), one binary. No coordinating ESLint and Prettier configs, no eslint-config-prettier to disable formatting rules, no import-sorter plugin. Install Biome and run biome check --fix.
200+ Lint Rules
Biome includes rules from ESLint core, typescript-eslint, eslint-plugin-react, and more. Many rules include safe auto-fixes. The rule set is curated: Biome doesn’t aim for 100% ESLint parity, but covers the rules most projects need.
Prettier-Compatible Formatter
Biome’s formatter produces output compatible with Prettier for the vast majority of code. Switch from Prettier to Biome and your diffs stay clean. The compatibility target means the formatting is familiar and your team doesn’t need to adjust.
Zero Config to Start
Run npx @biomejs/biome check and it works. Biome ships with sensible defaults that cover most projects. Create biome.json when you need to customize.
Who Is This For?
- Teams frustrated with ESLint + Prettier config complexity
- Large codebases and monorepos where linting/formatting speed matters
- New projects that want a single tool instead of three
- CI pipelines that would benefit from faster check times
Pros
- Dramatically faster than ESLint + Prettier
- One tool replaces three (linter + formatter + import sorter)
- Zero config to start
- Prettier-compatible formatter output
- 200+ lint rules with auto-fix
- No Node.js runtime overhead
Cons
- Smaller rule ecosystem than ESLint
- No custom rule API (ESLint plugins won’t work)
- CSS and GraphQL support is newer
- Less community documentation
- Migrating existing ESLint configs takes effort
Verdict
Biome is the most compelling alternative to the ESLint + Prettier combination. The unified tool approach eliminates config coordination, and the Rust-powered speed is noticeable on any project with more than a few files. For new projects, Biome is worth starting with: zero config, fast feedback, and one tool to maintain.
The main reason to stay with ESLint is the plugin ecosystem. If your project depends on ESLint plugins that Biome doesn’t cover (eslint-plugin-security, eslint-plugin-testing-library, custom rules), ESLint remains necessary. For projects that use only the standard ESLint and Prettier rules, the migration to Biome is straightforward and the speed improvement is immediate.
Build a code quality or developer tool?
Get reviewed and linked from our 27-site network.
See Packages