Aller au contenu

Set up your editor

Ce contenu n’est pas encore disponible dans votre langue.

Biome comes with a language server, so editor extensions give you the same diagnostics, formatting, and assist actions as the CLI while you type or save your code.

The Biome team maintains the extensions for VS Code, Zed, and IntelliJ. Helix connects to Biome’s language server directly, and extensions for other editors are maintained by the community.

VS Code is a popular code editor for web developers, built by Microsoft. Its engine also powers other editors such as VSCodium and Cursor.

Install the Biome extension from the Visual Studio Marketplace, or from the Open VSX registry for VSCodium, Cursor, and other derivatives.

To make Biome the default formatter, open a supported file and:

  1. Open the Command Palette (View or Ctrl/⌘+⇧+P).
  2. Select Format Document With…
  3. Select Configure Default Formatter.
  4. Select Biome.

See the VS Code extension reference to enable features such as format and fix on save, and for troubleshooting guidance.

Zed is a code editor built for speed and collaboration.

To install the Biome extension:

  1. Open the Command Palette (View or Ctrl/⌘+⇧+P).
  2. Select zed: extensions.
  3. Search for Biome.
  4. Select Install.

See the Zed extension reference for more information about how to enable features such as format and fix on save.

IntelliJ IDEA is an IDE built by JetBrains. It shares its platform with other JetBrains IDEs such as WebStorm, and the Biome plugin works in all of them.

Install the Biome plugin from the JetBrains Marketplace, or install it from your IDE:

  1. Go to Settings.
  2. Select Plugins from the menu on the left.
  3. Select the Marketplace tab.
  4. Search for Biome and select Install.
  5. Restart the IDE to activate the plugin.

To install the plugin from disk instead:

  1. Download the plugin .zip from the Versions tab of the plugin page.
  2. Open the IDE settings, then select Plugins.
  3. Select the settings button, then Install Plugin from Disk…

Helix does not need an extension. It connects to Biome through the biome lsp-proxy command, which acts as a language server over standard input and output.

To use Biome in every project, set it as a language server in your languages.toml file:

languages.toml
[language-server.biome]
command = "biome"
args = ["lsp-proxy"]
# Inline configuration is also supported
# https://biomejs.dev/blog/biome-v2-4/#editor-inline-configuration
[language-server.biome.config.biome.inlineConfig]
linter.rules.suspicious.noConsole = "off"
[[language]]
name = "javascript"
language-servers = [ { name = "typescript-language-server", except-features = [ "format" ] }, "biome" ]
auto-format = true

To make Helix apply project-specific settings, add Biome’s configuration files to the roots field. Helix then detects the project root from the presence of those files:

languages.toml
[language-server.biome]
command = "biome"
args = ["lsp-proxy"]
[[language]]
name = "typescript"
roots = ["biome.json", "biome.jsonc", "package.json"]
language-servers = [ { name = "typescript-language-server", except-features = [ "format" ] }, "biome" ]
auto-format = true

To use Biome with another language, such as JSON or CSS, add a [[language]] block for it. See the languages supported by Biome and the language identifiers defined by the Language Server Protocol.

These extensions are maintained by the community: