Why Biome
Biome replaces ESLint AND Prettier in one tool — written in Rust, 10-100x faster. Linting and formatting with zero config, one dependency.
Install
npm install --save-dev @biomejs/biome
npx @biomejs/biome init
One Command
# Lint + format everything
npx biome check --write .
# Format only
npx biome format --write .
# Lint only
npx biome lint .
# CI mode (no writes, just check)
npx biome ci .
biome.json
{
"$schema": "https://biomejs.dev/schemas/1.8.0/schema.json",
"organizeImports": { "enabled": true },
"linter": {
"enabled": true,
"rules": {
"recommended": true,
"complexity": {
"noExcessiveCognitiveComplexity": "warn"
},
"suspicious": {
"noExplicitAny": "error"
}
}
},
"formatter": {
"enabled": true,
"indentStyle": "space",
"indentWidth": 2,
"lineWidth": 100
}
}
VS Code Extension
Install the Biome VS Code extension — format on save, inline lint errors, quick fixes.
Migration from ESLint + Prettier
# Auto-migrate ESLint config
npx @biomejs/biome migrate eslint
# Auto-migrate Prettier config
npx @biomejs/biome migrate prettier
Speed Comparison
Project: 5,000 TypeScript files
ESLint + Prettier: 45 seconds
Biome: 0.8 seconds (56x faster)
Key Features
- All-in-one — linter + formatter + import sorter
- Fast — written in Rust, 10-100x faster than ESLint
- Zero config — works out of the box
- 200+ lint rules — covers ESLint recommended + more
- IDE support — VS Code, IntelliJ, Neovim
- MIT license — free forever
Resources
Need to extract code quality metrics, lint configs, or project standards? Check out my Apify tools or email spinov001@gmail.com for custom solutions.
Top comments (0)