Журнал изменений

Version 2.3.0

Minor Changes

#7263 a3e3369 Thanks @arendjr! - Biome’s resolver now supports baseUrl if specified in tsconfig.json.

Example

Given the following file structure:

tsconfig.json
```
1
{
2
  "compilerOptions": {
3
    "baseUrl": "./src"
4
  }
5
}
```
src/foo.ts
```
1
export function foo() {}
```
In this scenario, import { foo } from "foo"; should work regardless of the location of the file containing the import statement.

Fixes #6432.
#7745 6fcbc07 Thanks @dyc3! - Added ignore option to noUnknownAtRules. If an unknown at-rule matches any of the items provided in ignore, a diagnostic won’t be emitted.
#7753 63cb7ff Thanks @ematipico! - Enhanced the init command. The init command now checks if the existing project contains known ignore files and known generated folders.

If Biome finds .gitignore or .ignore files, it will add the following configuration to biome.json:
```
1
{
2
  "vcs": {
3
    "enabled": true,
4
    "clientKind": "git",
5
    "useIgnoreFile": true
6
  }
7
}
```
If Biome finds a dist/ folder, it will exclude it automatically using the double-exclude syntax:
```
1
{
2
  "files": {
3
    "includes": ["**", "!!**/dist"]
4
  }
5
}
```
#7548 85d3a3a Thanks @siketyan! - The rules in a domain are no longer enabled automatically by the installed dependencies unless the rule is recommended.

#7723 d3aac63 Thanks @ematipico! - Added --css-parse-css-modules CLI flag to control whether CSS Modules syntax is enabled.

You can now enable or disable CSS Modules parsing directly from the command line:

1
biome check --css-parse-css-modules=true file.module.css
2
biome format --css-parse-css-modules=true file.module.css
3
biome lint --css-parse-css-modules=true file.module.css
4
biome ci --css-parse-css-modules=true file.module.css

#7723 d3aac63 Thanks @ematipico! - Added --css-parse-tailwind-directives CLI flag to control whether Tailwind CSS 4.0 directives and functions are enabled.

You can now enable or disable Tailwind CSS 4.0 directive parsing directly from the command line:
Terminal window
```
1
biome check --css-parse-tailwind-directives=true file.css
2
biome format --css-parse-tailwind-directives=true file.css
3
biome lint --css-parse-tailwind-directives=true file.css
4
biome ci --css-parse-tailwind-directives=true file.css
```
#7330 272632f Thanks @ematipico! - Updated the formatting of .svelte and .vue files. Now the indentation of the JavaScript blocks matches Prettier’s:
```
1
<script>
2
 import Component from "./Component"
3
   import Component from "./Component"
4
</script>
```
#7333 de0d2d6 Thanks @dyc3! - Implemented the indentScriptAndStyle option for vue and svelte files, with the default set to false to match Prettier’s vueIndentScriptAndStyle option. When enabled, this option indents the content within <script> and <style> tags to align with the surrounding HTML structure.

It can be enabled with this configuration:
```
1
{
2
  "html": {
3
    "formatter": {
4
      "indentScriptAndStyle": true
5
    }
6
  }
7
}
```
Which will format this code to:
```
1
<script>
2
import Component from "./Component.vue";
3
</script>
```
#7359 ebbddc4 Thanks @arendjr! - Deprecated the option files.experimentalScannerIgnores in favour of force-ignore syntax in files.includes.

files.includes supports ignoring files by prefixing globs with an exclamation mark (!). With this change, it also supports force-ignoring globs by prefixing them with a double exclamation mark (!!).

The effect of force-ignoring is that the scanner will not index files matching the glob, even in project mode, even if those files are imported by other files, and even if they are files that receive special treatment by Biome, such as nested biome.json files.

Example

Let’s take the following configuration:
```
1
{
2
  "files": {
3
    "includes": [
4
      "**",
5
      "!**/generated",
6
      "!!**/dist",
7
      "fixtures/example/dist/*.js"
8
    ]
9
  },
10
  "linter": {
11
    "domains": {
12
      "project": "all"
13
    }
14
  }
15
}
```
This configuration achieves the following:
- Because the project domain is enabled, all supported files in the project are indexed and processed by the linter, except:
- Files inside a generated folder are not processed by the linter, but they will get indexed if a file outside a generated folder imports them.
- Files inside a dist folder are never indexed nor processed, not even if they are imported for any purpose, except:
- When the dist folder is inside fixtures/example/, its .js files do get both indexed and processed.
In general, we now recommend using the force-ignore syntax for any folders that contain output files, such as build/ and dist/. For such folders, it is highly unlikely that indexing has any useful benefits. For folders containing generated files, you may wish to use the regular ignore syntax so that type information can still be extracted from the files.

experimentalScannerIgnores will continue to work for now, but you’ll see a deprecation warning if you still use it.

Run the biome migrate --write command to automatically update the configuration file.

#7698 3b6f5e3 Thanks @ematipico! - Added a new reporter named rdjson. This reporter prints diagnostics following the RDJSON format:

The following command:

1
biome check --reporter=rdjson

Will emit diagnostics in the following format:

1
{
2
  "source": {
3
    "name": "Biome",
4
    "url": "https://biomejs.dev"
5
  },
6
  "diagnostics": [
7
    {
8
      "code": {
9
        "url": "https://biomejs.dev/linter/rules/no-unused-imports",
10
        "value": "lint/correctness/noUnusedImports"
11
      },
12
      "location": {
13
        "path": "index.ts",
14
        "range": {
15
          "end": {
16
            "column": 11,
17
            "line": 0
18
          },
19
          "start": {
20
            "column": 7,
21
            "line": 0
22
          }
23
        }
24
      },
25
      "message": "This import is unused."
26
    },
27
    {
28
      "code": {
29
        "url": "https://biomejs.dev/linter/rules/no-unused-imports",
30
        "value": "lint/correctness/noUnusedImports"
31
      },
32
      "location": {
33
        "path": "index.ts",
34
        "range": {
35
          "end": {
36
            "column": 10,
37
            "line": 1
38
          },
39
          "start": {
40
            "column": 9,
41
            "line": 1
42
          }
43
        }
44
      },
45
      "message": "Several of these imports are unused."
46
    }
47
  ]
48
}

#7719 188a767 Thanks @cadunass! - The formatWithErrors option can now be set via CLI using the --format-with-errors flag.

This flag was previously only available in the configuration file. It allows formatting to proceed on files with syntax errors, which is useful during development when you want to auto-format code while fixing syntax issues.

Example
Terminal window
```
1
biome format --format-with-errors=true --write file.js
```
#7723 d3aac63 Thanks @ematipico! - Added --json-parse-allow-comments CLI flag to control whether comments are allowed in JSON files.

You can now enable or disable comment parsing in JSON files directly from the command line:
Terminal window
```
1
biome check --json-parse-allow-comments=true file.json
2
biome format --json-parse-allow-comments=true file.json
3
biome lint --json-parse-allow-comments=true file.json
4
biome ci --json-parse-allow-comments=true file.json
```

#7723 d3aac63 Thanks @ematipico! - Added --json-parse-allow-trailing-commas CLI flag to control whether trailing commas are allowed in JSON files.

You can now enable or disable trailing comma parsing in JSON files directly from the command line:

1
biome check --json-parse-allow-trailing-commas=true file.json
2
biome format --json-parse-allow-trailing-commas=true file.json
3
biome lint --json-parse-allow-trailing-commas=true file.json
4
biome ci --json-parse-allow-trailing-commas=true file.json

#7758 cea002f Thanks @ematipico! - Promoted new lint rules:
- Promoted noNonNullAssertedOptionalChain to the suspicious group
- Promoted useReactFunctionComponents to the style group
- Promoted useImageSize to the correctness group
- Promoted useConsistentTypeDefinitions to the style group
- Promoted useQwikClasslist to the correctness group
- Promoted noSecrets to the security group
Removed the lint rule useAnchorHref, because its use case is covered by useValidAnchor.

#6356 296627d Thanks @wrick17! - Added the new checkstyle reporter. When --reporter=checkstyle is passed to the CLI, Biome will emit diagnostics for Checkstyle format:

1
<?xml version="1.0" encoding="utf-8"?>
2
<checkstyle version="4.3">
3
  <file name="index.ts">
4
    <error line="1" column="8" severity="warning" message="This import is unused." source="lint/correctness/noUnusedImports" />
5
    <error line="2" column="10" severity="warning" message="Several of these imports are unused." source="lint/correctness/noUnusedImports" />
