Zum Inhalt springen
Michael Blaess
IT-Consulting
Michael Blaess
DE

Why Biome instead of ESLint and Prettier?

6 min read BiomeESLintPrettierTypeScriptJavaScript

Anyone who writes JavaScript or TypeScript usually has two tools in the project.
A linter reads the source code and reports suspicious spots, such as a variable nobody uses. A formatter brings indentation, line length and quotes into a consistent form. The classic linter is ESLint, the classic formatter is Prettier, and both run in Node.js.

Rust is the hype among programming languages right now, and in the JavaScript world one tool after another is being rewritten in it:
SWC as a compiler, Rolldown as the bundler for Vite, Oxc with a linter of its own.
Biome is written in Rust as well. It is a linter and a formatter in one program and therefore competes with ESLint and Prettier at the same time.

Preview card of the biomejs/biome repository on GitHub with contributors, stars and forks Preview card of the eslint/eslint repository on GitHub with contributors, stars and forks Preview card of the prettier/prettier repository on GitHub with contributors, stars and forks
The preview cards of the three repositories on GitHub, as of October 12, 2026.

On Friday, October 9, 2026, turbo-mod, my mod for Claude Code, got Biome as its linter. Two days later retro-text-effects.js followed, which had been checked with ESLint 9 until then. Both tools were measured against each other on that repo.

Four reasons to switch

  • One tool, one configuration. Linting, formatting and import sorting depend on one file (biome.json) and one command (biome check). With ESLint and Prettier it is two tools with two configurations.
  • Two packages instead of 88. Every package less is one less to keep up to date and to check when a security advisory comes in.
  • Runtime. On 1,100 files ESLint and Prettier together take 6.6 seconds, Biome takes 0.4 seconds.
  • Useful defaults. Biome’s recommended rules reported 22 findings in retro-text-effects.js, the previous ESLint configuration reported none.

Biome does not replace the TypeScript compiler or esbuild. Types are still checked by tsc --noEmit.

The setup

In turbo-mod the setup consists of the package @biomejs/biome pinned to version 2.5.15 and a biome.json with 15 lines:

{
  "$schema": "https://biomejs.dev/schemas/2.5.15/schema.json",
  "vcs": { "enabled": true, "clientKind": "git", "useIgnoreFile": true },
  "files": { "includes": ["hooks/**", "types/**", "!hooks/palettes.ts"] },
  "formatter": { "indentStyle": "space", "indentWidth": 2, "lineWidth": 120 },
  "javascript": {
    "formatter": {
      "quoteStyle": "single",
      "semicolons": "asNeeded",
      "arrowParentheses": "asNeeded",
      "trailingCommas": "all"
    }
  },
  "linter": { "enabled": true }
}

biome check . checks linting, formatting and imports in one run. With --write Biome writes the fixes into the files. In turbo-mod it reformatted four files, the linter found nothing in the existing code.

Three important findings

Exclude generated files.
turbo-mod contains a file with color palettes that is generated by a script. Biome formatted it on the first run, afterwards it was 650 lines longer. The solution is in the configuration above: an entry with a leading exclamation mark in files.includes.

Do not switch on the recommended rules explicitly.
Biome 2.5.15 reports the line "rules": { "recommended": true } as deprecated. The recommended rules apply anyway, "linter": { "enabled": true } is enough.

A successful run proves nothing yet!
If a linter reports nothing, the code may be clean. It may also be that the linter does not see the files at all because a pattern in the configuration does not match. That is why every setup needs a counter-check: create a file with deliberate errors, run the tools, delete the file again.

The measurement

The measurement ran on a copy of retro-text-effects.js with 57 files and 5,077 lines of JavaScript, as of October 11, 2026. ESLint ran with the repo’s configuration, Biome with its recommended rules. The machine: Windows 11, Intel Core i7-14700, 96 GB of RAM. The versions: Node.js 24.15.0, ESLint 9.39.5, Prettier 3.9.10, Biome 2.5.15.

The results

ESLint reports nothing in the 57 files, Biome reports 22 findings.
18 of them are warnings about parameters that a function accepts and does not use.
In its default setting ESLint only reports parameters that are not followed by a used one, Biome reports every one. On top of that there are two errors on a forEach whose arrow function returns a value on the side, and two notes. There was no real bug among them.

The runtime

The table shows the runtime in milliseconds, in each case the middle value (median) of all runs. For the second column the src folder was copied twenty times side by side.
That is not an organically grown project, but it should still do for the question of how the tools behave with more files.

57 files (20 runs) 1,100 files (10 runs)
eslint . 615 3,417
prettier --check . 577 3,388
ESLint and Prettier one after the other 1,229 6,563
biome check . via npm 246 429
biome check . directly 75 278

“Via npm” means: Biome is started as a script from the package.json.
Node.js starts first and then the actual binary. “Directly” means: the binary is called without the detour through Node.js.

With 57 files the lead says little. Starting Node.js alone costs 157 milliseconds on this machine, so more than half of Biome’s time via npm is just that. With 1,100 files the difference becomes clear:
linting and formatting take roughly fifteen times as long with ESLint and Prettier as with biome check.

But careful:
These are warm runs, the machine already had all files in memory. A cold start after rebooting the machine was not measured.

The installation

ESLint and Prettier Biome
Installed packages 88 2
Files in node_modules 1,268 25
Size of node_modules 21.4 MB 79.8 MB

The size is the surprise of this measurement 🙂 Biome brings fewer packages but takes up almost four times as much space. The binary for Windows alone is 79 MB.

What speaks against Biome

Astro files are only partly understood.
This website is built with Astro. A copy of its source with 36 Astro files produced 149 warnings about unused imports and variables with the defaults, and almost all of them are false alarms.
In this setting Biome does not see that an import is used further down in the markup. The offered fix would remove the import of the page layout 😕

The documentation says so openly:
Vue, Svelte and Astro have been supported since version 2.3.0, but this should be considered experimental. With the option html.experimentalFullSupportEnabled three of the 149 warnings remained.
Tailwind 4 needs an option too: without css.parser.tailwindDirectives Biome reported 15 parse errors in the stylesheet.

ESLint plugins cannot be reused.
Biome has its own plugins, written in a query language called GritQL.
According to the migration guide, rules from ESLint plugins have to be carried over by hand in the biome.json, as far as Biome has a counterpart. This was not tried here, retro-text-effects.js does not use any ESLint plugins.

The automatic migration does not run by itself.
biome migrate eslint --write generated a biome.json with 219 lines from the ESLint configuration of retro-text-effects.js, with every rule listed individually. Four ESLint rules do not exist in Biome yet. With a small configuration it is probably easier to start fresh with Biome’s defaults.

Should you switch now?

For my own repos with plain JavaScript or TypeScript:
yes. turbo-mod and retro-text-effects.js have already been switched, and Biome is my standard for new projects.

For projects with Astro, Vue or Svelte I would try the experimental support on a copy first. And anyone who uses many ESLint plugins should go through the list of rules beforehand.

What I learned from it

The switch itself was done quickly: one new file, one npm install, and four files looked slightly different afterwards. What helped more were the counter-check with a deliberately wrong file and measuring on my own code. That Biome is faster was to be expected. That it hardly matters in a small repo, and that the installation is larger than ESLint and Prettier together, only showed up in the measurement.

Sources (checked on October 11, 2026, the three Rust projects on October 12, 2026): Biome · Biome, language support · Biome, plugins · Biome, migrating from ESLint and Prettier · ESLint, rule no-unused-vars · SWC · Rolldown · Oxc

Planning a similar project?

I support you from consulting and planning through implementation to quality assurance.

“It is not that we have too little time, but that we waste much of it.”

- Seneca