Frontend Development 9 min read

Biome 2024 Review and 2025 Roadmap Overview

The article reviews Biome's rapid progress in 2024—including multiple minor releases, new commands, expanded language support, team growth, awards, and IDE integrations—while outlining the ambitious 2025 roadmap featuring plugins, domain‑based linting, monorepo enhancements, multi‑file analysis, type inference, and broader language support.

ByteDance Web Infra
ByteDance Web Infra
ByteDance Web Infra
Biome 2024 Review and 2025 Roadmap Overview

Biome is a tool the author believes will have many future use cases, and based on its current maintenance effort and planning, Biome is expected to succeed by 2025.

Review: Biome 2024

2024 was a significant year for Biome with rapid progress:

Four minor versions (1.6 to 1.9) were released, adding many useful features: Added commands biome search and biome explain , extending biome migrate to make migration from ESLint and Prettier easier. Supported formatting and linting for CSS and GraphQL files. Partial support for Astro, Svelte, and Vue files. Configuration files can now extends each other, useful for monorepos and large projects. Custom reporters enable better CI integration and machine‑readable logs. Support for .editorconfig configuration. Added many new lint rules and improvements, notably the useSortedClasses rule for Tailwind support.

The maintainer team grew from 10 to 18 members in 2024.

Biome won the "Productivity Booster" award at OS Awards 2024.

New sponsors joined the community‑driven project.

Improved IDE support: Zed extension added. Comprehensive revamp of the VS Code extension (currently in pre‑release). IDEA plugin received a major update, available via the nightly channel.

Enterprise Support

Starting January 2025, Biome will offer enterprise support, allowing contributors to dedicate more time to development.

Biome 2.0 Plan

Biome is actively developing version 2.0. Although no release date is set, the following features are planned:

Plugins : A long‑requested plugin system will enable users to write custom lint rules, especially for GritQL.

Domains : Domain configuration will let users enable/disable rule sets for specific ecosystems (e.g., React, Next.js) and automatically activate rules based on dependencies listed in package.json .

Monorepo Support : Enhanced biome.json extends handling and internal ProjectLayout capabilities will improve monorepo support.

Suppressions : Support for suppression comments like // biome-ignore , // biome-ignore-all , and // biome-ignore-start / // biome-ignore-end .

Multi‑file analysis : True multi‑file analysis will allow lint rules to query information from other files, enabling more powerful checks.

2025 Roadmap

The following items are under consideration for 2025, though they cannot be guaranteed due to Biome’s community‑driven nature:

HTML support : Adding formatter and linter capabilities for HTML.

Embedded languages : Handling CSS/GraphQL inside JS template strings and JS/CSS inside HTML, improving support for Astro, Svelte, and Vue.

Type inference : Building on multi‑file analysis to introduce type inference, including a real implementation of the noFloatingPromises rule.

.d.ts generation : Transforming TypeScript source into declaration files for projects with isolatedModules enabled.

JSDoc support : Using JSDoc comments as a source of type information if type inference is added.

Markdown support : Ongoing work to lint and format Markdown files.

More plugins : Expanding plugin capabilities beyond GritQL lint rule creation based on community feedback.

Your Support

The project’s progress relies heavily on users and sponsors; without them Biome would not be where it is today.

Ways to support Biome in 2025 include:

Become a contributor (see the contributing guide).

Sponsor the project to accelerate CI times and improve developer productivity.

Hire Biome contributors; companies employing contributors for three months or more automatically qualify for sponsorship benefits.

Improve documentation by writing guides or translating content for non‑English developers.

frontendtoolingRoadmaplintingcode formattingBiome
ByteDance Web Infra
Written by

ByteDance Web Infra

ByteDance Web Infra team, focused on delivering excellent technical solutions, building an open tech ecosystem, and advancing front-end technology within the company and the industry | The best way to predict the future is to create it

0 followers
Reader feedback

How this landed with the community

login Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.