Running Biome?

Biome migration half finished or rules fighting you? We ship it properly.

Biome promises one tool, one config and a build step measured in milliseconds, which it mostly delivers once the ESLint and Prettier rules it does not yet cover are decided one way or the other. We finish the migration, write a config the team will actually read, and wire it into pre-commit and CI without the churn a half-done move usually brings.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

biome.log

still broken

What it is

Biome at a glance

Biome is a Rust-based toolchain that combines a formatter, a linter and an import organizer for JavaScript, TypeScript, JSX, JSON and CSS. It started life as Rome (announced in 2020 by Sebastian McKenzie, the original Babel author), was forked under the Biome name in August 2023 after Rome ran out of funding, and reached its stable 1.0 release later that year. Biome 2.0 shipped in 2025 with a redesigned config and broader language coverage.

The project is open source under the MIT and Apache-2.0 licenses, maintained by a working group that formed after the Rome fork. It targets ESLint and Prettier as the pair it wants to replace, with a single CLI, a single config file, and performance one to two orders of magnitude faster than the JavaScript tools it supersedes.

Type
Rust-based linter, formatter and import organizer
First released
2023 (1.0), 2025 (2.0), continuing Rome from 2020
License
MIT or Apache-2.0, open source
Maintained by
Biome core team and contributors
Typically used for
Replacing ESLint and Prettier, fast CI formatter checks, pre-commit linting, monorepo-wide code style

The honest version

Biome pros and cons

No technology is all upside. This is where Biome earns its place and where it tends to cause trouble.

Where Biome is strong

  • Genuinely fastLinting and formatting a large repo that took Prettier and ESLint 30 seconds now lands in under a second. Pre-commit hooks stop feeling like a tax.
  • One tool, one configA biome.json replaces .prettierrc, .eslintrc, their ignore files and their plugin lists. The config is small enough that reviewers actually read it.
  • Good defaultsThe formatter is close enough to Prettier that most migrations do not need a style debate, and the linter ships a sensible recommended set out of the box.
  • Native TypeScript understandingRules that need type info are limited, but syntactic coverage is thorough, and the tool runs without a project-wide parse.
  • LSP and editor integrationA first-party VS Code extension and a language server speak to any editor that supports LSP, so warnings appear in the editor without a Node process on the side.
  • CI-friendly outputThe CLI returns machine-readable diagnostics, GitHub Actions annotations and a diff-friendly format that fits into pull request bots without a wrapper.

Where Biome bites

  • Rule coverage trails ESLintThe typescript-eslint rule set is still larger. Teams that leaned heavily on type-aware rules or framework-specific plugins keep ESLint around for the gap and run both for a while.
  • Plugin ecosystem is smallThere is no ESLint-style universe of community plugins yet. If your current config relies on a niche framework rule set, that rule set probably does not exist in Biome.
  • Config churn between 1.x and 2.xField names moved, organizeImports became part of assist, and some rules were renamed. Migrating an old biome.json by hand is annoying if you skipped a few releases.
  • CSS and JSON support is still growingCSS formatting and linting work for mainstream patterns, but SCSS, Less and advanced PostCSS features are either partial or absent.
  • Nursery rules move under your feetA rule marked nursery can change its options, be renamed, or be removed before it stabilizes. Pinning the version matters if the team adopted nursery rules.
  • Harder to selectively override per fileFine-grained overrides exist, but the mental model is coarser than ESLint's layered config. Rare but awkward when a specific legacy folder needs its own rules.

Sound familiar?

Common Biome problems we fix

The Biome problems that bring people to us, and what you have once each one is fixed.

biome.json could not be parsed

The config fails to load

A trailing comma in a biome.json (as opposed to biome.jsonc), a schema key renamed between majors, or two config files existing at the same root confusing the resolver.

Config parses in both CLI and editor

'organizeImports' has been renamed

A Biome 1 config does not work on 2

Field names moved under assist and actions, several rule names changed, and the formatter options were restructured. The CLI warns, the editor plugin silently ignores.

Config aligned with the installed version

useExhaustiveDependencies expects 'hooks'

A React-specific rule needs more config

Hooks rules that need to know your custom useFoo helpers, left at defaults, which means they either miss dependency issues or flag false positives.

Hook rules configured for your codebase

The rule 'useSortedClasses' is nursery

A nursery rule changes unexpectedly

A rule you adopted from the nursery tier changed its behavior or options between minors, and CI started flagging code the editor still passes.

Nursery rules pinned or dropped deliberately

Could not auto-detect a project root

Monorepo detection fails

A pnpm workspace or Nx layout where Biome cannot find a sensible root, leading to inconsistent rule application between packages.

Project root explicit, rules consistent

VS Code extension: binary not found

The editor integration is broken

A local install missing, a workspace without node_modules, or a global Biome being preferred over the project version, which makes the editor and CLI disagree.

Editor and CLI run the same Biome

file.ts is not formatted correctly

CI fails after a migration

A pre-existing ESLint fix pattern that Biome formats differently, or a Prettier plugin for a language Biome handles natively, left turned on at the same time.

One formatter in charge, no competing passes

Both biome.json and biome.jsonc exist

Duplicate configs exist in the repo

An old biome.json left behind after a migration to JSONC comments, or two configs added by different contributors at the same level.

Single config, canonical and tracked

What we do

Biome help, from one rule to a full migration

Reach us for one failing Biome rule, or let us run the entire ESLint and Prettier migration for you.

Rescue
A CI run that is red on formatting, an editor plugin that does not light up, or a config that refuses to parse after an upgrade. We clear the block first.
ESLint and Prettier migration
A complete port of your existing rules and formatter config, with a decision log for every rule Biome does not cover and whether to keep ESLint alongside.
Monorepo rollout
A shared biome.json at the root, per-package overrides where they are justified, and pre-commit hooks that stay fast even on a thousand-package workspace.
Rule tuning
Picking which nursery and recommended rules the team will enforce, with documented reasoning so the next person to read the config knows why.
Version upgrades
Biome 1 to 2 and beyond, running the built-in migration, hand-fixing what the migration misses, and keeping the editor, CLI and CI on the same binary.
Managed Tech
Rule set reviews, dependency bumps, CI output monitoring, and an engineer to call when a Biome release surfaces new findings on previously clean code.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Biome alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Biome questions

Something else? Call+1 737 727 7327

Should we replace ESLint and Prettier with Biome?

For most projects, the formatter swap is easy and the lint rule swap is a judgment call. We review which of your current ESLint rules Biome covers, which are type-aware and still need ESLint, and either go all-in or run both tools side by side for a transition period. The honest answer depends on which rules your team actually relies on.

Does Biome support type-aware linting?

Only in a limited way. Rules that require a full TypeScript program (like typescript-eslint's strict rules) are not yet in Biome because the project has not shipped a full type checker. If type-aware rules matter to you, plan to keep tsc and some ESLint rules in the pipeline while Biome handles the fast path.

How do we migrate from a Biome 1 config to Biome 2?

The CLI has a migration command that handles most of the renames, but the organizeImports move under assist, the changed formatter fields and any adopted nursery rules need manual review. We run the migration, diff the before and after, and smoke test the rule set against real files before committing it.

Can we use Biome in a monorepo?

Yes. One biome.json at the workspace root is the usual pattern, with per-package overrides where a workspace genuinely needs different rules. For pnpm and Nx layouts we pin the Biome version at the root and make sure every workspace runs the same binary in pre-commit and CI.

Why does the Biome VS Code extension not light up?

Usually because the binary is not resolvable from the workspace. Either the project forgot to install @biomejs/biome, the extension is pointing at a global install while the project uses a different version, or a monorepo root is confusing the resolver. We check the three and align them.

How much does Biome help cost?

You pay nothing to get an estimate. Tell us the repo size, the current ESLint and Prettier setup, and the migration goal, and a quote with scope comes back by return.

Free estimate

Biome giving you trouble?

Share biome.json, the current ESLint config and a sample CI log. A real engineer answers with a quote and a clear scope.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.