All versions since 2.4.4

2.4.4

Patch Changes

#9150 6946835 Thanks @dyc3! - Fixed #9138: Astro files containing --- in HTML content (e.g., <h1>---Hi</h1>) are now parsed correctly, both when a frontmatter block is present and when there is no frontmatter at all.
#9150 aa6f837 Thanks @dyc3! - Fixed #9138: The HTML parser incorrectly failing to parse bracket characters ([ and ]) in text content (e.g. <div>[Foo]</div>).
#9151 c0d4b0c Thanks @dyc3! - Fixed parsing of Svelte directive keywords (use, style) when used as plain text content in HTML/Svelte files. Previously, <p>use JavaScript</p> or <p>style it</p> would incorrectly produce a bogus element instead of proper text content.
#9162 7f1e060 Thanks @dyc3! - Fixed #9161: The Vue parser now correctly handles colon attributes like xlink:href and xmlns:xlink by parsing them as single attributes instead of splitting them into separate tokens.
#9164 458211b Thanks @dyc3! - Fixed #9161: The noAssignInExpressions rule no longer flags assignments in Vue v-on directives (e.g., @click="counter += 1"). Assignments in event handlers are idiomatic Vue patterns and are now skipped by the rule.

2.4.5

Patch Changes

#9185 e43e730 Thanks @dyc3! - Added the nursery rule useVueScopedStyles for Vue SFCs. This rule enforces that <style> blocks have the scoped attribute (or module for CSS Modules), preventing style leakage and conflicts between components.
#9184 49c8fde Thanks @chocky335! - Improved plugin performance by batching all plugins into a single syntax visitor with a kind-to-plugin lookup map, reducing per-node dispatch overhead from O(N) to O(1) where N is the number of plugins.
#9283 071c700 Thanks @dyc3! - Fixed noUndeclaredVariables erroneously flagging functions and variables defined in the <script setup> section of Vue SFCs.
#9221 4612133 Thanks @ematipico! - Fixed an issue where the JSON reporter didn’t contain the duration of the command.
#9294 1805c8f Thanks @Netail! - Extra rule source reference. biome migrate eslint should do a bit better detecting rules in your eslint configurations.
#9178 101b3bb Thanks @Bertie690! - Fixed #9172 and #9168: Biome now considers more constructs as valid test assertions.

Previously, assert, expectTypeOf and assertType were not recognized as valid assertions by Biome’s linting rules, producing false positives in lint/nursery/useExpect and other similar rules.

Now, these rules will no longer produce errors in test cases that used these constructs instead of expect:
```
1
import { expectTypeOf, assert, assertType } from "vitest";
2

3
const myStr = "Hello from vitest!";
4
it("should be a string", () => {
5
  expectTypeOf(myStr).toBeString();
6
});
7
test("should still be a string", () => {
8
  assertType<string>(myStr);
9
});
10
it.todo("should still still be a string", () => {
11
  assert(typeof myStr === "string");
12
});
```
#9173 32dad2d Thanks @dyc3! - Added parsing support for Svelte’s new comments-in-tags feature.

The HTML parser will now accept JS style comments in tags in Svelte files.
```
1
<button
2
  // single-line comment
3
  onclick={doTheThing}
4
>click me</button>
5

6
<div
7
  /* block comment */
8
  class="foo"
9
>text</div>
```
#8952 1d2ca15 Thanks @pkallos! - Added the nursery rule useNullishCoalescing. This rule suggests using the nullish coalescing operator (??) instead of logical OR (||) when the left operand may be nullish. This prevents bugs where falsy values like 0, '', or false are incorrectly treated as missing. Addresses #8043
```
1
// Invalid
2
declare const x: string | null;
3
const value = x || "default";
4

5
// Valid
6
const value = x ?? "default";
```
#9243 1992a85 Thanks @Netail! - Fixed #7813: improved the diagnostic of the rule useExhaustiveDependencies. The diagnostic now shows the name of the variable to add to the dependency array.

#9063 3d0648f Thanks @taga3s! - Added the nursery rule noVueRefAsOperand. This rule disallows cases where a ref is used as an operand.

