Biome: One Tool to Format and Lint Your JavaScript Ecosystem

You know the drill. You set up ESLint, then Prettier, then figure out how to make them play nice together. Then you wait. And wait. And wait some more. Then you discover that one plugin you need hasn't been updated in two years. If any of this sounds familiar, there's a new player in town worth your attention: Biome.

Biome is a fast formatter and linter for JavaScript, TypeScript, JSX, JSON, and CSS. It's written in Rust, which means it's fast fast. But speed alone isn't the story here. What makes Biome interesting is that it's a single tool that handles both formatting and linting, with zero configuration needed to get started.

What It Does

Biome combines a code formatter (think Prettier) and a linter (think ESLint) into one binary. It supports:

• JavaScript and TypeScript
• JSX and TSX
• JSON
• CSS

You give it a file or a folder, and it formats your code while also catching common issues. No plugins. No manual setup. No "oops, I forgot to install that parser." It just works.

Why It's Cool

Speed first. Because Biome is built with Rust, it's noticeably faster than most JavaScript-native tools. For large projects, the difference is dramatic. Running it in CI or as a pre-commit hook won't make your eyes glaze over.

Zero configuration. Out of the box, Biome picks sensible defaults. You can customize things, but you don't have to. Compare that to the ESLint + Prettier + plugins + config dance, and you'll see why this is refreshing.

Unified experience. No more "is this a formatting error or a linting error?" Biome handles both in one pass. The error messages are clear, and the output is consistent.

No Node.js required in production. Since it's a compiled binary, you can run Biome in CI without needing to install Node.js at all. That's a nice win for deployment pipelines.

How to Try It

Getting started is simple. You can install it globally via npm:

npm install -g @biomejs/biome

Or use it directly with npx:

npx @biomejs/biome format --write src/

To lint your code:

npx @biomejs/biome lint src/

Or do both in one command:

npx @biomejs/biome check src/

There's also a VSCode extension for real-time feedback. Check out the GitHub repository for full documentation and configuration options.

Final Thoughts

Biome isn't trying to replace everything overnight. But if you're starting a new project or tired of managing the Prettier + ESLint combo, it's worth a weekend test. The speed alone might sell you, but the simplicity is the real win. It does one thing (well, two things) and does them fast and without drama.

Sometimes the best tool is the one you don't have to think about. Biome is shaping up to be that tool.

Found this useful? Follow @githubprojects for more developer tools and project highlights.