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
Running Biome?
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.
What it is
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.
The honest version
No technology is all upside. This is where Biome earns its place and where it tends to cause trouble.
Sound familiar?
The Biome problems that bring people to us, and what you have once each one is fixed.
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
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
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
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
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
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
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
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
Reach us for one failing Biome rule, or let us run the entire ESLint and Prettier migration for you.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
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.
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.
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.
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.
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.
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
Share biome.json, the current ESLint config and a sample CI log. A real engineer answers with a quote and a clear scope.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: