Zed extension

Installation

Requires Zed >= v0.131.0.

This extension is available in the extensions view inside the Zed editor. Open zed: extensions and search for Biome. It runs the Biome binary under the hood and checks for Biome installations in the following order:

Path specified in Zed’s configuration, for example like this:

1
{
2
  "lsp": {
3
    "biome": {
4
     "binary": {
5
        "path": "/var/biome-2.2.3/bin/biome",
6
        "arguments": [
7
          "lsp-proxy"
8
       ]
9
      }
10
    }
11
  }
12
}

Locally installed Biome via package.json
System-wide installed Biome in PATH

If neither exists, it will ask Zed to install Biome using npm and use that.

Configuration

`config_path`

By default, the configuration file is required to be in the root of the workspace.

Otherwise, it can be configured through the lsp settings:

1
{
2
  "lsp": {
3
    "biome": {
4
      "settings": {
5
        "config_path": "<path>/biome.json"
6
      }
7
    }
8
  }
9
}

`require_config_file`

It enables Biome only if the project contains a configuration file:

Default: false

1
{
2
  "lsp": {
3
    "biome": {
4
      "settings": {
5
        "require_config_file": true
6
      }
7
    }
8
  }
9
}

`inline_config`

An inline version of the Biome configuration. The options of this configuration will override the options coming from any biome.json file read from disk (or the defaults).

For example, let’s say your project enables the rule noConsole with error severity:

1
{
2
  "linter": {
3
    "rules": {
4
      "suspicious": {
5
        "noConsole": "error"
6
      }
7
    }
8
  }
9
}

However, during local development, you want to disable this rule because it’s useful and you don’t want to see red squiggles. In your inline_config, you would write something like the following:

1
{
2
  "lsp": {
3
    "biome": {
4
      "settings": {
5
        "inline_config": {
6
          "linter": {
7
            "rules": {
8
              "suspicious": {
9
                "noConsole": "off"
10
              }
11
            }
12
          }
13
        }
14
      }
15
    }
16
  }
17
}

Formatting

To use the language server as a formatter, specify biome as your formatter in the settings:

1
{
2
  "languages": {
3
    "Astro": { "formatter": { "language_server": { "name": "biome" } } },
4
    "CSS": { "formatter": { "language_server": { "name": "biome" } } },
5
    "GraphQL": { "formatter": { "language_server": { "name": "biome" } } },
6
    "HTML": { "formatter": { "language_server": { "name": "biome" } } },
7
    "JSON": { "formatter": { "language_server": { "name": "biome" } } },
8
    "JSONC": { "formatter": { "language_server": { "name": "biome" } } },
9
    "JSX": { "formatter": { "language_server": { "name": "biome" } } },
10
    "JavaScript": { "formatter": { "language_server": { "name": "biome" } } },
11
    "Svelte": { "formatter": { "language_server": { "name": "biome" } } },
12
    "TSX": { "formatter": { "language_server": { "name": "biome" } } },
13
    "TypeScript": { "formatter": { "language_server": { "name": "biome" } } },
14
    "Vue.js": { "formatter": { "language_server": { "name": "biome" } } },
15
  }
16
}

See Language Support for more information.

Enable biome only when biome.json is present

1
{
2
  "lsp": {
3
    "biome": {
4
      "settings": {
5
        "require_config_file": true
6
      }
7
    }
8
  }
9
}

Run code actions on format:

1
{
2
  "languages": {
3
    "JavaScript": {
4
      "formatter": { "language_server": { "name": "biome" } },
5
      "code_actions_on_format": {
6
        "source.fixAll.biome": true,
7
        "source.organizeImports.biome": true
8
      }
9
    },
10
    "TypeScript": {
11
      "formatter": { "language_server": { "name": "biome" } },
12
      "code_actions_on_format": {
13
        "source.fixAll.biome": true,
14
        "source.organizeImports.biome": true
15
      }
16
    },
17
    "TSX": {
18
      "formatter": { "language_server": { "name": "biome" } },
19
      "code_actions_on_format": {
20
        "source.fixAll.biome": true,
21
        "source.organizeImports.biome": true
22
      }
23
    }
24
  }
25
}

If you want to apply unsafe fixes on save, you must make the code fix of the rule safe.

Project-based configuration

You can include these settings in Zed Project Settings (.zed/settings.json) at the root of your project folder or as Zed User Settings (~/.config/zed/settings.json) which will apply to all projects by default.

Disable biome for a particular project

You can exclude biome for a given language (e.g. GraphQL) on project with:

1
{
2
  "languages": {
3
    "GraphQL": {
4
      "language_servers": [ "!biome", "..." ]
5
    }
6
  }
7
}

Global Settings

It is not recommended to add biome to top-level language_servers, formatter or code_actions_on_format keys in your Zed setting.json. Specifying biome as language_server or formatter globally may break functionality for languages that biome does not support (Rust, Python, etc). See language support for a complete list of supported languages.

This documentation previously recommended global settings; please switch your Zed settings to explicitly configure biome on a per language basis.