All versions since 2.0.6

2.0.6

Patch Changes

#6557 fd68458 Thanks @ematipico! - Fixed a bug where Biome didn’t provide all the available code actions when requested by the editor.
#6511 72623fa Thanks @Conaclos! - Fixed #6492. The organizeImports assist action no longer duplicates a comment at the start of the file when :BLANK_LINE: precedes the first import group.
#6557 fd68458 Thanks @ematipico! - Fixed #6287 where Biome Language Server didn’t adhere to the settings.requireConfiguration option when pulling diagnostics and code actions. Note that for this configuration be correctly applied, your editor must support dynamic registration capabilities.
#6551 0b63b1d Thanks @Conaclos! - Fixed #6536. useSortedKeys no longer panics in some edge cases where object spreads are involved.
#6503 9a8fe0f Thanks @ematipico! - Fixed #6482 where nursery rules that belonged to a domain were incorrectly enabled.
#6565 e85761c Thanks @daivinhtran! - Fixed #4677: Now the noUnusedImports rule won’t produce diagnostics for types used in JSDoc comment of exports.
#6166 b8cbd83 Thanks @mehm8128! - Added the nursery rule noExcessiveLinesPerFunction. This rule restrict a maximum number of lines of code in a function body.

The following code is now reported as invalid when the limit of maximum lines is set to 2:
```
1
function foo() {
2
  const x = 0;
3
  const y = 1;
4
  const z = 2;
5
}
```
The following code is now reported as valid when the limit of maximum lines is set to 3:
```
1
const bar = () => {
2
  const x = 0;
3
  const z = 2;
4
};
```
#6553 5f42630 Thanks @denbezrukov! - Fixed #6547. Now the Biome CSS parser correctly parses @starting-style when it’s used inside other at-rules. The following example doesn’t raise an error anymore:
```
1
@layer my-demo-layer {
2
  @starting-style {
3
    div.showing {
4
      background-color: red;
5
    }
6
  }
7
}
```
#6458 05402e3 Thanks @ematipico! - Fixed an issue where the rule useSemanticElements used the incorrect range when positioning suppression comments.
#6560 6d8a6b9 Thanks @siketyan! - Fixed #6559: the error message on detected a large file was outdated and referred a removed configuration option files.ignore.
#6458 05402e3 Thanks @ematipico! - Fixed #6384. The rule useAltText now emits a diagnostic with a correct range, so suppression comments can work correctly.
#6518 7a56288 Thanks @wojtekmaj! - Fixed #6508, where the rule noUselessFragments incorrectly flagged Fragments containing HTML entities as unnecessary.
#6517 c5217cf Thanks @arendjr! - Fixed #6515. When using the extends field to extend a configuration from an NPM package, we now accept the condition names "biome" and "default" for exporting the configuration in the package.json.

This means that where previously your package.json had to contain an export declaration similar to this:
```
1
{
2
  "exports": {
3
    ".": "./biome.json"
4
  }
5
}
```
You may now use one of these as well:
```
1
{
2
  "exports": {
3
    ".": {
4
      "biome": "./biome.json"
5
    }
6
  }
7
}
```
Or:
```
1
{
2
  "exports": {
3
    ".": {
4
      "default": "./biome.json"
5
    }
6
  }
7
}
```
#6219 a3a3715 Thanks @huangtiandi1999! - Added new nursery rule noUnassignedVariables, which disallows let or var variables that are read but never assigned.

The following code is now reported as invalid:
```
1
let x;
2
if (x) {
3
  console.log(1);
4
}
```
The following code is now reported as valid:
```
1
let x = 1;
2
if (x) {
3
  console.log(1);
4
}
```
#6395 f62e748 Thanks @mdevils! - Added the new nursery rule noImplicitCoercion, which disallows shorthand type conversions in favor of explicit type conversion functions.

Example (Invalid): Boolean conversion using double negation:
```
1
!!foo;
2
!!(foo + bar);
```
Example (Invalid): Number conversion using unary operators:
```
1
+foo;
2
-(-foo);
3
foo - 0;
4
foo * 1;
5
foo / 1;
```
Example (Invalid): String conversion using concatenation:
```
1
"" + foo;
2
foo + "";
3
`` + foo;
4
foo += "";
```
Example (Invalid): Index checking using bitwise NOT:
```
1
~foo.indexOf(1);
2
~foo.bar.indexOf(2);
```
Example (Valid): Using explicit type conversion functions:
```
1
Boolean(foo);
2
Number(foo);
3
String(foo);
4
foo.indexOf(1) !== -1;
```
#6544 f28b075 Thanks @daivinhtran! - Fixed #6536. Now the rule noUselessFragments produces diagnostics for a top-level useless fragment that is in a return statement.
#6320 5705f1a Thanks @mdevils! - Added the new nursery rule useUnifiedTypeSignature, which disallows overload signatures that can be unified into a single signature.

Overload signatures that can be merged into a single signature are redundant and should be avoided. This rule helps simplify function signatures by combining overloads by making parameters optional and/or using type unions.

Example (Invalid): Overload signatures that can be unified:
```
1
function f(a: number): void;
2
function f(a: string): void;
```
```
1
interface I {
2
  a(): void;
3
  a(x: number): void;
4
}
```
Example (Valid): Unified signatures:
```
1
function f(a: number | string): void {}
```
```
1
interface I {
2
  a(x?: number): void;
3
}
```
Example (Valid): Different return types cannot be merged:
```
1
interface I {
2
  f(): void;
3
  f(x: number): number;
4
}
```
#6545 2782175 Thanks @ematipico! - Fixed #6529, where the Biome Language Server would emit an error when the user would open a file that isn’t part of its workspace ( node_modules or external files). Now the language server doesn’t emit any errors and it exits gracefully.

#6524 a27b825 Thanks @vladimir-ivanov! - Fixed #6500: The useReadonlyClassProperties rule now correctly marks class properties as readonly when they are assigned in a constructor, setter or method, even if the assignment occurs inside an if or else block.

The following code is now correctly detected by the rule:

1
class Price {
2
  #price: string;
3

4
  @Input()
5
  set some(value: string | number) {
6
    if (
7
      value === undefined ||
8
      value === null ||
9
      value === "undefined" ||
10
      value === "null" ||
11
      Number.isNaN(value)
12
    ) {
13
      this.#price = "";
14
    } else {
15
      this.#price = "" + value;
16
    }
17
  }
18
}

#6355 e128ea9 Thanks @anthonyshew! - Added a new nursery rule noAlert that disallows the use of alert, confirm and prompt.

The following code is deemed incorrect:
```
1
alert("here!");
```
#6548 37e9799 Thanks @ematipico! - Fixed #6459, where the Biome LSP was not taking into account the correct settings when applying source.fixAll.biome code action.

2.1.0

Minor Changes

#6512 0c0bf82 Thanks @arendjr! - The rule noFloatingPromises can now detect floating arrays of Promises.

Invalid examples

1
// This gets flagged because the Promises are not handled.
2
[1, 2, 3].map(async (x) => x + 1);

Valid examples

1
await Promise.all([1, 2, 3].map(async (x) => x + 1));

#6637 6918085 Thanks @arendjr! - Type inference is now able to handle the sequence operator ( ,), as well as post- and pre-update operators: ++.

Example

1
let x = 5;
2

3
// We now infer that `x++` resolves to a number, while the expression as a whole
4
// becomes a Promise:
5
(x++, new Promise((resolve) => resolve("comma")));

#6752 c9eaca4 Thanks @arendjr! - Fixed #6646: .gitignore files are now picked up even when running Biome from a nested directory, or when the ignore file itself is ignored through files.includes.
#6746 90aeead Thanks @arendjr! - biome migrate no longer enables style rules that were recommended in v1, because that would be undesirable for users upgrading from 2.0.

Users who are upgrading from Biome 1.x are therefore advised to first upgrade to Biome 2.0, and run the migration, before continuing to Biome 2.1 or later.

#6583 d415a3f Thanks @arendjr! - Added the nursery rule noMisusedPromises.

It signals Promises in places where conditionals or iterables are expected.

Invalid examples

1
const promise = Promise.resolve("value");
2

3
// Using a `Promise` as conditional is always truthy:
4
if (promise) {
5
  /* ... */
6
}
7

8
// Spreading a `Promise` has no effect:
9
console.log({ foo: 42, ...promise });
10

11
// This does not `await` the `Promise`s from the callbacks,
12
// so it does not behave as you may expect:
13
[1, 2, 3].forEach(async (value) => {
14
  await fetch(`/${value}`);
15
});

Valid examples

1
const promise = Promise.resolve("value");
2

3
if (await promise) {
4
  /* ... */
5
}
6

7
console.log({ foo: 42, ...(await promise) });

#6405 cd4a9bb Thanks @vladimir-ivanov! - Added the ignoreRestSiblings option to the noUnusedFunctionParameters rule.

This option is used to ignore unused function parameters that are siblings of the rest parameter.

The default is false, which means that unused function parameters that are siblings of the rest parameter will be reported.

Example
```
1
{
2
  "rules": {
3
    "noUnusedFunctionParameters": ["error", { "ignoreRestSiblings": true }]
4
  }
5
}
```
#6614 0840021 Thanks @arendjr! - We have implemented a more targeted version of the scanner, which ensures that if you provide file paths to handle on the CLI, the scanner will exclude directories that are not relevant to those paths.

Note that for many commands, such as biome check and biome format, the file paths to handle are implicitly set to the current working directory if you do not provide any path explicitly. The targeted scanner also works with such implicit paths, which means that if you run Biome from a subfolder, other folders that are part of the project are automatically exempted.

Use cases where you invoke Biome from the root of the project without providing a path, as well as those where project rules are enabled, are not expected to see performance benefits from this.

