Language support

Это содержимое пока не доступно на вашем языке.

Legend:

✅: Supported
🚫: Not in progress
⌛️: In progress
🟡: Experimental

Language	Parsing	Formatting	Linting	Plugin Support
JavaScript	✅	✅	✅	✅
TypeScript	✅	✅	✅	✅
JSX	✅	✅	✅	✅
TSX	✅	✅	✅	✅
JSON	✅	✅	✅	🚫
JSONC	✅	✅	✅	🚫
HTML	✅	✅	✅	✅
Vue	🟡	🟡	🟡	🟡
Svelte	🟡	🟡	🟡	🟡
Astro	🟡	🟡	🟡	🟡
CSS	✅️	✅️	✅️	✅
YAML	⌛️	🚫	🚫	🚫
GraphQL	✅️	✅️	✅️	🚫
Markdown	⌛️	🚫	🚫	🚫
GritQL	✅️	✅️	🚫	🚫

JavaScript support

Biome supports the ES2024 version of the language.

Biome supports only the official syntax. The team starts development of the new syntax when a proposal reaches Stage 3.

TypeScript support

Biome supports TypeScript version 5.6.

JSONC support

JSONC stands for “JSON with Comments.” This format is widely used by various tools like VS Code, TypeScript, Babel, etc. because it lets users add comments to configuration files. However, since JSONC isn’t a strictly defined standard, there’s some variation in how different tools handle trailing commas in JSONC files. To accommodate this, Biome doesn’t provide a dedicated language configuration for JSONC. Instead, we’ve enhanced our JSON parsing and formatting capabilities with options like json.parser.allowComments, json.parser.allowTrailingCommas, and json.formatter.trailingCommas. This approach allows Biome to effectively support different variants of JSON files.

For files with an extension name of .jsonc or those identified as jsonc according to the language identifier, Biome automatically applies the following default settings for parsing and formatting them:

json.parser.allowComments: true
json.parser.allowTrailingCommas: true
json.formatter.trailingCommas: none

Please note, some well-known files like tsconfig.json and .babelrc don’t use the .jsonc extension but still allow comments and trailing commas. While others, such as .eslintrc.json, only allow comments. Biome is able to identify these files and adjusts the json.parser.allowTrailingCommas option accordingly to ensure they are correctly parsed.

This section gives the full list of well-known files that Biome can recognize.

HTML super languages support

Since version v2.3.0, Biome supports Vue, Svelte and Astro file out of the box. This means that Biome is able to format and lint the HTML, CSS and JavaScript parts of the files.

However, this support must be considered experimental and subject to changes and improvements. In v2.3.0, we landed the architecture that enables this feature, however some formatting and linting rules must be adjusted.

In particular, as for v2.3.0, Biome doesn’t do any particular parsing for language specific syntax, for example the control-flow syntax of Svelte e.g. {#if } {/if}. This means that formatting might not match the desired expectations, and lint rules might not detect some cases.

Lint rules that work across embedded languages aren’t supported yet.

Linting HTML-ish languages

Some lint rules don’t work across boundaries just yet. For example, the following .vue file, the rule noUnusedVariables will flag a false positive for greeting:

1
<script setup lang="ts">
2
    const greeting = "hello world"
3
</script>
4

5
<template>
6
    <h1>{{ greeting }}</h1>
7
</template>

When linting .svelte, .astro or .vue files, it’s advised to turn off a few additional rules to prevent false positive linting errors caused by our partial support. Use the option overrides for that:

1
{
2
  "overrides": [
3
    {
4
      "includes": ["**/*.svelte", "**/*.astro", "**/*.vue"],
5
      "linter": {
6
        "rules": {
7
          "style": {
8
            "useConst": "off",
9
            "useImportType": "off"
10
          },
11
          "correctness": {
12
            "noUnusedVariables": "off",
13
            "noUnusedImports": "off"
14
          }
15
        }
16
      }
17
    }
18
  ]
19
}

Formatting with different settings

With Biome, you can control the formatting of different languages. Now that Biome can process multiple languages in the same file, the chances of inconsistencies can grow based on your configuration.

For example, you could risk having a file mixed with tabs and spaces when formatting a HTML-ish file that contains JavaScript and CSS code, like in the following example (we assume full support is enabled):

1
{
2
  "javascript": {
3
    "format": {
4
      "indentStyle": "tab"
5
    }
6
  },
7
  "css": {
8
    "format": {
9
      "indentStyle": "space",
10
      "indentWidth": 4
11
    }
12
  }
13
}

We created a GitHub discussion to address the issue, join the discussion and let us know what you think.