Biome replaces ESLint and Prettier with a single fast Rust-based tool. Test your knowledge of its capabilities, migration path, and configuration model.
0 / 5 completed
1 / 5
What is Biome's core value proposition compared to having separate ESLint + Prettier configurations?
Biome unifies linting and formatting in one Rust binary, which means no more fighting between ESLint's and Prettier's opinions on the same code constructs. A single biome.json controls both, lint and format run in one pass, and performance is dramatically higher because Rust handles both without two separate Node.js processes.
2 / 5
When migrating from ESLint to Biome, what does biome migrate eslint do?
biome migrate eslint reads your existing .eslintrc or eslint.config.js and attempts to produce an equivalent biome.json, enabling or disabling rules that map to Biome equivalents. This reduces the manual effort of migration, though some ESLint plugin rules may not have Biome counterparts yet.
3 / 5
How does Biome's imports organiser work when enabled?
Biome's imports organiser sorts import statements (e.g., Node built-ins first, then third-party, then local) and removes duplicates as part of the format pass. It is opt-in via the assist settings in biome.json and integrates into the same single-pass formatting pipeline.
4 / 5
What does the biome check --write command do?
biome check --write is the all-in-one command: it formats files, applies lint auto-fixes, and organises imports — all in one pass. This single command replaces running eslint --fix and prettier --write separately, and it operates across the whole project in parallel using Rust threads.
5 / 5
What CSS support does Biome provide as of version 1.6+?
Biome added CSS support starting with experimental formatting and basic parsing in version 1.6. The goal is to extend the unified linter+formatter to CSS and eventually SCSS, bringing the same zero-config, high-performance experience to stylesheets that Biome already provides for JS/TS. Full rule coverage is still in progress.