Implemented #6234, and fixed #6483 and #6563.
#6488 c5ee385 Thanks @ianzone! - nx.json and project.json have been added to the list of well-known files.
#6720 52e36ae Thanks @minht11! - Added $ symbol to organizeImports :ALIAS: group.

import { action } from '$lib' will be treated as alias import.

Patch Changes

#6712 2649ac6 Thanks @sterliakov! - Fixed #6595: Biome now supports // biome-ignore-all file-level suppressions in files that start with a shebang (#!).
#6758 28dc49e Thanks @arendjr! - Fixed #6573: Grit plugins can now match bare imports.

Example

The following snippet:
```
1
`import $source`
```
will now match:
```
1
import "main.css";
```

#6550 b424f46 Thanks @arendjr! - Type inference is now able to handle logical expressions: &&, ||, and ??.

Examples

1
// We can now infer that because `true` is truthy, the entire expression
2
// evaluates to a `Promise`.
3
true && Promise.reject("logical operator bypass");
4

5
// And we know that this doesn't:
6
false && Promise.reject("logical operator bypass");
7

8
// Truthiness, falsiness, and non-nullishness can all be determined on more
9
// complex expressions as well. So the following also works:
10
type Nullish = null | undefined;
11

12
type Params = {
13
  booleanOption: boolean | Nullish;
14
  falsyOption: false | Nullish;
15
};
16

17
function foo({ booleanOption, falsyOption }: Params) {
18
  // This may be a Promise:
19
  booleanOption ?? Promise.reject("logical operator bypass");
20

21
  // But this never is:
22
  falsyOption && Promise.reject("logical operator bypass");
23
}

#6413 4aa0e50 Thanks @wojtekmaj! - Improved error message in useDateNow rule.
#6673 341e062 Thanks @dyc3! - Fixed a case where the HTML formatter would mangle embedded language tags if whitespaceSensitivity was set to strict
#6642 a991229 Thanks @unvalley! - Fixed #4494: The noSecrets rule now correctly uses the entropyThreshold option to detect secret like strings.
#6520 0c43545 Thanks @arendjr! - Type inference is now able to handle ternary conditions in type aliases.

Note that we don’t attempt to evaluate the condition itself. The resulting type is simply a union of both conditional outcomes.

Example
```
1
type MaybeResult<T> = T extends Function ? Promise<string> : undefined;
2

3
// We can now detect this function _might_ return a `Promise`:
4
function doStuff<T>(input: T): MaybeResult<T> {
5
  /* ... */
6
}
```
#6711 1937691 Thanks @sterliakov! - Fixed #6654: Fixed range highlighting of <explanation> placeholder in inline suppression block comments.
#6756 d12b26f Thanks @dyc3! - Fixed #6669: Added an exception to noUnusedImports to allow type augmentation imports.
```
1
import type {} from "@mui/lab/themeAugmentation";
```
#6643 df15ad6 Thanks @skewb1k!
Fixed #4994: LSP server registered some capabilities even when the client did not support dynamic registration.
#6599 5e611fa Thanks @vladimir-ivanov! - Fixed #6380: The noFocusedTests rule now correctly displays the function name in the diagnostic message when a test is focused.

Every instance of a focused test function (like fdescribe, fit, ftest and only) had the word ‘only’ hardcoded. This has been updated to use the actual function name, so the message is now more accurate and specific.

Example for fdescribe:
```
1
  i The 'fdescribe' method is often used for debugging or during implementation.
2

3
  i Consider removing 'f' prefix from 'fdescribe' to ensure all tests are executed.
```

#6671 0c9ab43 Thanks @vladimir-ivanov! - Fixed #6634: The useReadonlyClassProperties rule now correctly flags mutations in class getters and in arrow functions within class properties.

Examples:

1
class GetterWithMutationValue {
2
  #value: string;
3

4
  get value() {
5
    if (!this.#value) {
6
      this.#value = "defaultValue";
7
    }
8

9
    return this.#value;
10
  }
11
}

1
class ClassPropertyArrowFunctionWithMutation {
2
  private bar: string | null = null;
3

4
  readonly action = () => {
5
    this.bar = "init";
6
  };
7
}

#6682 ca04cea Thanks @ematipico! - Fixed #6668: Biome Assist is now enabled by default for CSS files.

#6525 66b089c Thanks @arendjr! - Type inference can now infer the return types of functions and methods without annotations.

Examples

1
const sneakyObject = {
2
  doSomething() {
3
    return Promise.resolve("This is a floating promise!");
4
  },
5
};
6

7
// We can now detect that `doSomething()` returns a `Promise`.
8
sneakyObject.doSomething();

#6531 c06df79 Thanks @arendjr! - Biome’s type inference now detects the type of properties with getters.

Examples

1
const sneakyObject2 = {
2
  get something() {
3
    return new Promise((_, reject) => reject("This is a floating promise!"));
4
  },
5
};
6
// We now detect this is a Promise:
7
sneakyObject2.something;

#6587 a330fcc Thanks @Conaclos! - organizeImports is now able to sort named specifiers and import attributes with bogus nodes.
#6618 6174869 Thanks @Shinyaigeek! - Fixed #6610: JSON import attributes are now correctly detected when they contain extra whitespace.
#6753 fce5d2c Thanks @dyc3! - Improved the error messages when Biome is provided incompatible arguments on the CLI.
#6587 a330fcc Thanks @Conaclos! - Fixed #6491: The action of useSortedKeys removed comments or wrongly transferred them to distinct nodes.
#6696 92964a7 Thanks @unvalley! - Fixed #6633: The noImplicitCoercion rule no longer reports diagnostics for 1 / value expressions.
```
1
1 / value; // no error
```
#6683 43d871e Thanks @ematipico! - Fixed #6537: Biome no longer removes the trailing comma from JSON files when formatter.json.trailingCommas is explicitly set to "all".
#6693 bfdce0b Thanks @dyc3! - Fixed #6691: The HTML parser will now consider . to be a valid character for tag names.
#6716 ead03d1 Thanks @siketyan! - The Biome LSP server no longer responds with an error for a textDocument/codeActions request when Biome doesn’t support a feature for the file (e.g. Code actions aren’t supported in GritQL files).
#6679 7bf9a60 Thanks @marko-hologram! - Fixed #6638: JavaScript formatter overrides options now correctly override expand option. JSON formatter overrides options now correctly override bracketSpacing and expand options.
#6717 7f5b541 Thanks @siketyan! - Fixed #6688: the noUselessFragments no longer reports <Fragment /> elements that includes HTML character entities.
#6600 853e1b5 Thanks @daivinhtran! - Fixed #4677: The noUnusedImports rule won’t produce diagnostics for types used in comments of static members anymore.
#6662 3afc804 Thanks @arendjr! - If a nested configuration file is ignored by the root configuration, it will now actually be ignored.

Biome has an exception in place for configuration files so they cannot be ignored, because the configuration files are vital to Biome itself. But this exception was incorrectly applied to nested configurations as well. Now only the root configuration is exempt from being ignored.
#6596 c0718ca Thanks @ematipico! - Fixed #6566: Biome no longer errors when using the option --files-ignore-unknown=true in stdin mode.

Biome has also become less strict when using --stdin-file-path in stdin mode. It will no longer error if the file path doesn’t contain an extension, but instead it will return the original content.
#6562 153eda7 Thanks @vladimir-ivanov! - Added the nursery rule noMagicNumbers. The rule detects and reports the use of “magic numbers” — numeric literals that are used directly in code without being assigned to a named constant.

Example
```
1
let total = price * 1.23; // Magic number for tax rate will highlight 1.23 as magic number
```
#6663 af78d6d Thanks @ematipico! - Fixed #6656: Biome now correctly formats HTML void elements such as <meta> when they contain a self-closing slash.
```
1
<meta foo="bar" />
2
<meta foo="bar">
```
#6732 31e4396 Thanks @vladimir-ivanov! - Resolved #6281: Improved performance of handling package.json files in the scanner.
#6625 19cb475 Thanks @arendjr! - Fixed #6616: Fixed an issue with extending configurations that contained an explicit root field while the configuration in the project did not.
#6650 19aab18 Thanks @sterliakov! - Fixed #6621: Improved handling of multiple adjacent line suppressions. Biome now handles such suppressions separately, tracking whether each one is used.
#6700 cdd6e17 Thanks @denbezrukov! - Fixed #6680: Biome incorrectly formatted container-style queries by inserting misplaced spaces.
```
1
@container style (--responsive: true) {}
2
@container style(--responsive: true) {}
```
#6709 ecf3954 Thanks @dyc3! - Fixed #6038: Fixed a false positive in noShadow where a function parameter in a type definition was erroneously flagged as a violation.

#6593 a4acbb7 Thanks @arendjr! - Type inference is now able to handle ternary conditions in expressions.

Examples

1
const condition = Math.random() > -1; // Always true, but dynamic to linter
2

3
// We now detect that this may return a `Promise`.
4
condition ? Promise.reject("ternary bypass") : null;
5

6
// On the other hand, we know the following is never a `Promise`:
7
const alwaysFalsy = 0;
8
alwaysFalsy ? Promise.reject("ternary bypass") : null;

#6428 4b501d3 Thanks @siketyan! - Added MemoryFileSystem to the WASM API.

You can now insert a file from your JS code:

1
import { MemoryFileSystem, Workspace } from "@biomejs/wasm-web";
2

3
const fs = new MemoryFileSystem();
4
const workspace = Workspace.withFileSystem(fs);
5

6
fs.insert("/index.js", new TextEncoder().encode("let foo = 1;"));
7
fs.remove("/index.js");

#6594 626d4a1 Thanks @ematipico! - Fixed #6528: Biome didn’t return the correct output when applying source.fixAll.biome inside Astro/Vue/Svelte files that contained safe fixed.

2.1.1

Patch Changes

#6781 9bbd34f Thanks @siketyan! - Fixed the FileFeaturesResult interface in the WASM API was defined as a mapped object but the actual value was a Map object.
#6761 cf3c2ce Thanks @dyc3! - Fixed #6759, a false positive for noFocusedTests that was triggered by calling any function with the name fit on any object.

The following code will now pass the noFocusedTests rule:
```
1
import foo from "foo";
2
foo.fit();
```

2.1.2

Patch Changes

#6865 b35bf64 Thanks @denbezrukov! - Fix #6485: Handle multiple semicolons correctly in blocks (#6485)
```
1
div {
2
  box-sizing: border-box;
3
  color: red;
4
}
```
#6798 3579ffa Thanks @dyc3! - Fixed #6762, Biome now knows that ~/.config/zed/settings.json and ~/.config/Code/User/settings.json allows comments by default.
#6839 4cd62d8 Thanks @ematipico! - Fixed #6838, where the Biome File Watcher incorrectly watched and stored ignored files, causing possible memory leaks when those files were dynamically created (e.g. built files).
#6879 0059cd9 Thanks @denbezrukov! - Refactor: remove one level of indirection for CSS declarations with semicolon Previously, accessing a declaration from a list required an extra step:
```
1
item
2
.as_any_css_declaration_with_semicolon()
3
.as_css_declaration_with_semicolon()
```
Now, it can be done directly with:
```
1
item.as_css_declaration_with_semicolon()
```
#6839 4cd62d8 Thanks @ematipico! - Fixed a bug where the Biome Language Server didn’t correctly ignore specific files when vcs.useIgnoreFile is set to true.
#6884 5ff50f8 Thanks @arendjr! - Improved the performance of noImportCycles by ~30%.
#6903 241dd9e Thanks @arendjr! - Fixed #6829: Fixed a false positive reported by useImportExtensions when importing a .js file that had a matching .d.ts file in the same folder.
#6846 446112e Thanks @darricheng! - Fixed an issue where biome was using the wrong string quotes when the classes string has quotes, resulting in invalid code after applying the fix.
#6823 eebc48e Thanks @arendjr! - Improved #6172: Optimised the way function arguments are stored in Biome’s type inference. This led to about 10% performance improvement in RedisCommander.d.ts and about 2% on @next/font type definitions.
#6878 3402976 Thanks @ematipico! - Fixed a bug where the Biome Language Server would apply an unsafe fix when using the code action quickfix.biome.

Now Biome no longer applies an unsafe code fix when using the code action quickfix.biome.

#6794 4d5fc0e Thanks @vladimir-ivanov! - Fixed #6719: The noInvalidUseBeforeDeclaration rule covers additional use cases.

Examples:

1
type Bar = { [BAR]: true };
2
const BAR = "bar";

1
interface Bar {
2
  child: { grandChild: { [BAR]: typeof BAR; enumFoo: EnumFoo } };
3
}
4
const BAR = "bar";
5
enum EnumFoo {
6
  BAR = "bar",
7
}

#6863 531e97e Thanks @dyc3! - Biome now considers whether the linter is enabled when figuring out how the project should be scanned. Resolves #6815.
#6832 bdbc2b1 Thanks @togami2864! - Fixed #6165: Fixed false negative in noUnusedPrivateClassMembers rule when checking member usage in classes
#6839 4cd62d8 Thanks @ematipico! - Fixed a bug where the root ignore file wasn’t correctly loaded during the scanning phase, causing false positives and incorrect expectations among users.

Now, when using vcs.useIgnoreFile, the **the globs specified in the ignore file from the project root ** will have the same semantics as the files.includes setting of the root configuration.

Refer to the relative web page to understand how they work.
#6898 5beb024 Thanks @arendjr! - Fixed #6891: Improved type inference for array indices.

Example:
```
1
const numbers: number[];
2
numbers[42]; // This now infers to `number | undefined`.
```

#6809 8192451 Thanks @arendjr! - Fixed #6796: Fixed a false positive that happened in noFloatingPromises when calling functions that were declared as part of for ... of syntax inside async functions.

Instead, the variables declared inside for ... of loops are now correctly inferred if the expression being iterated evaluates to an Array (support for other iterables will follow later).

Invalid example

1
const txStatements: Array<(tx) => Promise<any>> = [];
2

3
db.transaction((tx: any) => {
4
  for (const stmt of txStatements) {
5
    // We correctly flag this resolves to a `Promise`:
6
    stmt(tx);
7
  }
8
});

Valid example

1
async function valid(db) {
2
  const txStatements: Array<(tx: any) => void> = [(tx) => tx.insert().run()];
3

4
  db.transaction((tx: any) => {
5
    for (const stmt of txStatements) {
6
      // We don't flag a false positive here anymore:
7
      stmt(tx);
8
    }
9
  });
10
}

#6757 13a0818 Thanks @mdevils! - Added the rule noVueReservedProps, resolves #6309.

It prevents the use of reserved Vue prop names such as key and ref which can cause conflicts and unexpected behavior in Vue components.

Invalid example

1
import { defineComponent } from "vue";
2

3
export default defineComponent({
4
  props: ["ref", "key", "foo"],
5
});

1
<script setup>
2
defineProps({
3
  ref: String,
4
  key: String,
5
  foo: String,
6
});
7
</script>

Valid examples

1
import { defineComponent } from "vue";
2

3
export default defineComponent({
4
  props: ["foo"],
5
});

1
<script setup>
2
defineProps({ foo: String });
3
</script>

#6840 1a57b51 Thanks @denbezrukov! - Allow multiple identifiers in ::part() pseudo-element selector.
```
1
::part(first second) {
2
}
```
#6845 4fd44ec Thanks @arendjr! - Fixed #6510: The scanner no longer shows diagnostics on inaccessible files unless --verbose is used.
#6844 b7e2d4d Thanks @sterliakov! - Fixed #6837: Fixed regression with multiple consecutive line suppression comments using instances (like // biome-ignore lint/correctness/useExhaustiveDependencies(depName): reason).
#6818 5f3f5a6 Thanks @siketyan! - Fixed an issue where textDocument/codeAction in the LSP could respond with outdated text edits after the workspace watcher observed outdated changes to the file.
#6804 3e6ab16 Thanks @arendjr! - noFloatingPromises will no longer suggest to add await keyword inside synchronous callbacks nested inside async functions.
#6901 c9e969a Thanks @arendjr! - Fixed #6777: Fixed type inference handling of this to avoid infinite recursion.

Thanks to @sterliakov for the thorough investigation!

#6855 d1581c7 Thanks @vladimir-ivanov! - Fixed #6775: useReadonlyClassProperties now also captures mutations inside function arguments.

Example:

1
class Counter {
2
  private counter: number;
3
  count() {
4
    console.log(this.counter++);
5
    const counterString = `${this.counter++}`;
6
  }
7
}

#6839 4cd62d8 Thanks @ematipico! - Fixed a bug where Biome didn’t throw any error when vcs.useIgnoreFile is set to true, and there wasn’t any ignore file read. Now Biome correctly throws an error if no ignore files are found.
#6911 6d68074 Thanks @arendjr! - Fixed #6838: Reduce resource consumption in the Biome Language Server by using non-recursive filesystem watchers instead of recursive ones.

Watchers are responsible for notifying Biome of changes to files in the filesystem. We used to set up a single recursive watcher, but that meant that Biome would receive filesystem notifications for all files in your project, even for ignored folders such as build/ or dist/ folders.

With this patch, we set up non-recursive watchers only for the folders that are relevant to a project.

Related to this, we also solved an issue where incoming notifications were incorrectly filtered, causing ignored files to be processed and stored in our module graph anyway.

2.1.3

Patch Changes

#7057 634a667 Thanks @mdevils! - Added the rule noVueReservedKeys, which prevents the use of reserved Vue keys.

It prevents the use of Vue reserved keys such as those starting with like $el, $data, $props) and keys starting with \_ in data properties, which can cause conflicts and unexpected behavior in Vue components.

Invalid example

1
<script>
2
export default {
3
  data: {
4
    $el: "",
5
    _foo: "bar",
6
  },
7
};
8
</script>

1
<script>
2
export default {
3
  computed: {
4
    $data() {
5
      return this.someData;
6
    },
7
  },
8
};
9
</script>

Valid examples

1
<script>
2
export default {
3
  data() {
4
    return {
5
      message: "Hello Vue!",
6
      count: 0,
7
    };
8
  },
9
};
10
</script>

1
<script>
2
export default {
3
  computed: {
4
    displayMessage() {
5
      return this.message;
6
    },
7
  },
8
};
9
</script>

#6941 734d708 Thanks @JamBalaya56562! - Added @eslint-react/no-nested-component-definitions as a rule source for noNestedComponentDefinitions. Now it will get picked up by biome migrate --eslint.
#6463 0a16d54 Thanks @JamBalaya56562! - Fixed a website link for the useComponentExportOnlyModules linter rule to point to the correct URL.
#6944 e53f2fe Thanks @sterliakov! - Fixed #6910: Biome now ignores type casts and assertions when evaluating numbers for noMagicNumbers rule.
#6991 476cd55 Thanks @denbezrukov! - Fixed #6973: Add support for parsing the :active-view-transition-type() pseudo-class
```
1
:active-view-transition-type(first second) {
2
}
```
#6992 0b1e194 Thanks @ematipico! - Added a new JSON rule called noQuickfixBiome, which disallow the use of code action quickfix.biome inside code editor settings.
#6943 249306d Thanks @JamBalaya56562! - Fixed @vitest/eslint-plugin source url.
#6947 4c7ed0f Thanks @JamBalaya56562! - Fixed ESLint migration for the rule prefer-for from eslint-plugin-solid to Biome’s useForComponent.
#6976 72ebadc Thanks @siketyan! - Fixed #6692: The rules noUnusedVariables and noUnusedFunctionParameters no longer cause an infinite loop when the suggested name is not applicable (e.g. the suggested name is already declared in the scope).
#6990 333f5d0 Thanks @rvanlaarhoven! - Fixed the documentation URL for lint/correctness/noUnknownPseudoClass
#7000 4021165 Thanks @harxki! - Fixed #6795: noUnassignedVariables now correctly recognizes variables used in JSX ref attributes.
#7044 b091ddf Thanks @ematipico! - Fixed #6622, now the rule useSemanticElements works for JSX self-closing elements too.
#7014 c4864e8 Thanks @siketyan! - Fixed #6516: The biome migrate command no longer break the member list with trailing comments.

#6979 29cb6da Thanks @unvalley! - Fixed #6767: useSortedClasses now correctly removes leading and trailing whitespace in className.

Previously, trailing spaces in className were not fully removed.

1
// Think we have this code:
2
<div className="text-sm font-bold            " />
3

4
// Before: applied fix, but a trailing space was preserved
5
<div className="font-bold text-sm " />
6

7
// After: applied fix, trailing spaces removed
8
<div className="font-bold text-sm" />

#7055 ee4828d Thanks @dyc3! - Added the nursery rule useReactFunctionComponents. This rule enforces the preference to use function components instead of class components.

Valid:
```
1
function Foo() {
2
  return <div>Hello, world!</div>;
3
}
```
Invalid:
```
1
class Foo extends React.Component {
2
  render() {
3
    return <div>Hello, world!</div>;
4
  }
5
}
```
#6924 2d21be9 Thanks @ematipico! - Fixed #113, where the Biome Language Server didn’t correctly update the diagnostics when the configuration file is modified in the editor. Now the diagnostics are correctly updated every time the configuration file is modified and saved.
#6931 e6b2380 Thanks @arendjr! - Fixed #6915: useHookAtTopLevel no longer hangs when rules call themselves recursively.
#7012 01c0ab4 Thanks @siketyan! - Fixed #5837: Invalid suppression comments such as biome-ignore-all-start or biome-ignore-all-end no longer causes a panic.
#6949 48462f8 Thanks @fireairforce! - Support parse import defer(which is a stage3 proposal). The syntax look like this:
```
1
import defer * as foo from "<specifier>";
```

#6938 5feb5a6 Thanks @vladimir-ivanov! - Fixed #6919 and #6920: useReadonlyClassProperties now does checks for mutations in async class methods.

Example:

1
class Counter3 {
2
  private counter: number;
3
  async count() {
4
    this.counter = 1;
5
    const counterString = `${this.counter++}`;
6
  }
7
}

#6942 cfda528 Thanks @sterliakov! - Fixed #6939. Biome now understands this binding in classes outside of methods.

2.1.4

Patch Changes

#7121 b9642ab Thanks @arendjr! - Fixed #7111: Imported symbols using aliases are now correctly recognised.
#7103 80515ec Thanks @omasakun! - Fixed #6933 and #6994.

When the values of private member assignment expressions, increment expressions, etc. are used, those private members are no longer marked as unused.
#6887 0cc38f5 Thanks @ptkagori! - Added the noQwikUseVisibleTask rule to Qwik.

This rule is intended for use in Qwik applications to warn about the use of useVisibleTask$() functions which require careful consideration before use.

Invalid:
```
1
useVisibleTask$(() => {
2
  console.log("Component is visible");
3
});
```
Valid:
```
1
useTask$(() => {
2
  console.log("Task executed");
3
});
```
#7084 50ca155 Thanks @ematipico! - Added the new nursery rule noUnnecessararyConditions, which detects whenever some conditions don’t change during the life cycle of the program, and truthy or false, hence deemed redundant.

For example, the following snippets will trigger the rule:
```
1
// Always truthy literal conditions
2
if (true) {
3
  console.log("always runs");
4
}
```
```
1
// Unnecessary condition on constrained string type
2
function foo(arg: "bar" | "baz") {
3
  if (arg) {
4
    // This check is unnecessary
5
  }
6
}
```
#6887 0cc38f5 Thanks @ptkagori! - Added the useImageSize rule to Biome.

The useImageSize rule enforces the use of width and height attributes on <img> elements for performance reasons. This rule is intended to prevent layout shifts and improve Core Web Vitals by ensuring images have explicit dimensions.

Invalid:
```
1
<img src="/image.png" />
2
<img src="https://example.com/image.png" />
3
<img src="/image.png" width="200" />
4
<img src="/image.png" height="200" />
```
Valid:
```
1
<img width="200" height="600" src="/static/images/portrait-01.webp" />
2
<img width="100" height="100" src="https://example.com/image.png" />
```
#6887 0cc38f5 Thanks @ptkagori! - Added the useAnchorHref rule to Biome.

The useAnchorHref rule enforces the presence of an href attribute on <a> elements in JSX. This rule is intended to ensure that anchor elements are always valid and accessible.

Invalid:
```
1
<a>Link</a>
```
```
1
<a target="_blank">External</a>
```
Valid:
```
1
<a href="/home">Home</a>
```
```
1
<a href="https://example.com" target="_blank">
2
  External
3
</a>
```
#7100 29fcb05 Thanks @Jayllyz! - Added the rule noNonNullAssertedOptionalChain.

This rule prevents the use of non-null assertions (!) immediately after optional chaining expressions ( ?.). Optional chaining is designed to safely handle nullable values by returning undefined when the chain encounters null or undefined. Using a non-null assertion defeats this purpose and can lead to runtime errors.
```
1
// Invalid - non-null assertion after optional chaining
2
obj?.prop!;
3
obj?.method()!;
4
obj?.[key]!;
5
obj?.prop!;
6

7
// Valid - proper optional chaining usage
8
obj?.prop;
9
obj?.method();
10
obj?.prop ?? defaultValue;
11
obj!.prop?.method();
```
#7129 9f4538a Thanks @drwpow! - Removed option, combobox, listbox roles from useSemanticElements suggestions
#7106 236deaa Thanks @arendjr! - Fixed #6985: Inference of return types no longer mistakenly picks up return types of nested functions.
#7102 d3118c6 Thanks @omasakun! - Fixed #7101: noUnusedPrivateClassMembers now handles members declared as part of constructor arguments:
1. If a class member defined in a constructor argument is only used within the constructor, it removes the private modifier and makes it a plain method argument.
2. If it is not used at all, it will prefix it with an underscore, similar to noUnusedFunctionParameter.
#7104 5395297 Thanks @harxki! - Reverting to prevent regressions around ref handling
#7143 1a6933a Thanks @siketyan! - Fixed #6799: The noImportCycles rule now ignores type-only imports if the new ignoreTypes option is enabled (enabled by default).
[!WARNING] Breaking Change: The noImportCycles rule no longer detects import cycles that include one or more type-only imports by default. To keep the old behaviour, you can turn off the ignoreTypes option explicitly:
```
1
{
2
  "linter": {
3
    "rules": {
4
      "nursery": {
5
        "noImportCycles": {
6
          "options": {
7
            "ignoreTypes": false
8
          }
9
        }
10
      }
11
    }
12
  }
13
}
```
#7099 6cc84cb Thanks @arendjr! - Fixed #7062: Biome now correctly considers extended configs when determining the mode for the scanner.
#6887 0cc38f5 Thanks @ptkagori! - Added the useQwikClasslist rule to Biome.

This rule is intended for use in Qwik applications to encourage the use of the built-in class prop (which accepts a string, object, or array) instead of the classnames utility library.

Invalid:
```
1
<div class={classnames({ active: true, disabled: false })} />
```
Valid:
```
1
<div classlist={{ active: true, disabled: false }} />
```
#7019 57c15e6 Thanks @fireairforce! - Added support in the JS parser for import source(a stage3 proposal). The syntax looks like:
```
1
import source foo from "<specifier>";
```
#7053 655049e Thanks @jakeleventhal! - Added the useConsistentTypeDefinitions rule.

This rule enforces consistent usage of either interface or type for object type definitions in TypeScript.

The rule accepts an option to specify the preferred style:
- interface (default): Prefer using interface for object type definitions
- type: Prefer using type for object type definitions
Examples:
```
1
// With default option (interface)
2
// ❌ Invalid
3
type Point = { x: number; y: number };
4

5
// ✅ Valid
6
interface Point {
7
  x: number;
8
  y: number;
9
}
10

11
// With option { style: "type" }
12
// ❌ Invalid
13
interface Point {
14
  x: number;
15
  y: number;
16
}
17

18
// ✅ Valid
19
type Point = { x: number; y: number };
```
The rule will automatically fix simple cases where conversion is straightforward.

2.2.0

Minor Changes

#5506 1f8755b Thanks @sakai-ast! - The noRestrictedImports rule has been enhanced with a new patterns option. This option allows for more flexible and powerful import restrictions using gitignore-style patterns.

You can now define patterns to restrict entire groups of modules. For example, you can disallow imports from any path under import-foo/ except for import-foo/baz.
```
1
{
2
  "options": {
3
    "patterns": [
4
      {
5
        "group": ["import-foo/*", "!import-foo/baz"],
6
        "message": "import-foo is deprecated, except for modules in import-foo/baz."
7
      }
8
    ]
9
  }
10
}
```
Invalid examples
```
1
import foo from "import-foo/foo";
2
import bar from "import-foo/bar";
```
Valid examples
```
1
import baz from "import-foo/baz";
```
Additionally, the patterns option introduces importNamePattern to restrict specific import names using regular expressions. The following example restricts the import names that match x , y or z letters from modules under import-foo/.
```
1
{
2
  "options": {
3
    "patterns": [
4
      {
5
        "group": ["import-foo/*"],
6
        "importNamePattern": "[xyz]"
7
      }
8
    ]
9
  }
10
}
```
Invalid examples
```
1
import { x } from "import-foo/foo";
```
Valid examples
```
1
import { foo } from "import-foo/foo";
```
Furthermore, you can use the invertImportNamePattern boolean option to reverse this logic. When set to true, only the import names that match the importNamePattern will be allowed. The following configuration only allows the import names that match x , y or z letters from modules under import-foo/.
```
1
{
2
  "options": {
3
    "patterns": [
4
      {
5
        "group": ["import-foo/*"],
6
        "importNamePattern": "[xyz]",
7
        "invertImportNamePattern": true
8
      }
9
    ]
10
  }
11
}
```
Invalid examples
```
1
import { foo } from "import-foo/foo";
```
Valid examples
```
1
import { x } from "import-foo/foo";
```
#6506 90c5d6b Thanks @nazarhussain! - Allow customization of the sort order for different sorting actions. These actions now support a sort option:
- assist/source/useSortedKeys now has a sortOrder option
- assist/source/useSortedAttributes now has a sortOrder option
- assist/source/organizeImports now has an identifierOrder option
For each of these options, the supported values are the same:
1. natural. Compares two strings using a natural ASCII order. Uppercase letters come first (e.g. A < a < B < b) and number are compared in a human way (e.g. 9 < 10). This is the default value.
2. **lexicographic **. Strings are ordered lexicographically by their byte values. This orders Unicode code points based on their positions in the code charts. This is not necessarily the same as “alphabetical” order, which varies by language and locale.
#7159 df3afdf Thanks @ematipico! - Added the new rule useBiomeIgnoreFolder. Since v2.2, Biome correctly prevents the indexing and crawling of folders.

However, the correct pattern has changed. This rule attempts to detect incorrect usage, and promote the new pattern:
biome.json
```
1
{
2
  "files": {
3
    "includes": [
4
      "!dist/**",
5
      "!**/fixtures/**",
6
      "!dist",
7
      "!**/fixtures",
8
    ]
9
  }
10
}
```
#6989 85b1128 Thanks @arendjr! - Fixed minor inconsistencies in how files.includes was being handled.

Previously, Biome sometimes failed to properly ignore the contents of a folder if you didn’t specify the /** at the end of a glob pattern. This was unfortunate, because it meant we still had to traverse the folder and then apply the glob to every entry inside it.

This is no longer an issue and we now recommend to ignore folders without using the /** suffix.
#7118 a78e878 Thanks @avshalomt2! - Added support for .graphqls files. Biome can now format and lint GraphQL files that have the extension .graphqls

#6159 f02a296 Thanks @bavalpey! - Added a new option to Biome’s JavaScript formatter, javascript.formatter.operatorLinebreak, to configure whether long lines should be broken before or after binary operators.

For example, the following configuration:

1
{
2
  formatter: {
3
    javascript: {
4
      operatorLinebreak: "before", // defaults to "after"
5
    },
6
  },
7
}

Will cause this JavaScript file:

1
const VERY_LONG_CONDITION_1234123412341234123412341234 = false;
2

3
if (
4
  VERY_LONG_CONDITION_1234123412341234123412341234 &&
5
  VERY_LONG_CONDITION_1234123412341234123412341234 &&
6
  VERY_LONG_CONDITION_1234123412341234123412341234 &&
7
  VERY_LONG_CONDITION_1234123412341234123412341234
8
) {
9
  console.log("DONE");
10
}

to be formatted like this:

1
const VERY_LONG_CONDITION_1234123412341234123412341234 = false;
2

3
if (
4
  VERY_LONG_CONDITION_1234123412341234123412341234 &&
5
  VERY_LONG_CONDITION_1234123412341234123412341234 &&
6
  VERY_LONG_CONDITION_1234123412341234123412341234 &&
7
  VERY_LONG_CONDITION_1234123412341234123412341234
8
) {
9
  console.log("DONE");
10
}

#7137 a653a0f Thanks @ematipico! - Promoted multiple lint rules from nursery to stable groups and renamed several rules for consistency.

Promoted rules

The following rules have been promoted from nursery to stable groups:

CSS
- Promoted noImportantStyles to the complexity group.
- Promoted noUnknownAtRules to the suspicious group.
GraphQL
- Promoted useGraphqlNamedOperations to the correctness group.
- Promoted useGraphqlNamingConvention to the style group.
JavaScript/TypeScript
- Promoted noExcessiveLinesPerFunction to the complexity group.
- Promoted noImplicitCoercions to the complexity group.
- Promoted useIndexOf to the complexity group.
- Promoted noGlobalDirnameFilename to the correctness group.
- Promoted noNestedComponentDefinitions to the correctness group.
- Promoted noProcessGlobal to the correctness group.
- Promoted noReactPropAssignments to the correctness group.
- Promoted noRestrictedElements to the correctness group.
- Promoted noSolidDestructuredProps to the correctness group.
- Promoted useJsonImportAttributes to the correctness group.
- Promoted useParseIntRadix to the correctness group.
- Promoted useSingleJsDocAsterisk to the correctness group.
- Promoted useUniqueElementIds to the correctness group.
- Promoted noAwaitInLoops to the performance group.
- Promoted noUnwantedPolyfillio to the performance group.
- Promoted useGoogleFontPreconnect to the performance group.
- Promoted useSolidForComponent to the performance group.
- Promoted noMagicNumbers to the style group.
- Promoted useConsistentObjectDefinitions to the style group.
- Promoted useExportsLast to the style group.
- Promoted useGroupedAccessorPairs to the style group.
- Promoted useNumericSeparators to the style group.
- Promoted useObjectSpread to the style group.
- Promoted useReadonlyClassProperties to the style group.
- Promoted useSymbolDescription to the style group.
- Promoted useUnifiedTypeSignatures to the style group.
- Promoted noBitwiseOperators to the suspicious group.
- Promoted noConstantBinaryExpressions to the suspicious group.
- Promoted noTsIgnore to the suspicious group.
- Promoted noUnassignedVariables to the suspicious group.
- Promoted noUselessRegexBackrefs to the suspicious group.
- Promoted noUselessEscapeInString to the suspicious group.
- Promoted useIterableCallbackReturn to the suspicious group.
- Promoted useStaticResponseMethods to the suspicious group.
Renamed rules

The following rules have been renamed during promotion. The migration tool will automatically update your configuration:
- Renamed noAwaitInLoop to noAwaitInLoops.
- Renamed noConstantBinaryExpression to noConstantBinaryExpressions.
- Renamed noDestructuredProps to noSolidDestructuredProps.
- Renamed noImplicitCoercion to noImplicitCoercions.
- Renamed noReactPropAssign to noReactPropAssignments.
- Renamed noUnknownAtRule to noUnknownAtRules.
- Renamed noUselessBackrefInRegex to noUselessRegexBackrefs.
- Renamed useAdjacentGetterSetter to useGroupedAccessorPairs.
- Renamed useConsistentObjectDefinition to useConsistentObjectDefinitions.
- Renamed useConsistentResponse to useStaticResponseMethods.
- Renamed useForComponent to useSolidForComponent.
- Renamed useJsonImportAttribute to useJsonImportAttributes.
- Renamed useNamedOperation to useGraphqlNamedOperations.
- Renamed useNamingConvention to useGraphqlNamingConvention.
- Renamed useUnifiedTypeSignature to useUnifiedTypeSignatures.
Configuration files using the old rule names will need to be updated. Use the migration tool to automatically update your configuration:
Terminal window
```
1
biome migrate --write
```
#7159 df3afdf Thanks @ematipico! - Added the new rule noBiomeFirstException. This rule prevents the incorrect usage of patterns inside files.includes.

This rule catches if the first element of the array contains !. This mistake will cause Biome to analyze no files:
biome.json
```
1
{
2
  files: {
3
    includes: ["!dist/**"], // this is an error
4
  },
5
}
```
#6923 0589f08 Thanks @ptkagori! - Added Qwik Domain to Biome

This release introduces **Qwik domain support ** in Biome, enabling Qwik developers to use Biome as a linter and formatter for their projects.
- Added the Qwik domain infrastructure to Biome.
- Enabled the following rules for Qwik:
  - useJsxKeyInIterable
  - noReactSpecificProps
#6989 85b1128 Thanks @arendjr! - Fixed #6965: Implemented smarter scanner for project rules.

Previously, if project rules were enabled, Biome’s scanner would scan all dependencies regardless of whether they were used by/reachable from source files or not. While this worked for a first version, it was far from optimal.

The new scanner first scans everything listed under the files.includes setting, and then descends into the dependencies that were discovered there, including transitive dependencies. This has three main advantages:
- Dependencies that are not reachable from your source files don’t get indexed.
- Dependencies that have multiple type definitions, such as those with separate definitions for CommonJS and ESM imports, only have the relevant definitions indexed.
- If vcs.useIgnoreFile is enabled, .gitignore gets respected as well. Assuming you have folders such as build/ or dist/ configured there, those will be automatically ignored by the scanner.
The change in the scanner also has a more nuanced impact: Previously, if you used files.includes to ignore a file in an included folder, the scanner would still index this file. Now the file is fully ignored, unless you import it.

As a user you should notice better scanner performance (if you have project rules enabled), and hopefully you need to worry less about configuring files.experimentalScannerIgnores. Eventually our goal is still to deprecate that setting, so if you’re using it today, we encourage you to see which ignores are still necessary there, and whether you can achieve the same effect by ignoring paths using files.includes instead.

None of these changes affect the scanner if no project rules are enabled.

#6731 d6a05b5 Thanks @ematipico! - The --reporter=summary has been greatly enhanced. It now shows the list of files that contains violations, the files shown are clickable and can be opened from the editor.

Below an example of the new version:

1
reporter/parse ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
2

3
  i The following files have parsing errors.
4

5
  - index.css
6

7
reporter/format ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
8

9
  i The following files needs to be formatted.
10

11
  - index.css
12
  - index.ts
13
  - main.ts
14

15
reporter/violations ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
16

17
  i Some lint rules or assist actions reported some violations.
18

19
  Rule Name                                        Diagnostics
20

21
  lint/correctness/noUnknownFunction               14 (2 error(s), 12 warning(s), 0 info(s))
22
  lint/suspicious/noImplicitAnyLet                 16 (12 error(s), 4 warning(s), 0 info(s))
23
  lint/suspicious/noDoubleEquals                   8 (8 error(s), 0 warning(s), 0 info(s))
24
  assist/source/organizeImports                    2 (2 error(s), 0 warning(s), 0 info(s))
25
  lint/suspicious/noRedeclare                      12 (12 error(s), 0 warning(s), 0 info(s))
26
  lint/suspicious/noDebugger                       8 (8 error(s), 0 warning(s), 0 info(s))

#6896 527db7f Thanks @ematipico! - Added new functions to the @biomejs/wasm-* packages:
- fileExists: returns whether the input file exists in the workspace.
- isPathIgnored: returns whether the input path is ignored.
- updateModuleGraph: updates the internal module graph of the input path.
- getModuleGraph: it returns a serialized version of the internal module graph.
- scanProject: scans the files and directories in the project to build the internal module graph.

#6398 d1a315d Thanks @josh-! - Added support for tracking stable results in user-provided React hooks that return objects to useExhaustiveDependencies to compliment existing support for array return values. For example:

1
{
2
  // rule options
3
  useExhaustiveDependencies: {
4
    level: "error",
5
    options: {
6
      hooks: [
7
        {
8
          name: "useCustomHook",
9
          stableResult: ["setMyState"],
10
        },
11
      ],
12
    },
13
  },
14
}

This will allow the following to be validated:

1
const { myState, setMyState } = useCustomHook();
2
const toggleMyState = useCallback(() => {
3
  setMyState(!myState);
4
}, [myState]); // Only `myState` needs to be specified here.

#7201 2afaa49 Thanks @Conaclos! - Implemented #7174. useConst no longer reports variables that are read before being written.

Previously, useConst reported uninitialised variables that were read in an inner function before being written, as shown in the following example:
```
1
let v;
2
function f() {
3
  return v;
4
}
5
v = 0;
```
This can produce false positives in the case where f is called before v has been written, as in the following code:
```
1
let v;
2
function f() {
3
  return v;
4
}
5
console.log(f()); // print `undefined`
6
v = 0;
```
Although this is an expected behavior of the original implementation, we consider it problematic since the rule’s fix is marked as safe. To avoid false positives like this, the rule now ignores the previous examples. However, this has the disadvantage of resulting in false negatives, such as not reporting the first example.

Patch Changes

#7156 137d111 Thanks @ematipico! - Fixed #7152. Now the rule noDuplicateFontNames correctly detects font names with spaces e.g. Liberation Mono. The diagnostic of the rule now points to the first instances of the repeated font.

The following example doesn’t trigger the rule anymore:
```
1
c {
2
  font-family:
3
    SF Mono,
4
    Liberation Mono,
5
    sans-serif;
6
}
7
d {
8
  font:
9
    1em SF Mono,
10
    Liberation Mono,
11
    sans-serif;
12
}
```

#6907 7331bb9 Thanks @ematipico! - Added a new experimental option that allows parsing of .html files that contain interpolation syntax.

1
{
2
  html: {
3
    // This is the new, experimental option.
4
    parser: {
5
      interpolation: true,
6
    },
7
  },
8
}

1
<h1>{{ $title }}</h1>

#7124 3f436b8 Thanks @Jayllyz! - Added the rule useMaxParams.

This rule enforces a maximum number of parameters for functions to improve code readability and maintainability. Functions with many parameters are difficult to read, understand, and maintain because they require memorizing parameter order and types.

1
// Invalid - too many parameters (default max: 4)
2
function processData(
3
  name,
4
  age,
5
  email,
6
  phone,
7
  address,
8
  city,
9
  country,
10
  zipCode,
11
) {
12
  // ...
13
}
14

15
// Valid - within parameter limit
16
function processData(userData) {
17
  const { name, age, email, phone, address, city, country, zipCode } =
18
    userData;
19
  // ...
20
}
21

22
function calculateSum(a, b, c) {
23
  return a + b + c;
24
}

#7161 1a14a59 Thanks @ematipico! - Fixed #7160. Now Biome correctly computes ignored files when using formatter.includes, linter.includes and assist.includes inside nested configurations that use "extends": "//".
#7081 a081bbe Thanks @Jayllyz! - Added the rule noNextAsyncClientComponent.

This rule prevents the use of async functions for client components in Next.js applications. Client components marked with “use client” directive should not be async as this can cause hydration mismatches, break component rendering lifecycle, and lead to unexpected behavior with React’s concurrent features.
```
1
"use client";
2

3
// Invalid - async client component
4
export default async function MyComponent() {
5
  return <div>Hello</div>;
6
}
7

8
// Valid - synchronous client component
9
export default function MyComponent() {
10
  return <div>Hello</div>;
11
}
```
#7171 5241690 Thanks @siketyan! - Fixed #7162: The noUndeclaredDependencies rule now considers a type-only import as a dev dependency.

For example, the following code is no longer reported:

package.json:
```
1
{
2
  "devDependencies": {
3
    "type-fest": "*"
4
  }
5
}
```
foo.ts:
```
1
import type { SetRequired } from "type-fest";
```
Note that you still need to declare the package in the devDependencies section in package.json.

2.2.2

Patch Changes

#7266 b270bb5 Thanks @ematipico! - Fixed an issue where Biome got stuck when analyzing some files. This is usually caused by a bug in the inference engine. Now Biome has some guards in place in case the number of types grows too much, and if that happens, a diagnostic is emitted and the inference is halted.
#7281 6436180 Thanks @ematipico! - Fixed an issue where the function scanProject wouldn’t work as expected.
#7285 1511d0c Thanks @rriski! - Partially fixed #6782: JSX node kinds are now supported in GritQL AST nodes.
#7249 dff85c0 Thanks @ematipico! - Fixed #748, where Biome Language Server didn’t show the unsafe fixes when requesting the quick fixes. Now all LSP editors will show also opt-in, unsafe fixes.
#7266 b270bb5 Thanks @ematipico! - Fixed #7020: Resolved an issue with analysing types of static member expressions involving unions. If the object type was a union that referenced nested unions, it would trigger an infinite loop as it tried to keep expanding nested unions, and the set of types would grow indefinitely.
#7209 679b70e Thanks @patrickshipe! - Resolved an overcorrection in useImportExtensions when importing explicit index files.

Imports that explicitly reference an index file are now preserved and no longer rewritten to nested index paths.

Example
```
1
// Before
2
      import "./sub/index";
3
      import "./sub/index/index.js";
4

5
// After
6
      import "./sub/index";
7
      import "./sub/index.js";
```
#7270 953f9c6 Thanks @arendjr! - Fixed #6172: Resolved an issue with inferring types for rest parameters. This issue caused rest-parameter types to be incorrect, and in some cases caused extreme performance regressions in files that contained many methods with rest-parameter definitions.
#7234 b7aa111 Thanks @JeetuSuthar! - Fixed #7233: The useIndexOf rule now correctly suggests using indexOf() instead of findIndex().

The diagnostic message was incorrectly recommending Array#findIndex() over Array#indexOf(), when it should recommend the opposite for simple equality checks.
#7283 0b07f45 Thanks @ematipico! - Fixed #7236. Now Biome correctly migrates JSONC configuration files when they are passed using --config-path.
#7239 1d643d8 Thanks @minht11! - Fixed an issue where Svelte globals ($state and so on) were not properly recognized inside .svelte.test.ts/js and .svelte.spec.ts/js files.
#7264 62fdbc8 Thanks @ematipico! - Fixed a regression where when using --log-kind-pretty wasn’t working anymore as expected.
#7244 660031b Thanks @JeetuSuthar! - Fixed #7225: The noExtraBooleanCast rule now preserves parentheses when removing Boolean calls inside negations.
```
1
// Before
2
!Boolean(b0 && b1);
3
// After
4
!(b0 && b1); // instead of !b0 && b1
```
#7298 46a8e93 Thanks @unvalley! - Fixed #6695: useNamingConvention now correctly reports TypeScript parameter properties with modifiers.

Previously, constructor parameter properties with modifiers like private or readonly were not checked against naming conventions. These properties are now treated consistently with regular class properties.

2.2.3

Patch Changes

#7353 4d2b719 Thanks @JeetuSuthar! - Fixed #7340: The linter now allows the navigation property for view-transition in CSS.

Previously, the linter incorrectly flagged navigation: auto as an unknown property. This fix adds navigation to the list of known CSS properties, following the CSS View Transitions spec.
#7275 560de1b Thanks @arendjr! - Fixed #7268: Files that are explicitly passed as CLI arguments are now correctly ignored if they reside in an ignored folder.
#7358 963a246 Thanks @ematipico! - Fixed #7085, now the rule noDescendingSpecificity correctly calculates the specificity of selectors when they are included inside a media query.
#7387 923674d Thanks @qraqras! - Fixed #7381, now the useOptionalChain rule recognizes optional chaining using Yoda expressions (e.g., undefined !== foo && foo.bar).
#7316 f9636d5 Thanks @Conaclos! - Fixed #7289. The rule useImportType now inlines import type into import { type } when the style option is set to inlineType.

Example:
```
1
import type { T } from "mod";
2
// becomes
3
import { type T } from "mod";
```
#7350 bb4d407 Thanks @siketyan! - Fixed #7261: two characters ・ (KATAKANA MIDDLE DOT, U+30FB) and ･ (HALFWIDTH KATAKANA MIDDLE DOT, U+FF65) are no longer considered as valid characters in identifiers. Property keys containing these character(s) are now preserved as string literals.
#7377 811f47b Thanks @ematipico! - Fixed a bug where the Biome Language Server didn’t correctly compute the diagnostics of a monorepo setting, caused by an incorrect handling of the project status.
#7245 fad34b9 Thanks @kedevked! - Added the new lint rule useConsistentArrowReturn.

This rule enforces a consistent return style for arrow functions.

Invalid
```
1
const f = () => {
2
  return 1;
3
};
```
This rule is a port of ESLint’s arrow-body-style rule.

#7370 e8032dd Thanks @fireairforce! - Support dynamic import defer and import source. The syntax looks like:

1
import.source("foo");
2
import.source("x", { with: { attr: "val" } });
3
import.defer("foo");
4
import.defer("x", { with: { attr: "val" } });

#7369 b1f8cbd Thanks @siketyan! - Range suppressions are now supported for Grit plugins.

For JavaScript, you can suppress a plugin as follows:

1
// biome-ignore-start lint/plugin/preferObjectSpread: reason
2
Object.assign({ foo: "bar" }, baz);
3
// biome-ignore-end lint/plugin/preferObjectSpread: reason

For CSS, you can suppress a plugin as follows:

1
body {
2
  /* biome-ignore-start lint/plugin/useLowercaseColors: reason */
3
  color: #fff;
4
  /* biome-ignore-end lint/plugin/useLowercaseColors: reason */
5
}

#7384 099507e Thanks @ematipico! - Reduced the severity of certain diagnostics emitted when Biome deserializes the configuration files. Now these diagnostics are emitted as Information severity, which means that they won’t interfere when running commands with --error-on-warnings
#7302 2af2380 Thanks @unvalley! - Fixed #7301: useReadonlyClassProperties now correctly skips JavaScript files.
#7288 94d85f8 Thanks @ThiefMaster! - Fixed #7286. Files are now formatted with JSX behavior when javascript.parser.jsxEverywhere is explicitly set.

Previously, this flag was only used for parsing, but not for formatting, which resulted in incorrect formatting of conditional expressions when JSX syntax is used in .js files.
#7311 62154b9 Thanks @qraqras! - Added the new nursery rule noUselessCatchBinding. This rule disallows unnecessary catch bindings.
```
1
try {
2
    // Do something
3
 } catch (unused) {}
4
 } catch {}
```

#7349 45c1dfe Thanks @ematipico! - Fixed #4298. Biome now correctly formats CSS declarations when it contains one single value:

1
.bar {
2
  --123456789012345678901234567890: var(--1234567890123456789012345678901234567);
3
  --123456789012345678901234567890: var(
4
    --1234567890123456789012345678901234567
5
  );
6
}

#7295 7638e84 Thanks @ematipico! - Fixed #7130. Removed the emission of a false-positive diagnostic. Biome no longer emits the following diagnostic:

1
lib/main.ts:1:5 suppressions/unused ━━━━━━━━━━━━━━━━━━━━━━━━━
2

3
  ⚠ Suppression comment has no effect because the tool is not enabled.
4

5
  > 1 │ /** biome-ignore-all assist/source/organizeImports: For the lib root file, we don't want to organize exports */
6
      │     ^^^^^^^^^^^^^^^^

#7377 811f47b Thanks @ematipico! - Fixed #7371 where the Biome Language Server didn’t correctly recompute the diagnostics when updating a nested configuration file.
#7348 ac27fc5 Thanks @ematipico! - Fixed #7079. Now the rule useSemanticElements doesn’t trigger components and custom elements.
#7389 ab06a7e Thanks @Conaclos! - Fixed #7344. useNamingConvention no longer reports interfaces defined in global declarations.

Interfaces declared in global declarations augment existing interfaces. Thus, they must be ignored.

In the following example, useNamingConvention reported HTMLElement. It is now ignored.
```
1
export {};
2
declare global {
3
  interface HTMLElement {
4
    foo(): void;
5
  }
6
}
```
#7315 4a2bd2f Thanks @vladimir-ivanov! - Fixed #7310: useReadonlyClassProperties correctly handles nested assignments, avoiding false positives when a class property is assigned within another assignment expression.

Example of code that previously triggered a false positive but is now correctly ignored:
```
1
class test {
2
  private thing: number = 0; // incorrectly flagged
3

4
  public incrementThing(): void {
5
    const temp = { x: 0 };
6
    temp.x = this.thing++;
7
  }
8
}
```

2.2.4

Patch Changes

#7453 aa8cea3 Thanks @arendjr! - Fixed #7242: Aliases specified in package.json’s imports section now support having multiple targets as part of an array.
#7454 ac17183 Thanks @arendjr! - Greatly improved performance of noImportCycles by eliminating allocations.

In one repository, the total runtime of Biome with only noImportCycles enabled went from ~23s down to ~4s.
#7447 7139aad Thanks @rriski! - Fixes #7446. The GritQL $... spread metavariable now correctly matches members in object literals, aligning its behavior with arrays and function calls.

#6710 98cf9af Thanks @arendjr! - Fixed #4723: Type inference now recognises index signatures and their accesses when they are being indexed as a string.

Example

1
type BagOfPromises = {
2
  // This is an index signature definition. It declares that instances of type
3
  // `BagOfPromises` can be indexed using arbitrary strings.
4
  [property: string]: Promise<void>;
5
};
6

7
let bag: BagOfPromises = {};
8
// Because `bag.iAmAPromise` is equivalent to `bag["iAmAPromise"]`, this is
9
// considered an access to the string index, and a Promise is expected.
10
bag.iAmAPromise;

#7415 d042f18 Thanks @qraqras! - Fixed #7212, now the useOptionalChain rule recognizes optional chaining using typeof (e.g., typeof foo !== 'undefined' && foo.bar).
#7419 576baf4 Thanks @Conaclos! - Fixed #7323. noUnusedPrivateClassMembers no longer reports as unused TypeScript private members if the rule encounters a computed access on this.

In the following example, member as previously reported as unused. It is no longer reported.
```
1
class TsBioo {
2
  private member: number;
3

4
  set_with_name(name: string, value: number) {
5
    this[name] = value;
6
  }
7
}
```
351bccd Thanks @ematipico! - Added the new nursery lint rule noJsxLiterals, which disallows the use of string literals inside JSX.

The rule catches these cases:
```
1
<>
2
  <div>test</div> {/* test is invalid */}
3
  <>test</>
4
  <div>
5
    {/* this string is invalid */}
6
    asdjfl test foo
7
  </div>
8
</>
```
#7406 b906112 Thanks @mdevils! - Fixed an issue (#6393) where the useHookAtTopLevel rule reported excessive diagnostics for nested hook calls.

The rule now reports only the offending top-level call site, not sub-hooks of composite hooks.
```
1
// Before: reported twice (useFoo and useBar).
2
function useFoo() {
3
  return useBar();
4
}
5
function Component() {
6
  if (cond) useFoo();
7
}
8
// After: reported once at the call to useFoo().
```
#7461 ea585a9 Thanks @arendjr! - Improved performance of noPrivateImports by eliminating allocations.

In one repository, the total runtime of Biome with only noPrivateImports enabled went from ~3.2s down to ~1.4s.
351bccd Thanks @ematipico! - Fixed #7411. The Biome Language Server had a regression where opening an editor with a file already open wouldn’t load the project settings correctly.
#7142 53ff5ae Thanks @Netail! - Added the new nursery rule noDuplicateDependencies, which verifies that no dependencies are duplicated between the bundledDependencies, bundleDependencies, dependencies, devDependencies, overrides, optionalDependencies, and peerDependencies sections.

For example, the following snippets will trigger the rule:
```
1
{
2
  "dependencies": {
3
    "foo": ""
4
  },
5
  "devDependencies": {
6
    "foo": ""
7
  }
8
}
```
```
1
{
2
  "dependencies": {
3
    "foo": ""
4
  },
5
  "optionalDependencies": {
6
    "foo": ""
7
  }
8
}
```
```
1
{
2
  "dependencies": {
3
    "foo": ""
4
  },
5
  "peerDependencies": {
6
    "foo": ""
7
  }
8
}
```
351bccd Thanks @ematipico! - Fixed #3824. Now the option CLI --color is correctly applied to logging too.

2.2.5

Patch Changes

#7597 5c3d542 Thanks @arendjr! - Fixed #6432: useImportExtensions now works correctly with aliased paths.
#7269 f18dac1 Thanks @CDGardner! - Fixed #6648, where Biome’s noUselessFragments contained inconsistencies with ESLint for fragments only containing text.

Previously, Biome would report that fragments with only text were unnecessary under the noUselessFragments rule. Further analysis of ESLint’s behavior towards these cases revealed that text-only fragments (<>A</a>, <React.Fragment>B</React.Fragment>, <RenamedFragment>B</RenamedFragment>) would not have noUselessFragments emitted for them.

On the Biome side, instances such as these would emit noUselessFragments, and applying the suggested fix would turn the text content into a proper JS string.
```
1
// Ended up as: - const t = "Text"
2
const t = <>Text</>
3

4
// Ended up as: - const e = t ? "Option A" : "Option B"
5
const e = t ? <>Option A</> : <>Option B</>
6

7
/* Ended up as:
8
  function someFunc() {
9
    return "Content desired to be a multi-line block of text."
10
  }
11
*/
12
function someFunc() {
13
  return <>
14
    Content desired to be a multi-line
15
    block of text.
16
  <>
17
}
```
The proposed update was to align Biome’s reaction to this rule with ESLint’s; the aforementioned examples will now be supported from Biome’s perspective, thus valid use of fragments.
```
1
// These instances are now valid and won't be called out by noUselessFragments.
2

3
const t = <>Text</>
4
const e = t ? <>Option A</> : <>Option B</>
5

6
function someFunc() {
7
  return <>
8
    Content desired to be a multi-line
9
    block of text.
10
  <>
11
}
```
#7498 002cded Thanks @siketyan! - Fixed #6893: The useExhaustiveDependencies rule now correctly adds a dependency that is captured in a shorthand object member. For example:
```
1
useEffect(() => {
2
  console.log({ firstId, secondId });
3
}, []);
```
is now correctly fixed to:
```
1
useEffect(() => {
2
  console.log({ firstId, secondId });
3
}, [firstId, secondId]);
```
#7509 1b61631 Thanks @siketyan! - Added a new lint rule noReactForwardRef, which detects usages of forwardRef that is no longer needed and deprecated in React 19.

For example:
```
1
export const Component = forwardRef(function Component(props, ref) {
2
  return <div ref={ref} />;
3
});
```
will be fixed to:
```
1
export const Component = function Component({ ref, ...props }) {
2
  return <div ref={ref} />;
3
};
```
Note that the rule provides an unsafe fix, which may break the code. Don’t forget to review the code after applying the fix.

#7520 3f06e19 Thanks @arendjr! - Added new nursery rule noDeprecatedImports to flag imports of deprecated symbols.

Invalid example

1
import { oldUtility } from "./utils.js";

1
/**
2
 * @deprecated
3
 */
4
export function oldUtility() {}

Valid examples

1
import { newUtility, oldUtility } from "./utils.js";

1
export function newUtility() {}
2

3
// @deprecated (this is not a JSDoc comment)
4
export function oldUtility() {}

#7457 9637f93 Thanks @kedevked! - Added style and requireForObjectLiteral options to the lint rule useConsistentArrowReturn.

This rule enforces a consistent return style for arrow functions. It can be configured with the following options:
- style: (default: asNeeded)
  - always: enforces that arrow functions always have a block body.
  - never: enforces that arrow functions never have a block body, when possible.
  - asNeeded: enforces that arrow functions have a block body only when necessary (e.g. for object literals).
style: "always"

Invalid:
```
1
const f = () => 1;
```
Valid:
```
1
const f = () => {
2
  return 1;
3
};
```
style: "never"

Invalid:
```
1
const f = () => {
2
  return 1;
3
};
```
Valid:
```
1
const f = () => 1;
```
style: "asNeeded"

Invalid:
```
1
const f = () => {
2
  return 1;
3
};
```
Valid:
```
1
const f = () => 1;
```
style: "asNeeded" and requireForObjectLiteral: true

Valid:
```
1
const f = () => {
2
  return { a: 1 };
3
};
```

#7510 527cec2 Thanks @rriski! - Implements #7339. GritQL patterns can now use native Biome AST nodes using their PascalCase names, in addition to the existing TreeSitter-compatible snake_case names.

1
engine biome(1.0)
2
language js(typescript,jsx)
3

4
or {
5
  // TreeSitter-compatible pattern
6
  if_statement(),
7

8
  // Native Biome AST node pattern
9
  JsIfStatement()
10
} as $stmt where {
11
  register_diagnostic(
12
    span=$stmt,
13
    message="Found an if statement"
14
  )
15
}

#7574 47907e7 Thanks @kedevked! - Fixed 7574. The diagnostic message for the rule useSolidForComponent now correctly emphasizes <For /> and provides a working hyperlink to the Solid documentation.
#7497 bd70f40 Thanks @siketyan! - Fixed #7320: The useConsistentCurlyBraces rule now correctly detects a string literal including " inside a JSX attribute value.
#7522 1af9931 Thanks @Netail! - Added extra references to external rules to improve migration for the following rules: noUselessFragments & noNestedComponentDefinitions
#7597 5c3d542 Thanks @arendjr! - Fixed an issue where package.json manifests would not be correctly discovered when evaluating files in the same directory.
#7565 38d2098 Thanks @siketyan! - The resolver can now correctly resolve .ts, .tsx, .d.ts, .js files by .js extension if exists, based on the file extension substitution in TypeScript.

For example, the linter can now detect the floating promise in the following situation, if you have enabled the noFloatingPromises rule.

foo.ts
```
1
export async function doSomething(): Promise<void> {}
```
bar.ts
```
1
import { doSomething } from "./foo.js"; // doesn't exist actually, but it is resolved to `foo.ts`
2

3
doSomething(); // floating promise!
```

#7542 cadad2c Thanks @mdevils! - Added the rule noVueDuplicateKeys, which prevents duplicate keys in Vue component definitions.

This rule prevents the use of duplicate keys across different Vue component options such as props, data, computed, methods, and setup. Even if keys don’t conflict in the script tag, they may cause issues in the template since Vue allows direct access to these keys.

Invalid examples

1
<script>
2
export default {
3
  props: ["foo"],
4
  data() {
5
    return {
6
      foo: "bar",
7
    };
8
  },
9
};
10
</script>

1
<script>
2
export default {
3
  data() {
4
    return {
5
      message: "hello",
6
    };
7
  },
8
  methods: {
9
    message() {
10
      console.log("duplicate key");
11
    },
12
  },
13
};
14
</script>

1
<script>
2
export default {
3
  computed: {
4
    count() {
5
      return this.value * 2;
6
    },
7
  },
8
  methods: {
9
    count() {
10
      this.value++;
11
    },
12
  },
13
};
14
</script>

Valid examples

1
<script>
2
export default {
3
  props: ["foo"],
4
  data() {
5
    return {
6
      bar: "baz",
7
    };
8
  },
9
  methods: {
10
    handleClick() {
11
      console.log("unique key");
12
    },
13
  },
14
};
15
</script>

1
<script>
2
export default {
3
  computed: {
4
    displayMessage() {
5
      return this.message.toUpperCase();
6
    },
7
  },
8
  methods: {
9
    clearMessage() {
10
      this.message = "";
11
    },
12
  },
13
};
14
</script>

#7546 a683acc Thanks @siketyan! - Internal data for Unicode strings have been updated to Unicode 17.0.
#7497 bd70f40 Thanks @siketyan! - Fixed #7256: The useConsistentCurlyBraces rule now correctly ignores a string literal with braces that contains only whitespaces. Previously, literals that contains single whitespace were only allowed.
#7565 38d2098 Thanks @siketyan! - The useImportExtensions rule now correctly detects imports with an invalid extension. For example, importing .ts file with .js extension is flagged by default. If you are using TypeScript with neither the allowImportingTsExtensions option nor the rewriteRelativeImportExtensions option, it’s recommended to turn on the forceJsExtensions option of the rule.
#7581 8653921 Thanks @lucasweng! - Fixed #7470: solved a false positive for noDuplicateProperties. Previously, declarations in @container and @starting-style at-rules were incorrectly flagged as duplicates of identical declarations at the root selector.

For example, the linter no longer flags the display declaration in @container or the opacity declaration in @starting-style.
```
1
a {
2
  display: block;
3
  @container (min-width: 600px) {
4
    display: none;
5
  }
6
}
7

8
[popover]:popover-open {
9
  opacity: 1;
10
  @starting-style {
11
    opacity: 0;
12
  }
13
}
```
#7529 fea905f Thanks @qraqras! - Fixed #7517: the useOptionalChain rule no longer suggests changes for typeof checks on global objects.
```
1
// ok
2
typeof window !== "undefined" && window.location;
```
#7476 c015765 Thanks @ematipico! - Fixed a bug where the suppression action for noPositiveTabindex didn’t place the suppression comment in the correct position.
#7511 a0039fd Thanks @arendjr! - Added nursery rule noUnusedExpressions to flag expressions used as a statement that is neither an assignment nor a function call.

Invalid examples
```
1
f; // intended to call `f()` instead
```
```
1
function foo() {
2
  0; // intended to `return 0` instead
3
}
```
Valid examples
```
1
f();
```
```
1
function foo() {
2
  return 0;
3
}
```
#7564 40e515f Thanks @turbocrime! - Fixed #6617: improved useIterableCallbackReturn to correctly handle arrow functions with a single-expression void body.

Now the following code doesn’t trigger the rule anymore:
```
1
[].forEach(() => void null);
```

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

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.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.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.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.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.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.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.6 Latest

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.

All versions since 2.0.6

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Invalid example

Valid examples

Patch Changes

Invalid example

Valid examples

Patch Changes

Minor Changes

Promoted rules

CSS

GraphQL

JavaScript/TypeScript

Renamed rules

Patch Changes

Patch Changes

Example

Patch Changes

Invalid

Patch Changes

Example

Patch Changes

Invalid example

Valid examples

style: "always"

style: "never"

style: "asNeeded"

style: "asNeeded" and requireForObjectLiteral: true

Invalid examples

Valid examples

Invalid examples

Valid examples

Patch Changes

Example

Invalid

Valid

Patch Changes

Minor Changes

Example

Example

Example

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

2.3.6 Latest

Patch Changes

Invalid

Valid

`style: "always"`

`style: "never"`

`style: "asNeeded"`

`style: "asNeeded"` and `requireForObjectLiteral: true`