The following code is now flagged:

1
import { ref } from "vue";
2

3
const count = ref(0);
4
count++; // Should be: count.value++

1
import { ref } from "vue";
2

3
const ok = ref(false);
4
if (ok) {
5
  // Should be: if (ok.value)
6
  //
7
}

#9273 f239e20 Thanks @denbezrukov! - Fixed #9253: parsing of @container scroll-state(...) queries.

1
@container scroll-state(scrolled: bottom) {
2
}
3
@container scroll-state(stuck) {
4
}
5
@container scroll-state(not (stuck)) {
6
}
7
@container scroll-state((stuck) and (scrolled: bottom)) {
8
}
9
@container scroll-state((stuck) or (snapped: x)) {
10
}
11
@container main-layout scroll-state(not ((stuck) and (scrolled: bottom))) {
12
}

#9259 96939c0 Thanks @ematipico! - Fixed CSS formatter incorrectly collapsing selectors when a BOM (Byte Order Mark) character is present at the start of the file. The formatter now correctly preserves line breaks between comments and selectors in BOM-prefixed CSS files, matching Prettier’s behavior.
#9251 59e33fb Thanks @ematipico! - Fixed #9249: The CSS formatter no longer incorrectly breaks ratio values (like 1 / -1) across lines when followed by comments.
#9284 ec3a17f Thanks @denbezrukov! - Fixed #9253: removed false-positive diagnostics for valid @container/@supports general-enclosed queries.
```
1
@container scroll-state(scrolled: bottom) {
2
}
3
@supports foo(bar: baz) {
4
}
```
#9215 b2619a1 Thanks @FrederickStempfle! - Fixed #9189: biome ci in GitHub Actions now correctly disables colors so that ::error/::warning workflow commands are not wrapped in ANSI escape codes.
#9256 65ae4c1 Thanks @ematipico! - Fixed JSON reporter escaping of special characters in diagnostic messages. The JSON reporter now properly escapes double quotes, backslashes, and control characters in error messages and advice text, preventing invalid JSON output when diagnostics contain these characters.
#9223 5b9da81 Thanks @ematipico! - Fixed an issue where the JSON reporter didn’t write output to a file when --reporter-file was specified. The output is now correctly written to the specified file instead of always going to stdout.
#9154 c487e54 Thanks @abossenbroek! - Fixed #9115: The noPlaywrightMissingAwait rule no longer produces false positives on jest-dom matchers like toBeVisible, toBeChecked, toHaveAttribute, etc. For matchers shared between Playwright and jest-dom, the rule now checks whether expect()’s argument is a Playwright locator or page object before flagging. Added semantic variable resolution so that extracted Playwright locators (e.g. const loc = page.locator('.item'); expect(loc).toBeVisible()) are still correctly flagged.
#9269 33e5cdf Thanks @dyc3! - Fixed a false positive where noUndeclaredVariables reported bindings from Vue <script setup> as undeclared when used in <template>.

This change ensures embedded bindings collected from script snippets (like imports and defineModel results) are respected by the rule.
#9267 2c2e060 Thanks @ematipico! - Fixed #9143 and #8849: The noUnresolvedImports rule no longer reports false positives for several common patterns:
- node:fs, node:path, node:url, and other Node.js built-in modules with the node: prefix are now accepted.
- Packages that declare their TypeScript entry point via "typings" (instead of "types") in package.json now resolve correctly.
- Named imports from aliased re-export chains (e.g. export { x as y } from "...") are now resolved correctly through the alias.
- Namespace re-exports (e.g. export * as Ns from "...") are now recognized as own exports of the barrel module.
#9254 f7bf12b Thanks @ematipico! - Fixed #8842: The CSS formatter now correctly formats @container scroll-state() without adding an unwanted space between the function name and opening parenthesis.
#9211 2d0b8e6 Thanks @ematipico! - Fixed #7905. Improved the accuracy of type-aware lint rules when analyzing re-exported functions and values.

Previously, when a binding was imported from another module, its type was not correctly inferred during the type analysis phase. This caused type-aware lint rules to fail to detect issues when working with re-exported imports.

The following rules now correctly handle re-exported imports:
- useAwaitThenable
- noFloatingPromises
- noMisusedPromises
- useArraySortCompare
Example of now-working detection:
getValue.ts
```
1
export async function getValue(): Promise<number> {
2
  return 42;
3
}
4

5
// reexport.ts
6
export { getValue } from "./getValue";
7

8
// index.ts
9
import { getValue } from "./reexport";
10

11
// Previously: no diagnostic (type was unknown)
12
// Now: correctly detects that getValue() returns a Promise
13
await getValue(); // Valid - properly awaited
14
getValue(); // Diagnostic - floating promise
```
#8934 b49707c Thanks @tim-we! - Fixed #8265: Biome now correctly detects test framework calls that use three arguments (label, options, callback) (e.g., describe("foo", { retry: 2 }, () => {})). This fixes both formatting and the noDuplicateTestHooks lint rule for test frameworks like Vitest.
#9191 688fd34 Thanks @dyc3! - Fixed #9180: fixed a panic caused by an interaction between noRedundantUseStrict and the formatter
#9048 9bbdf4d Thanks @ff1451! - Added the nursery rule useNamedCaptureGroup. The rule enforces using named capture groups in regular expressions instead of numbered ones. It supports both regex literals and RegExp constructor calls.
```
1
// Invalid: unnamed capture group
2
/(foo)/;
3
new RegExp("(foo)");
4

5
// Valid: named capture group
6
/(?<id>foo)/;
7
new RegExp("(?<id>foo)");
```
#9255 9b6685b Thanks @ematipico! - Fixed #9234, where some nursery rules panicked when they were configured with the option level without the corresponding options.
#8968 a2b4494 Thanks @LouisLau-art! - Fixed #8812: lint/suspicious/noArrayIndexKey will now report index usage anywhere in JSX key template or binary expressions, not only in the last visited identifier.
#9266 84935a4 Thanks @dyc3! - Fixed #9250: noVueDuplicateKeys will no longer flag keys under watch, preventing false positives.
#9056 1f2fe2e Thanks @ruidosujeira! - Added the nursery rule useArraySome to prefer .some() over verbose existence checks like filter(...).length > 0 and findIndex(...) !== -1, with suggestions for find/findLast existence checks. This also applies to ES2025 iterator helpers such as Iterator.prototype.find.
#9163 f87acf6 Thanks @JUSTIVE! - Added graphql to valid embedded graphql template tags inside JavaScript files, when the feature javascript.experimentalEmbeddedSnippetsEnabled is enabled. This allows proper support for graphql tags used in RelayJS.

Now, code snippets like the following are correctly formatted and limited:
```
1
import { graphql } from "react-relay";
2

3
const query = graphql`
4
  query {
5
    user(id: 1) {
6
      id
7
      name
8
    }
9
  }
10
`;
```
#8773 6b01778 Thanks @xcb3d! - Added the new nursery rule useUnicodeRegex.

The rule enforces the use of the u or v flag for regular expressions. This ensures proper handling of Unicode characters like emoji.
```
1
// Invalid
2
/foo/;
3
new RegExp("foo", "gi");
4

5
// Valid
6
/foo/u;
7
new RegExp("foo", "giu");
```

2.4.6

Patch Changes

#9305 40869b5 Thanks @ematipico! - Fixed #4946: noUnreachable no longer reports code inside finally blocks as unreachable when there is a break, continue, or return in the corresponding try body.
#9303 464910c Thanks @ematipico! - Fixed #2786: The formatter no longer produces different output on subsequent runs when a case clause has a trailing line comment followed by a single block statement.
#9324 6294aa2 Thanks @arendjr! - Fixed #7730: useAnchorContent now recognises SolidJS’s innerHTML the same way as React’s dangerouslySetInnerHTML.
#9298 1003229 Thanks @Netail! - Fixed #9296, so comments are moved along with the attributes in the useSortedAttributes assist rule code fix.
#9329 855b451 Thanks @dyc3! - Improved performance of noEmptyBlockStatements. The rule is now smarter about short-circuiting its logic.
#9326 85dfe9b Thanks @dyc3! - Improved performance for noImportCycles by explicitly excluding node_modules from the cycle detection. The performance improvement is directly proportional to how big your dependency tree is.
#9323 d5ee469 Thanks @ematipico! - Fixed #9217 and biomejs/biome-vscode#959, where the Biome language server didn’t correctly resolve the editor setting configurationPath when the provided value is a relative path.
#9302 86fbc70 Thanks @sepagian! - Fixed #9300: Lowercase component member expressions like <form.Field> in Svelte and Astro files are now correctly formatted.
```
1
<form .Field></form.Field>
2
<form.Field></form.Field>
```

2.4.7 Latest

Patch Changes

#9318 3ac98eb Thanks @ematipico! - Added new nursery lint rule useBaseline for CSS. The rule reports when CSS properties, property values, at-rules, media conditions, functions, or pseudo-selectors are not part of the configured Baseline tier.

For example, at the time of writing, the rule will trigger for the use of accent-color because it has limited availability:
```
1
a {
2
  accent-color: bar;
3
}
```
#9272 2de8362 Thanks @terror! - Added the nursery rule useImportsFirst that enforces all import statements appear before any non-import statements in a module. Inspired by the eslint-plugin-import import/first rule.
```
1
// Invalid
2
import { foo } from "foo";
3
const bar = 1;
4
import { baz } from "baz"; // ← flagged
5

6
// Valid
7
import { foo } from "foo";
8
import { baz } from "baz";
9
const bar = 1;
```
#9285 93ea495 Thanks @dyc3! - Fixed noUndeclaredVariables from erroneously flagging props only used in the template section in Vue SFCs
#9435 6c5a8f2 Thanks @siketyan! - Fixed #9432: Values referenced as a JSX element in Astro/Vue/Svelte templates are now correctly detected; noUnusedImports and useImportType rules no longer reports these values as false positives.
#9362 fc9ca4c Thanks @Netail! - Extra rule source references. biome migrate eslint should do a bit better detecting rules in your eslint configurations.
#9392 b881fea Thanks @g-ortuno! - Fixed biomejs/biome-vscode#959: LSP now correctly resolves project directory when configurationPath points to a configuration file outside the workspace.
#9420 a1c46af Thanks @ematipico! - Fixed #9385: noUselessEscapeInString no longer incorrectly flags valid CSS hex escapes (e.g. \e7bb) as useless. The rule now recognizes all hex digits (0-9, a-f, A-F) as valid escape characters in CSS strings.
#9416 f2581b8 Thanks @ematipico! - Fixed #9131, #9112, #9166: the formatter no longer crashes or produces corrupt output when a JS file with experimentalEmbeddedSnippetsEnabled contains non-embedded template literals alongside embedded ones (e.g. console.log(\test`)next tographql(`…`)`).
#9344 cb4d7d7 Thanks @ematipico! - Fixed #6921: noShadow no longer incorrectly flags destructured variable bindings in sibling scopes as shadowing. Object destructuring, array destructuring, nested patterns, and rest elements are now properly recognized as declarations.
#9360 bc5dd99 Thanks @ematipico! - Fixed #7125: The rule noShadow no longer incorrectly flags parameters in TypeScript constructor and method overload signatures.
#9371 29cac17 Thanks @ematipico! - Fixed #5279: Tabs in diagnostic diff output are now rendered at a consistent width across context and changed lines, fixing visual misalignment when source files use tab indentation.
#9043 61e2a02 Thanks @dyc3! - Fixed #8897: Biome now parses @utility names containing / when Tailwind directives are enabled.

#9354 930c858 Thanks @denbezrukov! - Improved CSS parser recovery for invalid unicode-range values that mix wildcard ranges with range intervals. For example, Biome now reports clearer diagnostics for invalid syntax like:

1
unicode-range: U+11???-2??;
2
unicode-range: U+11???-;

with diagnostics such as:

1
× Wildcard ranges cannot be combined with a range interval.
2
  > unicode-range: U+11???-2??;
3
                            ^
4

5
× Expected a codepoint but instead found ';'.
6
  > unicode-range: U+11???-;
7
                             ^

#9355 78e74a2 Thanks @SchahinRohani! - Fixed #9349: Biome now correctly handles Vue dynamic :alt and v-bind:alt bindings in useAltText, preventing false positives in .vue files.
#9369 b309dde Thanks @costajohnt! - Fixed #9210: useAnchorContent no longer reports an accessibility error for Astro Image components inside links when they provide non-empty alt text.
#9345 70c2d4e Thanks @ematipico! - Fixed #7214: useOptionalChain now detects optional chain patterns that don’t start at the beginning of a logical AND expression. For example, bar && foo && foo.length is now correctly flagged and fixed to bar && foo?.length.
#9311 78c4e9b Thanks @ruidosujeira! - Fixed #9245: the useSemanticElements rule no longer suggests <output> for role="status" and role="alert". The <output> element is only a relatedConcept of these roles, not a direct semantic equivalent. These roles are now excluded from suggestions, aligning with the intended behavior of the upstream prefer-tag-over-role rule.
#9363 b2ffb4a Thanks @ematipico! - Fixed #5212: useSemanticElements no longer reports a diagnostic when a semantic element already has its corresponding role attribute (e.g. <nav role="navigation">, <footer role="contentinfo">). These cases are now correctly left to noRedundantRoles.
#9364 1bb9edc Thanks @xvchris! - Fixed #9357. Improved the information emitted by some diagnostics.
#9434 bf12092 Thanks @siketyan! - Fixed #9433: noBlankTarget now correctly handles dynamic href attributes, such as <a href={company?.website} target="_blank">.
#9351 5046d2b Thanks @Netail! - Expanded the noNegationElse rule to cover the inequality & strict inequality operator.
#9353 2a29e0d Thanks @Conaclos! - Fixed #7583: organizeImports now sorts named specifiers inside bare exports and merges bare exports.
```
1
export { b, a };
2
export { c };
3
export { a, b, c };
```
Also, organizeImports now correctly adds a blank line between an import chunk and an export chunk.
```
1
import { A } from "package";
2

3
export { A };
```
#8658 bdcc934 Thanks @rksvc! - When the domains field is set in the configuration file, domains is now automatically enabled when Biome detects certain dependencies in package.json.
#9383 f5c8bf0 Thanks @ematipico! - Fixed #6606: The type inference engine now resolves Record<K, V> types, synthesizing them as object types with index signatures. This improves accuracy for type-aware lint rules such as noFloatingPromises, noMisusedPromises, useAwaitThenable, and useArraySortCompare when operating on Record-typed values.
#9359 701ddd3 Thanks @ematipico! - Fixed #7516: noUnusedImports no longer reports a false positive when a local variable shadows an imported type namespace that is still used in a type annotation.
#9473 50e93bd Thanks @ematipico! - Improved the detection of variables inside Astro files. Now the rule noUnusedVariables and others will trigger fewer false positives.
#9459 171b2ee Thanks @ematipico! - Fixed #9314. Now Biome doesn’t panic when useAriaPropsForRole is configured using an object.
#9465 c8918d6 Thanks @Netail! - Fixed #9464: Temporal is now correctly detected as a global.
#9367 722f0da Thanks @Netail! - Added the nursery rule noTopLevelLiterals. It requires the root-level value to be an array or object.

Invalid:
```
1
"just a string"
```
#9333 a294b89 Thanks @terror! - Fixed #9310. Now the HTML formatter doesn’t mangle elements that are followed by self-closing elements such as <br> or <img>.
#9391 4bffb66 Thanks @ematipico! - Slightly increased the performance of the CLI in projects that have more than ~2K files.
#9365 776cb64 Thanks @Netail! - Added the nursery rule noEmptyObjectKeys, which disallows the use of empty keys in JSON objects.

Invalid:
```
1
{
2
  "": "value"
3
}
```