Biome v2.3 finally adds experimental Vue support – all‑in‑one linting and formatting

The only pain point: no Vue support

Vue developers have long been unable to use Biome because it did not understand .vue files, forcing teams to rely on a combination of Prettier, ESLint, Stylelint and additional plugins just to lint and format Vue components.

The day finally arrives

Biome v2.3 introduces experimental support for Vue, Svelte and Astro. With the new flag enabled, Biome can format the <template>, lint the <script>, and adjust the <style> sections of a Vue file.

To activate the feature, add the following to the Biome configuration file:

{
  "html": {
    "experimentalFullSupportEnabled": true
  }
}

Although marked experimental, most Vue components pass Biome's checks without issues, confirming that the tool is now usable for Vue projects.

What it means for frontend teams

Previously, teams had to maintain a complex stack:

Formatting with Prettier

Syntax checking with ESLint

Style checking with Stylelint

Additional Tailwind plugins if needed

Custom .rc files and ignore lists to keep CI green

This configuration overhead was painful. Biome’s philosophy is simple: “One tool, all‑in‑one.” It ships with a comprehensive rule set, eliminating the need for dozens of plugins and reducing configuration friction.

Fast, stable, clean

Written in Rust, Biome runs dramatically faster than ESLint—often an order of magnitude quicker.

A single command formats code and performs syntax checking together.

After upgrading to v2.3, Biome also understands Tailwind CSS v4 syntax out of the box.

Because Biome uses a unified analysis engine rather than a plugin‑based architecture, it can parse TypeScript, React, CSS, and HTML in a single syntax tree, delivering both speed and stability.

From framework‑specific to framework‑agnostic

The new Vue support marks Biome’s transition from a React‑centric tool to a truly framework‑agnostic solution. While Vue support is still experimental, the broader implication is that many front‑end developers can eventually retire the tangled web of ESLint configs, Prettier plugins, and custom ignore lists in favor of a single, fast, and reliable tool.