Version History

2.3.7 Latest

Patch Changes

#8169 7fdcec8 Thanks @arendjr! - Fixed #7999: Correctly place await after leading comment in auto-fix action from noFloatingPromises rule.
#8157 12d5b42 Thanks @Conaclos! - Fixed #8148. noInvalidUseBeforeDeclaration no longer reports some valid use before declarations.

The following code is no longer reported as invalid:
```
1
class classA {
2
  C = C;
3
}
4
const C = 0;
```
#8178 6ba4157 Thanks @dyc3! - Fixed #8174, where the HTML parser would parse 2 directives as a single directive because it would not reject whitespace in Vue directives. This would cause the formatter to erroneously merge the 2 directives into one, resulting in broken code.
```
1
<Component v-else:property="123" />
2
<Component v-else :property="123" />
```
#8088 0eb08e8 Thanks @db295! - Fixed #7876: The noUnusedImports rule now ignores imports that are used by @linkcode and @linkplain (previously supported @link and @see).

The following code will no longer be a false positive:
```
1
import type { a } from "a"
2

3
/**
4
 * {@linkcode a}
5
 */
6
function func() {}
```
#8119 8d64655 Thanks @ematipico! - Improved the detection of the rule noUnnecessaryConditions. Now the rule isn’t triggered for variables that are mutated inside a module.

This logic deviates from the original rule, hence noUnnecessaryConditions is now marked as “inspired”.

In the following example, hey starts as false, but then it’s assigned to a string. The rule isn’t triggered inside the if check.
```
1
let hey = false;
2

3
function test() {
4
  hey = "string";
5
}
6

7
if (hey) {
8
}
```
#8149 e0a02bf Thanks @Netail! - Fixed #8144: Improve noSyncScripts, ignore script tags with type="module" as these are always non-blocking.
#8182 e9f068e Thanks @hirokiokada77! - Fixed #7877: Range suppressions now handle suppressed categories properly.

Valid:
```
1
// biome-ignore-start lint: explanation
2
const foo = 1;
3
// biome-ignore-end lint: explanation
```
#8111 bf1a836 Thanks @ryan-m-walker! - Added support for parsing and formatting the CSS if function.

Example
```
1
.basic-style {
2
  color: if(style(--scheme: dark): #eeeeee; else: #000000;);
3
}
```
#8173 7fc07c1 Thanks @ematipico! - Fixed #8138 by reverting an internal refactor that caused a regression to the rule noUnusedPrivateClassMembers.
#8119 8d64655 Thanks @ematipico! - Improved the type inference engine, by resolving types for variables that are assigned to multiple values.
#8158 fb1458b Thanks @dyc3! - Added the useVueValidVText lint rule to enforce valid v-text directives. The rule reports when v-text has an argument, has modifiers, or is missing a value.

Invalid:
```
1
<div v-text />
2

3
<div v-text:aaa="foo" />
4

5
<div v-text.bbb="foo" />
6

```
#8158 fb1458b Thanks @dyc3! - Fixed useVueValidVHtml so that it will now flag empty strings, e.g. v-html=""
#7078 bb7a15c Thanks @emilyinure! - Fixed #6675: Now only flags noAccumulatingSpread on Object.assign when a new object is being allocated on each iteration. Before, all cases using Object.assign with reduce parameters were warned despite not making new allocations.

The following code will no longer be a false positive:
```
1
foo.reduce((acc, bar) => Object.assign(acc, bar), {});
```
The following cases which do make new allocations will continue to warn:
```
1
foo.reduce((acc, bar) => Object.assign({}, acc, bar), {});
```
#8175 0c8349e Thanks @ryan-m-walker! - Fixed CSS formatting of dimension units to use correct casing for Q, Hz and kHz.

Before:
```
1
.cssUnits {
2
  a: 1Q;
3
  b: 1Hz;
4
  c: 1kHz;
5
}
```
After:
```
1
.cssUnits {
2
  a: 1Q;
3
  b: 1Hz;
4
  c: 1kHz;
5
}
```

2.3.6

Patch Changes

#8100 82b9a8e Thanks @Netail! - Added the nursery rule useFind. Enforce the use of Array.prototype.find() over Array.prototype.filter() followed by [0] when looking for a single result.

Invalid:
```
1
[1, 2, 3].filter((x) => x > 1)[0];
2

3
[1, 2, 3].filter((x) => x > 1).at(0);
```
#8118 dbc7021 Thanks @hirokiokada77! - Fixed #8117: useValidLang now accepts valid BCP 47 language tags with script subtags.

Valid:
```
1
<html lang="zh-Hans-CN"></html>
```
#7672 f1d5725 Thanks @Netail! - Added the nursery rule useConsistentGraphqlDescriptions, requiring all descriptions to follow the same style (either block or inline) inside GraphQL files.

Invalid:
```
1
enum EnumValue {
2
  "this is a description"
3
  DEFAULT
4
}
```
Valid:
```
1
enum EnumValue {
2
  """
3
  this is a description
4
  """
5
  DEFAULT
6
}
```
#8026 f102661 Thanks @matanshavit! - Fixed #8004: noParametersOnlyUsedInRecursion now correctly detects recursion by comparing function bindings instead of just names.

Previously, the rule incorrectly flagged parameters when a method had the same name as an outer function but called the outer function (not itself):
```
1
function notRecursive(arg) {
2
  return arg;
3
}
4

5
const obj = {
6
  notRecursive(arg) {
7
    return notRecursive(arg); // This calls the outer function, not the method itself
8
  },
9
};
```
Biome now properly distinguishes between these cases and will not report false positives.
#8097 5fc5416 Thanks @dyc3! - Added the nursery rule noVueVIfWithVFor. This rule disallows v-for and v-if on the same element.
```
1

2
<div v-for="item in items" v-if="item.isActive">
3
  {{ item.name }}
4
</div>
```
#8085 7983940 Thanks @Netail! - Added the nursery rule noForIn. Disallow iterating using a for-in loop.

Invalid:
```
1
for (const i in array) {
2
  console.log(i, array[i]);
3
}
```
#8086 2b41e82 Thanks @matanshavit! - Fixed #8045: The noNestedTernary rule now correctly detects nested ternary expressions even when they are wrapped in parentheses (e.g. foo ? (bar ? 1 : 2) : 3).

Previously, the rule would not flag nested ternaries like foo ? (bar ? 1 : 2) : 3 because the parentheses prevented detection. The rule now looks through parentheses to identify nested conditionals.

Previously not detected (now flagged):
```
1
const result = foo ? (bar ? 1 : 2) : 3;
```
Still valid (non-nested with parentheses):
```
1
const result = foo ? bar : baz;
```
#8075 e403868 Thanks @YTomm! - Fixed #7948: The useReadonlyClassProperties code fix when checkAllProperties is enabled will no longer insert a newline after readonly and the class property.
#8102 47d940e Thanks @lucasweng! - Fixed #8027. useReactFunctionComponents no longer reports class components that implement componentDidCatch using class expressions.

The rule now correctly recognizes error boundaries defined as class expressions:
```
1
const ErrorBoundary = class extends Component {
2
  componentDidCatch(error, info) {}
3

4
  render() {
5
    return this.props.children;
6
  }
7
};
```
#8097 5fc5416 Thanks @dyc3! - Added the nursery rule useVueHyphenatedAttributes, which encourages using kebab case for attribute names, per the Vue style guide’s recommendations.
```
1

2
<MyComponent myProp="value" />
3

4

5
<MyComponent my-prop="value" />
```

#8108 0f0a658 Thanks @Netail! - Added the nursery rule noSyncScripts. Prevent the usage of synchronous scripts.

Invalid:

1
<script src="https://third-party-script.js" />

Valid:

1
<script src="https://third-party-script.js" async />
2
<script src="https://third-party-script.js" defer />

#8098 1fdcaf0 Thanks @Jayllyz! - Added documentation URLs to rule descriptions in the JSON schema.
#8097 5fc5416 Thanks @dyc3! - Fixed an issue with the HTML parser where it would treat Vue directives with dynamic arguments as static arguments instead.
#7684 f4433b3 Thanks @vladimir-ivanov! - Changed noUnusedPrivateClassMembers to align more fully with meaningful reads.

This rule now distinguishes more carefully between writes and reads of private class members.
- A meaningful read is any access that affects program behavior.
- For example, this.#x += 1 both reads and writes #x, so it counts as usage.
- Pure writes without a read (e.g. this.#x = 1 with no getter) are no longer treated as usage.
This change ensures that private members are only considered “used” when they are actually read in a way that influences execution.

Invalid examples (previously valid)
```
1
class UsedMember {
2
  set #x(value) {
3
    doSomething(value);
4
  }
5

6
  foo() {
7
    // This assignment does not actually read #x, because there is no getter.
8
    // Previously, this was considered a usage, but now it’s correctly flagged.
9
    this.#x = 1;
10
  }
11
}
```
Valid example (Previously invalid)
```
1
class Foo {
2
  #usedOnlyInWriteStatement = 5;
3

4
  method() {
5
    // This counts as a meaningful read because we both read and write the value.
6
    this.#usedOnlyInWriteStatement += 42;
7
  }
8
}
```
#7684 f4433b3 Thanks @vladimir-ivanov! - Improved detection of used private class members

The analysis for private class members has been improved: now the tool only considers a private member “used” if it is actually referenced in the code.
- Previously, some private members might have been reported as used even if they weren’t actually accessed.
- With this change, only members that are truly read or called in the code are counted as used.
- Members that are never accessed will now be correctly reported as unused.
This makes reports about unused private members more accurate and helps you clean up truly unused code.

Example (previously valid)
```
1
type YesNo = "yes" | "no";
2

3
export class SampleYesNo {
4
  private yes: () => void;
5
  private no: () => void;
6
  private dontKnow: () => void; // <- will now report as unused
7

8
  on(action: YesNo): void {
9
    this[action]();
10
  }
11
}
```
#7681 b406db6 Thanks @kedevked! - Added the new lint rule, useSpread, ported from the ESLint rule prefer-spread.

This rule enforces the use of the spread syntax (...) over Function.prototype.apply() when calling variadic functions, as spread syntax is generally more concise and idiomatic in modern JavaScript (ES2015+).

The rule provides a safe fix.

Invalid
```
1
Math.max.apply(Math, args);
2
foo.apply(undefined, args);
3
obj.method.apply(obj, args);
```
Valid
```
1
Math.max(...args);
2
foo(...args);
3
obj.method(...args);
4

5
// Allowed: cases where the `this` binding is intentionally changed
6
foo.apply(otherObj, args);
```

#7287 aa55c8d Thanks @ToBinio! - Fixed #7205: The noDuplicateTestHooks rule now treats chained describe variants (e.g., describe.each/for/todo) as proper describe scopes, eliminating false positives.

The following code will no longer be a false positive:

1
describe("foo", () => {
2
  describe.for([])("baz", () => {
3
    beforeEach(() => {});
4
  });
5

6
  describe.todo("qux", () => {
7
    beforeEach(() => {});
8
  });
9

10
  describe.todo.each([])("baz", () => {
11
    beforeEach(() => {});
12
  });
13
});

#8013 0c0edd4 Thanks @Jayllyz! - Added the GraphQL nursery rule useUniqueGraphqlOperationName. This rule ensures that all GraphQL operations within a document have unique names.

Invalid:

1
query user {
2
  user {
3
    id
4
  }
5
}
6

7
query user {
8
  user {
9
    id
10
    email
11
  }
12
}

Valid:

1
query user {
2
  user {
3
    id
4
  }
5
}
6

7
query userWithEmail {
8
  user {
9
    id
10
    email
11
  }
12
}

#8084 c2983f9 Thanks @dyc3! - Fixed #8080: The HTML parser, when parsing Vue, can now properly handle Vue directives with no argument, modifiers, or initializer (e.g. v-else). It will no longer treat subsequent valid attributes as bogus.
```
1
<p v-else class="flex">World</p>
2

```
#8104 041196b Thanks @Conaclos! - Fixed noInvalidUseBeforeDeclaration. The rule no longer reports a use of an ambient variable before its declarations. The rule also completely ignores TypeScript declaration files. The following code is no longer reported as invalid:
```
1
CONSTANT;
2
declare const CONSTANT: number;
```
#8060 ba7b076 Thanks @dyc3! - Added the nursery rule useVueValidVBind, which enforces the validity of v-bind directives in Vue files.

Invalid v-bind usages include:
```
1
<Foo v-bind />
2

3
<Foo v-bind:foo />
4

5
<Foo v-bind:foo.bar="baz" />
6

```
#8113 fb8e3e7 Thanks @Conaclos! - Fixed noInvalidUseBeforeDeclaration. The rule now reports invalid use of classes, enums, and TypeScript’s import-equals before their declarations.

The following code is now reported as invalid:
```
1
new C();
2
class C {}
```
#8077 0170dcb Thanks @dyc3! - Added the rule useVueValidVElseIf to enforce valid v-else-if directives in Vue templates. This rule reports invalid v-else-if directives with missing conditional expressions or when not preceded by a v-if or v-else-if directive.
#8077 0170dcb Thanks @dyc3! - Added the rule useVueValidVElse to enforce valid v-else directives in Vue templates. This rule reports v-else directives that are not preceded by a v-if or v-else-if directive.
#8077 0170dcb Thanks @dyc3! - Added the rule useVueValidVHtml to enforce valid usage of the v-html directive in Vue templates. This rule reports v-html directives with missing expressions, unexpected arguments, or unexpected modifiers.
#8077 0170dcb Thanks @dyc3! - Added the rule useVueValidVIf to enforce valid v-if directives in Vue templates. It disallows arguments and modifiers, and ensures a value is provided.
#8077 0170dcb Thanks @dyc3! - Added the rule useVueValidVOn to enforce valid v-on directives in Vue templates. This rule reports invalid v-on / shorthand @ directives with missing event names, invalid modifiers, or missing handler expressions.

2.3.5

Patch Changes

#8023 96f3e77 Thanks @ematipico! - Added support Svelte syntax {@html}. Biome now is able to parse and format the Svelte syntax {@html}:
```
1
{@html   'div'}
2
{@html 'div'}
```
The contents of the expressions inside the {@html <expression>} aren’t formatted yet.
#8058 5f68bcc Thanks @ematipico! - Fixed a bug where the Biome Language Server would enable its project file watcher even when no project rules were enabled.

Now the watching of nested configuration files and nested ignore files is delegated to the editor, if their LSP spec supports it.
#8023 96f3e77 Thanks @ematipico! - Added support Svelte syntax {@render}. Biome now is able to parse and format the Svelte syntax {@render}:
```
1
{@render   sum(1, 2)   }
2
{@render sum(1, 2)}
```
The contents of the expressions inside the {@render <expression>} aren’t formatted yet.
#8006 f0612a5 Thanks @Bertie690! - Updated documentation and diagnostic for lint/complexity/noBannedTypes. The rule should have a more detailed description and diagnostic error message.
#8039 da70d8b Thanks @PFiS1737! - Biome now keeps a blank line after the frontmatter section in Astro files.
#8042 b7efa6f Thanks @dyc3! - The CSS Parser, with tailwindDirectives enabled, will now accept at rules like @media and @supports in @custom-variant shorthand syntax.
#8064 3ff9d45 Thanks @dibashthapa! - Fixed #7967: Fixed the issue with support for advanced SVG props
#8023 96f3e77 Thanks @ematipico! - Added support Svelte syntax {@attach}. Biome now is able to parse and format the Svelte syntax {@attach}:
```
1
<div {@attach    myAttachment   }>...</div>
2
<div {@attach myAttachment}>...</div>
```
The contents of the expressions inside the {@attach <expression>} aren’t formatted yet.
#8001 6e8a50e Thanks @ematipico! - Added support Svelte syntax {#key}. Biome now is able to parse and format the Svelte syntax {#key}:
```
1
{#key   expression} <div></div> {/key}
2
{#key expression}
3
  <div></div>
4
{/key}
```
The contents of the expressions inside the {#key <expression>} aren’t formatted yet.
#8023 96f3e77 Thanks @ematipico! - Added support Svelte syntax {@const}. Biome now is able to parse and format the Svelte syntax {@const}:
```
1
{@const   name = value}
2
{@const name = value}
```
The contents of the expressions inside the {@const <expression>} aren’t formatted yet.
#8044 8f77d4a Thanks @Netail! - Corrected rule source references. biome migrate eslint should do a bit better detecting rules in your eslint configurations.
#8065 1a2d1af Thanks @Netail! - Added the nursery rule useArraySortCompare. Require Array#sort and Array#toSorted calls to always provide a compareFunction.

Invalid:
```
1
const array = [];
2
array.sort();
```
Valid:
```
1
const array = [];
2
array.sort((a, b) => a - b);
```
#7673 a3a713d Thanks @dyc3! - The HTML parser is now able to parse vue directives. This enables us to write/port Vue lint rules that require inspecting the <template> section. However, this more complex parsing may result in parsing errors where there was none before. For those of you that have opted in to the experimental support (aka experimentalFullSupportEnabled), we greatly appreciate your help testing this out, and your bug reports.

#8031 fa6798a Thanks @ematipico! - Added support for the Svelte syntax {#if}{/if}. The Biome HTML parser is now able to parse and format the {#if}{/if} blocks:

1
<!-- if / else-if / else -->
2
{#if porridge.temperature > 100}
3
<p>too hot!</p>
4
  <p>too hot!</p>
5
{:else if 80 > porridge.temperature}
6
<p>too cold!</p>
7
  <p>too cold!</p>
8
{:else if 100 > porridge.temperature}
9
<p>too too cold!</p>
10
  <p>too too cold!</p>
11
{:else}
12
<p>just right!</p>
13
  <p>just right!</p>
14
{/if}

#8041 beeb7bb Thanks @dyc3! - The CSS parser, with tailwindDirectives enabled, will now accept lists of selectors in @custom-variant shorthand syntax.
```
1
@custom-variant cell (th:has(&), td:has(&));
```
#8028 c09e45c Thanks @fmajestic! - The GitLab reporter now outputs format errors.
#8037 78011b1 Thanks @PFiS1737! - indentScriptAndStyle no longer indents the frontmatter in Astro files.
#8009 6374b1f Thanks @tmcw! - Fixed an edge case in the useArrowFunction rule.

The rule no longer emits diagnostics for or offers to fix functions that reference the arguments object, because that object is undefined for arrow functions.

Valid example:
```
1
// Valid: this function cannot be transformed into an arrow function because
2
// arguments is not defined for arrow functions.
3
const getFirstArg = function () {
4
  return arguments[0];
5
};
```

2.3.4

Patch Changes

#7989 4855c4a Thanks @alissonlauffer! - Fixed a regression in Astro frontmatter parsing where comments inside quoted strings were incorrectly detected as actual comments. This caused the parser to prematurely terminate frontmatter parsing when encountering strings like const test = "//";. For example, the following Astro frontmatter now parses correctly:
```
1
---
2
const test = "// not a real comment";
3
---
```
#7968 0b28f5f Thanks @denbezrukov! - Refactored formatter to use strict Token element for better performance. The new Token variant is optimized for static, ASCII-only text (keywords, operators, punctuation) with the following constraints:
- ASCII only (no Unicode characters)
- No newlines (\n, \r)
- No tab characters (\t)
This enables faster printing and fitting logic by using bulk string operations (push_str, len()) instead of character-by-character iteration with Unicode width calculations.

#7941 19b8280 Thanks @Conaclos! - Fixed #7943. Rules’ options are now properly merged with the inherited options from a shared configuration.

This means that you can now override a specific option from a rule without resetting the other options to their default.

Given the following shared configuration:

1
{
2
  "linter": {
3
    "rules": {
4
      "style": {
5
        "useNamingConvention": {
6
          "level": "on",
7
          "options": {
8
            "strictCase": false,
9
            "conventions": [
10
              {
11
                "selector": { "kind": "variable", "scope": "global" },
12
                "formats": ["CONSTANT_CASE"]
13
              }
14
            ]
15
          }
16
        }
17
      }
18
    }
19
  }
20
}

And the user configuration that extends this shared configuration:

1
{
2
  "extends": ["shared.json"],
3
  "linter": {
4
    "rules": {
5
      "style": {
6
        "useNamingConvention": {
7
          "level": "on",
8
          "options": { "strictCase": true }
9
        }
10
      }
11
    }
12
  }
13
}

The obtained merged configuration is now as follows:

1
{
2
  "extends": ["shared.json"],
3
  "linter": {
4
    "rules": {
5
      "style": {
6
        "useNamingConvention": {
7
          "level": "on",
8
          "options": {
9
            "strictCase": true,
10
            "conventions": [
11
              {
12
                "selector": { "kind": "variable", "scope": "global" },
13
                "formats": ["CONSTANT_CASE"]
14
              }
15
            ]
16
          }
17
        }
18
      }
19
    }
20
  }
21
}

#7969 425963d Thanks @ematipico! - Added support for the Svelte syntax {@debug}. The Biome HTML parser is now able to parse and format the blocks:
```
1
{@debug     foo,bar,    something}
2
{@debug foo, bar, something}
```
#7986 3256f82 Thanks @lisiur! - Fixed #7981. Now Biome correctly detects and parses lang='tsx' and lang='jsx' languages when used inside in .vue files, when .experimentalFullSupportEnabled is enabled.
#7921 547c2da Thanks @dyc3! - Fixed #7854: The CSS parser, with tailwindDirectives enabled, will now parse @source inline("underline");.

#7856 c9e20c3 Thanks @Netail! - Added the nursery rule noContinue. Disallowing the usage of the continue statement, structured control flow statements such as if should be used instead.

Invalid:

1
let sum = 0,
2
  i;
3

4
for (i = 0; i < 10; i++) {
5
  if (i >= 5) {
6
    continue;
7
  }
8

9
  sum += i;
10
}

Valid:

1
let sum = 0,
2
  i;
3

4
for (i = 0; i < 10; i++) {
5
  if (i < 5) {
6
    sum += i;
7
  }
8
}

2.3.3

Patch Changes

#7907 57bd662 Thanks @ematipico! - Fixed #7839. Now the Biome parser correctly parses the Astro frontmatter even when a triple fence is inside quotes.
#7934 a35c496 Thanks @alissonlauffer! - Fixed #7919: The HTML parser now correctly handles Unicode BOM (Byte Order Mark) characters at the beginning of HTML files, ensuring proper parsing and tokenization.
#7869 c80361d Thanks @matanshavit! - Fixed #7864: Biome now preserves component tag name casing in Svelte, Astro, and Vue files.
#7926 69cecec Thanks @matanshavit! - Added the rule noParametersOnlyUsedInRecursion.

This rule detects function parameters that are exclusively used in recursive calls and can be removed to simplify the function signature since they are effectively unused.
```
1
function factorial(n, acc) {
2
  if (n === 0) return 1;
3
  return factorial(n - 1, acc); // acc is only used here
4
}
```
Fixes #6484.
#7774 2509b91 Thanks @dibashthapa! - Fixed #7657: Added the new rule no-unknown-property from ESLint
#7918 7165d06 Thanks @dyc3! - Fixed #7913: The CSS parser, with tailwindDirectives enabled, will now correctly handle @slot.
#7959 ffae203 Thanks @siketyan! - Fixed the Biome Language Server so it no longer returns an internal error when the formatter is disabled in the configuration.

2.3.2

Patch Changes

#7859 c600618 Thanks @Netail! - Added the nursery rule noIncrementDecrement, disallows the usage of the unary operators ++ and —.
#7901 0d17b05 Thanks @ematipico! - Fixed #7837, where Biome couldn’t properly parse text expressions that contained nested curly brackets. This was breaking parsing in Astro and Svelte files.
#7874 e617d36 Thanks @Bertie690! - Fixed #7230: noUselessStringConcat no longer emits false positives for multi-line strings with leading + operators.

Previously, the rule did not check for leading newlines on the + operator, emitting false positives if one occurred at the start of a line.
Notably, formatting with operatorLinebreak="before" would move the + operators to the start of lines automatically, resulting in spurious errors whenever a multi-line string was used.

Now, the rule correctly detects and ignores multi-line concatenations with leading operators as well, working regardless of the setting of operatorLinebreak.

Example
```
1
// The following code used to error if the `+` operators were at the start of lines (as opposed to the end).
2
// Now, the rule correctly recognizes this as a stylistic concatenation and ignores it.
3
const reallyLongStringThatShouldNotError =
4
  "Lorem ipsum dolor sit amet consectetur adipiscing elit." +
5
  "Quisque faucibus ex sapien vitae pellentesque sem placerat." +
6
  "In id cursus mi pretium tellus duis convallis." +
7
  "Tempus leo eu aenean sed diam urna tempor. Pulvinar vivamus fringilla";
```
#7786 33ffcd5 Thanks @daivinhtran! - Fixed #7601: Properly match Grit plugin’s code snippet with only one child.
#7901 0d17b05 Thanks @ematipico! - Fixed #7837, where Biome Language Server panicked when opening HTML-ish files when the experimental full support is enabled.

2.3.1

Patch Changes

#7840 72afdfa Thanks @ematipico! - Fixed #7838, which caused the new --css-parse-* arguments not being recognised by the ci command.
#7789 d5b416e Thanks @fronterior! - Fixed the LSP method workspace/didChangeWorkspaceFolders to perform incremental updates instead of replacing the entire folder list.
#7852 bd254c7 Thanks @dyc3! - Fixed #7843: The CSS parser, when tailwindDirectives is enabled, correctly parses --*: initial;.
#7872 0fe13fe Thanks @dyc3! - Fixed #7861: The HTML parser will now accept Svelte attribute shorthand syntax in .svelte files.
#7866 7b2600b Thanks @dyc3! - Fixed #7860: The css parser, with tailwindDirectives enabled, will now accept @plugin options.
#7853 fe90c78 Thanks @dyc3! - Fixed #7848: The css parser with tailwindDirectives enabled will now correctly parse tailwind’s source exclude syntax: @source not "foo.css";
#7878 c9f7fe5 Thanks @ematipico! - Fixed #7857: Biome now parses <script> tags as TypeScript when analysing .astro files.
#7867 b42b718 Thanks @smorimoto! - Fixed incorrect option name in HTML parser error message.

The error message for disabled text expressions incorrectly referred to the html.parser.textExpression option, which does not exist. Updated it to reference the correct html.parser.interpolation option.

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.

2.2.7

Patch Changes

#7715 b622425 Thanks @Netail! - Added the nursery rule noEmptySource, disallowing meaningless js, css, json & graphql files to prevent codebase clutter.
#7714 c7e5a14 Thanks @MeGaNeKoS! - Increased the maximum line limit for noExcessiveLinesPerFunction from 255 to 65,535 to better support large JSX/front-end components.
#5868 2db73ae Thanks @bushuai! - Fixed #5856, noRedundantUseStrict now keeps leading trivia
#7756 d665c97 Thanks @ematipico! - Improved the diagnostic message of the rule noDuplicateTestHooks.

2.2.6

Patch Changes

#7071 a8e7301 Thanks @ptkagori! - Added the useQwikMethodUsage lint rule for the Qwik domain.

This rule validates Qwik hook usage. Identifiers matching useXxx must be called only within serialisable reactive contexts (for example, inside component$, route loaders/actions, or within other Qwik hooks), preventing common Qwik antipatterns.

Invalid:

1
// Top-level hook call is invalid.
2
const state = useStore({ count: 0 });
3

4
function helper() {
5
  // Calling a hook in a non-reactive function is invalid.
6
  const loc = useLocation();
7
}

Valid:

1
component$(() => {
2
  const state = useStore({ count: 0 }); // OK inside component$.
3
  return <div>{state.count}</div>;
4
});
5

6
const handler = $(() => {
7
  const loc = useLocation(); // OK inside a $-wrapped closure.
8
  console.log(loc.params);
9
});

#7685 52071f5 Thanks @denbezrukov! - Fixed #6981: The NoUnknownPseudoClass rule no longer reports local pseudo-classes when CSS Modules are used.
#7640 899f7b2 Thanks @arendjr! - Fixed #7638: useImportExtensions no longer emits diagnostics on valid import paths that end with a query or hash.

Example
```
1
// This no longer warns if `index.css` exists:
2
import style from "../theme/index.css?inline";
```

#7071 a8e7301 Thanks @ptkagori! - Added the useQwikValidLexicalScope rule to the Qwik domain.

This rule helps you avoid common bugs in Qwik components by checking that your variables and functions are declared in the correct place.

Invalid:

1
// Invalid: state defined outside the component's lexical scope.
2
let state = useStore({ count: 0 });
3
const Component = component$(() => {
4
  return (
5
    <button onClick$={() => state.count++}>Invalid: {state.count}</button>
6
  );
7
});

Valid:

1
// Valid: state initialised within the component's lexical scope and captured by the event.
2
const Component = component$(() => {
3
  const state = useStore({ count: 0 });
4
  return <button onClick$={() => state.count++}>Valid: {state.count}</button>;
5
});

#7620 5beb1ee Thanks @Netail! - Added the rule useDeprecatedDate, which makes a deprecation date required for the graphql @deprecated directive.

Invalid

1
query {
2
  member @deprecated(reason: "Use `members` instead") {
3
    id
4
  }
5
}

Valid

1
query {
2
  member
3
    @deprecated(reason: "Use `members` instead", deletionDate: "2099-12-25") {
4
    id
5
  }
6
}

#7709 d6da4d5 Thanks @siketyan! - Fixed #7704: The useExhaustiveDependencies rule now correctly adds an object dependency when its method is called within the closure.

For example:
```
1
function Component(props) {
2
  useEffect(() => {
3
    props.foo();
4
  }, []);
5
}
```
will now be fixed to:
```
1
function Component(props) {
2
  useEffect(() => {
3
    props.foo();
4
  }, [props]);
5
}
```
#7624 309ae41 Thanks @lucasweng! - Fixed #7595: noUselessEscapeInString no longer reports $\{ escape in template literals.
#7665 29e4229 Thanks @ryan-m-walker! - Fixed #7619: Added support for parsing the CSS :state() pseudo-class.
```
1
custom-selector:state(checked) {
2
}
```
#7608 41df59b Thanks @ritoban23! - Fixed #7604: the useMaxParams rule now highlights parameter lists instead of entire function bodies. This provides more precise error highlighting. Previously, the entire function was highlighted; now only the parameter list is highlighted, such as (a, b, c, d, e, f, g, h).
#7643 459a6ac Thanks @daivinhtran! - Fixed #7580: Include plugin in summary report

Version History

2.3.7 Latest

Patch Changes

Patch Changes

Invalid

Valid

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Example

Example

Example

Patch Changes

Patch Changes

Patch Changes

Example

Invalid

Valid