6
    <error line="8" column="5" severity="warning" message="This variable f is unused." source="lint/correctness/noUnusedVariables" />
7
    <error line="9" column="7" severity="warning" message="This variable f is unused." source="lint/correctness/noUnusedVariables" />
8
    <error line="1" column="1" severity="error" message="The imports and exports are not sorted." source="assist/source/organizeImports" />
9
    <error line="4" column="3" severity="error" message="Using == may be unsafe if you are relying on type coercion." source="lint/suspicious/noDoubleEquals" />
10
    <error line="6" column="1" severity="error" message="This is an unexpected use of the debugger statement." source="lint/suspicious/noDebugger" />
11
    <error line="8" column="5" severity="error" message="This variable implicitly has the any type." source="lint/suspicious/noImplicitAnyLet" />
12
    <error line="9" column="7" severity="error" message="This variable implicitly has the any type." source="lint/suspicious/noImplicitAnyLet" />
13
    <error line="2" column="10" severity="error" message="Shouldn&apos;t redeclare &apos;z&apos;. Consider to delete it or rename it." source="lint/suspicious/noRedeclare" />
14
    <error line="9" column="7" severity="error" message="Shouldn&apos;t redeclare &apos;f&apos;. Consider to delete it or rename it." source="lint/suspicious/noRedeclare" />
15
    <error line="0" column="0" severity="error" message="Formatter would have printed the following content:" source="format" />
16
  </file>
17
  <file name="main.ts">
18
    <error line="1" column="8" severity="warning" message="This import is unused." source="lint/correctness/noUnusedImports" />
19
    <error line="2" column="10" severity="warning" message="Several of these imports are unused." source="lint/correctness/noUnusedImports" />
20
    <error line="8" column="5" severity="warning" message="This variable f is unused." source="lint/correctness/noUnusedVariables" />
21
    <error line="9" column="7" severity="warning" message="This variable f is unused." source="lint/correctness/noUnusedVariables" />
22
    <error line="1" column="1" severity="error" message="The imports and exports are not sorted." source="assist/source/organizeImports" />
23
    <error line="4" column="3" severity="error" message="Using == may be unsafe if you are relying on type coercion." source="lint/suspicious/noDoubleEquals" />
24
    <error line="6" column="1" severity="error" message="This is an unexpected use of the debugger statement." source="lint/suspicious/noDebugger" />
25
    <error line="8" column="5" severity="error" message="This variable implicitly has the any type." source="lint/suspicious/noImplicitAnyLet" />
26
    <error line="9" column="7" severity="error" message="This variable implicitly has the any type." source="lint/suspicious/noImplicitAnyLet" />
27
    <error line="2" column="10" severity="error" message="Shouldn&apos;t redeclare &apos;z&apos;. Consider to delete it or rename it." source="lint/suspicious/noRedeclare" />
28
    <error line="9" column="7" severity="error" message="Shouldn&apos;t redeclare &apos;f&apos;. Consider to delete it or rename it." source="lint/suspicious/noRedeclare" />
29
    <error line="0" column="0" severity="error" message="Formatter would have printed the following content:" source="format" />
30
  </file>
31
</checkstyle>

#7488 b13e524 Thanks @kpapa05! - Added “@rbxts/react” as an alias for “react” for handling the reactClassic jsxRuntime.
#7536 0bccd34 Thanks @TheAlexLichter! - Added .oxlintrc.json to well-known files.
#7548 85d3a3a Thanks @siketyan! - The following rules are now a part of the react domain, and they won’t be enabled automatically unless you enabled the domain, or Biome detects react as a dependency of your closest package.json:
- lint/correctness/noChildrenProp (recommended)
- lint/correctness/noReactPropAssignments
- lint/security/noDangerouslySetInnerHtml (recommended)
- lint/security/noDangerouslySetInnerHtmlWithChildren (recommended)
- lint/style/useComponentExportOnlyModules
- lint/suspicious/noArrayIndexKey (recommended)
#7667 480909a Thanks @ematipico! - Added the ability to show severity Information diagnostics in reporter outputs.

