Biome (formerly Rome) replaces ESLint and Prettier with a single fast tool. Its vocabulary for linting, formatting, and auto-fixing is increasingly common in modern JavaScript project discussions.
0 / 5 completed
1 / 5
A developer says: 'Replace ESLint and Prettier with Biome for faster linting and formatting.' What is Biome?
Biome (formerly Rome) is a Rust-based toolchain that combines a linter and formatter in one tool. It's significantly faster than the ESLint + Prettier combination because it's written in Rust and processes files in parallel. It's also opinionated — fewer configuration options means less setup. In discussions: 'switch to Biome' means consolidate linting and formatting into one tool and gain speed, at the cost of some configurability.
2 / 5
A PR config update changes biome.json to enable recommended rules. What does lint rules mean in this context?
Lint rules are static analysis checks: they examine your code for potential bugs (no-unused-vars), performance issues, style violations, or unsafe patterns — without running the code. recommended enables a curated set of rules that Biome considers broadly applicable. In reviews: 'the lint rule flags this' means a static analysis check caught an issue. 'Disable the rule' means mark it as allowed.
3 / 5
A developer says: 'Biome formats the code differently from Prettier — check the diff.' What does a formatter do?
A formatter rewrites code to follow consistent style conventions: indentation, quote style, trailing commas, line length. It changes how code looks, not what it does. Biome and Prettier are both formatters; they make slightly different style choices. In discussions: 'the formatter changed this' means a style-only change with no logic impact — safe to accept. 'Don't fight the formatter' is advice to let the tool decide style.
4 / 5
A developer says: 'Run Biome with --write to auto-fix the issues.' What does auto-fix mean?
Auto-fix means Biome (or ESLint with --fix) automatically applies safe mechanical corrections for lint violations with obvious fixes — removing unused imports, changing var to const, adding missing semicolons. Not all violations are auto-fixable (complex logic changes require manual intervention). In CI discussions: 'does it have auto-fix?' is about whether developers need to manually correct lint violations or can run a command.
5 / 5
A developer adds a Biome step to the pre-commit hook. What is a pre-commit hook?
A pre-commit hook is a script in .git/hooks/pre-commit (or managed by tools like Husky) that runs automatically when you run git commit. If it exits with an error, the commit is blocked. Common uses: run linting, formatting, type-checking, or tests on staged files. In discussions: 'add Biome to the pre-commit hook' means catch style/lint issues before they're committed, keeping the commit history clean.