What if one tool replaced ESLint AND Prettier — running 35x faster because it is written in Rust?
Biome is a toolchain for JavaScript, TypeScript, JSON, CSS, and GraphQL. It handles linting, formatting, and import sorting in one pass.
Why Biome
- 35x faster than ESLint + Prettier combined
- One tool — no more ESLint + Prettier + eslint-config-prettier conflicts
- Zero config — sensible defaults, works immediately
- Import sorting — built in, no extra plugin
- CSS and JSON — not just JS/TS
- Editor integration — VS Code, JetBrains, Neovim
Quick Start
npx @biomejs/biome init
# Format
npx biome format --write .
# Lint
npx biome lint .
# Both at once
npx biome check --write .
biome.json
{
"formatter": {
"indentStyle": "space",
"indentWidth": 2
},
"linter": {
"rules": {
"complexity": { "noForEach": "warn" },
"suspicious": { "noExplicitAny": "error" }
}
},
"organizeImports": { "enabled": true }
}
Migration from ESLint + Prettier
npx @biomejs/biome migrate eslint --write
npx @biomejs/biome migrate prettier --write
Biome reads your existing ESLint and Prettier configs and converts them.
Real Use Case
A monorepo had ESLint taking 45 seconds in CI — with 15 plugins, each adding startup time. After migrating to Biome, the same lint + format ran in 1.2 seconds. CI pipeline time dropped by 2 minutes per commit. Developers stopped disabling lint checks because they were no longer slow.
When to Use Biome
- Any JavaScript/TypeScript project
- Replacing ESLint + Prettier setup
- Monorepos where lint speed matters
- Teams wanting simpler tooling config
Get Started
Visit biomejs.dev — open source, MIT licensed.
Need custom data pipelines or scraping solutions? Check out my Apify actors or email me at spinov001@gmail.com for custom solutions.
Top comments (0)