If one or more rules are triggered, and they are configured to emit an Information diagnostic, now they’re counted in the final output:
Terminal window
```
1
Checked 1 file in <TIME>. No fixes applied.
2
Found 1 info.
```
#7702 28e8860 Thanks @ematipico! - Added linting and assist support for .html files, with addition of two new configurations:
- html.linter.enabled
- html.assist.enabled
The HTML linter, in this release, only contains the rule noHeaderScope. More rules will be released in the upcoming releases.
#7164 f66b0c5 Thanks @dyc3! - Added a new CSS parser option tailwindDirectives. Enabling this option will allow all of Tailwind v4’s syntax additions to be parsed and formatted by Biome.

You can enable this by setting css.parser.tailwindDirectives to true in your Biome configuration.
```
1
{
2
  "css": {
3
    "parser": {
4
      "tailwindDirectives": true
5
    }
6
  }
7
}
```
#7669 6ed4d16 Thanks @barklund! - React 19.2 support is now supported in Biome:
- Treats useEffectEvent like useRef in useExhaustiveDependencies
- Added <Activity /> to known React APIs.
#7702 28e8860 Thanks @ematipico! - Added experimental full support for HTML, Vue, Svelte and Astro files. In this release, the HTML parser has been enhanced, and it’s now able to parse .vue, .svelte and .astro files.

This means that now Biome is able to lint and format the JavaScript (TypeScript), HTML and CSS code that is contained in these files.

Now that the main architecture is stable and working, in the upcoming patches and minors we will also fix possible inaccuracies and edge cases coming from existing lint rules, such as noUnusedVariables inside <script> blocks or frontmatter.

The support is considered experimental because there might be cases that aren’t fine-parsed yet, hence causing possible inaccuracies when it comes to formatting and linting.
#7599 09445c8 Thanks @anaisbetts! - #### lineEnding has a new option auto

The option lineEnding now has a variant called auto to match the operating system’s expected line-ending style: on Windows, this will be CRLF (\r\n), and on macOS / Linux, this will be LF (\n).

This allows for cross-platform projects that use Biome not to have to force one option or the other, which aligns better with Git’s default behavior on these platforms.

Example usage:
```
1
{
2
  "formatter": {
3
    "lineEnding": "auto"
4
  }
5
}
```
Terminal window
```
1
biome format --line-ending auto
```
#7392 e4feb8e Thanks @ematipico! - Added new capabilities to the CLI arguments --skip and --only, available to the biome lint command.

--skip and --only can now accept domain names; when provided, Biome will run or skip all the rules that belong to a certain domain.

For example, the following command will only run the rules that belong to the next domain:
Terminal window
```
1
biome lint --only=next
```
Another example, the following command will skip the rules that belong to the project domain:
Terminal window
```
1
biome lint --skip=project
```
#7702 28e8860 Thanks @ematipico! - Added a new option called html.interpolation. This option enables the parsing of text expressions (or interpolation) in HTML files.

The following file.html will be correctly formatted:
file.html
```
1
<div>
2
  Hello {{ name }}!
3
  <p>Your balance is: {{ account.balance }}</p>
4
  <button>{{ isLoading ? "Loading..." : "Submit" }}</button>
5
</div>
```
To note that html.interpolation only parses text expressions that are delimited by double curly braces ({{ }}). The content of expressions is parsed as normal text.

Patch Changes

#7712 fcc9b42 Thanks @minht11! - Added new rule useVueDefineMacrosOrder which allows enforcing specific order for Vue compiler macros.

In this example, the rule will suggest moving defineProps before defineEmits:
```
1
<script lang="ts" setup>
2
const emit = defineEmits(["update"]);
3
const props = defineProps<{ name: string }>();
4
</script>
```
#7698 3b6f5e3 Thanks @ematipico! - Fixed an issue where the JUnit reporter returned a zero-based location. Now the location returned is one-based.
#7819 ef45056 Thanks @ematipico! - Fixed #7788. Removes some error logging that were emitted when loading possible configuration files.
#7593 e51dd55 Thanks @arendjr! - Fixed an issue with the files.maxSize setting. Previously the setting would always be looked up in the root settings, even in monorepos where a closer biome.json is available. It now correctly uses the nearest configuration.
#7825 ad55b35 Thanks @Conaclos! - Fixed #7798. useNamingConvention no longer panics when it encounters a name that consists of a single dollar sign $ that doesn’t match a custom convention.
#7764 93be2ab Thanks @gaauwe! - Fixed #6589: Biome now properly loads extension settings before loading the configuration file when opening a text document in the LSP server.

Журнал изменений

Version 2.3.0

Minor Changes

Example

Example

Example

Patch Changes