All versions since 2.4.10

All versions

2.4.10

Patch Changes

#8838 f3a6a6b Thanks @baeseokjae! - Added new lint nursery rule noImpliedEval.

The rule detects implied eval() usage through functions like setTimeout, setInterval, and setImmediate when called with string arguments.
```
1
// Invalid
2
setTimeout("alert('Hello');", 100);
3

4
// Valid
5
setTimeout(() => alert("Hello"), 100);
```
#9320 93c3b6c Thanks @taberoajorge! - Fixed #7664: noUnusedVariables no longer reports false positives for TypeScript namespace declarations that participate in declaration merging with an exported or used value declaration (const, function, or class) of the same name. The reverse direction is also handled: a value declaration merged with an exported namespace is no longer flagged.
#9630 1dd4a56 Thanks @raashish1601! - Fixed #9629: noNegationElse now keeps ternary branch comments attached to the correct branch when applying its fixer.
#9216 04243b0 Thanks @FrederickStempfle! - Fixed #9061: noProcessEnv now also detects process.env when process is imported from the "process" or "node:process" modules.

Previously, only the global process object was flagged:
```
1
import process from "node:process";
2
// This was not flagged, but now it is:
3
console.log(process.env.NODE_ENV);
```
#9692 61b7ec5 Thanks @mkosei! - Fixed Svelte #each destructuring parsing and formatting for nested patterns such as [key, { a, b }].
#9627 06a0f35 Thanks @ematipico! - Fixed #191: Improved the performance of how the Biome Language Server pulls code actions and diagnostics.

Before, code actions were pulled and computed all at once in one request. This approach couldn’t work in big files, and caused Biome to stale and have CPU usage spikes up to 100%.

Now, code actions are pulled and computed lazily, and Biome won’t choke anymore in big files.
#9643 5bfee36 Thanks @dyc3! - Fixed #9347: useVueValidVBind no longer reports valid object bindings like v-bind="props".
#9627 06a0f35 Thanks @ematipico! - Fixed assist diagnostics being invisible when using --diagnostic-level=error. Enforced assist violations (e.g. useSortedKeys) were filtered out before being promoted to errors, causing biome check to incorrectly return success.
#9695 9856a87 Thanks @dyc3! - Added the new nursery rule noUnsafePlusOperands, which reports + and += operations that use object-like, symbol, unknown, or never operands, or that mix number with bigint.
#9627 06a0f35 Thanks @ematipico! - Fixed duplicate parse errors in check and ci output. When a file had syntax errors, the same parse error was printed twice and the error count was inflated.
#9627 06a0f35 Thanks @ematipico! - Improved the performance of the commands lint and check when they are called with --write.
#9627 06a0f35 Thanks @ematipico! - Fixed --diagnostic-level not fully filtering diagnostics. Setting --diagnostic-level=error now correctly excludes warnings and infos from both the output and the summary counts.
#9623 13b3261 Thanks @ematipico! - Fixed #9258: --skip no longer causes suppressions/unused warnings for suppression comments targeting skipped rules or domains.
#9631 599dd04 Thanks @raashish1601! - Fixed #9625: experimentalEmbeddedSnippetsEnabled no longer crashes when a file mixes formatable CSS-in-JS templates with tagged templates that the embedded formatter can’t currently delegate, such as a styled-components interpolation returning `css```.

2.4.11 Latest

Patch Changes

#9350 4af4a3a Thanks @dyc3! - Added the new nursery rule useConsistentTestIt in the test domain. The rule enforces consistent use of either it or test for test functions in Jest/Vitest suites, with separate control for top-level tests and tests inside describe blocks.

Invalid:
```
1
test("should fly", () => {}); // Top-level test using 'test' flagged, convert to 'it'
2

3
describe("pig", () => {
4
  test("should fly", () => {}); // Test inside 'describe' using 'test' flagged, convert to 'it'
5
});
```
#9429 a2f3f7e Thanks @ematipico! - Added the new nursery lint rule useExplicitReturnType. It reports TypeScript functions and methods that omit an explicit return type.
```
1
function toString(x: any) {
2
  // rule triggered, it doesn't declare a return type
3
  return x.toString();
4
}
```
#9828 9e40844 Thanks @ematipico! - Fixed #9484: the formatter no longer panics when formatting files that contain graphql tagged template literals combined with parenthesized expressions.
#9886 e7c681e Thanks @ematipico! - Fixed an issue where, occasionally, some bindings and references were not properly tracked, causing false positives from noUnusedVariables and noUndeclaredVariables in Svelte, Vue, and Astro files.
#9760 5b16d18 Thanks @myx0m0p! - Fixed #4093: the noDelete rule no longer triggers for delete process.env.FOO, since delete is the documented way to remove environment variables in Node.js.
#9799 2af8efd Thanks @minseong0324! - Added the rule noMisleadingReturnType. The rule detects when a function’s return type annotation is wider than what the implementation actually returns.
```
1
// Flagged: `: string` is wider than `"loading" | "idle"`
2
function getStatus(b: boolean): string {
3
  if (b) return "loading";
4
  return "idle";
5
}
```
#9880 7f67749 Thanks @dyc3! - Improved the diagnostics for useFind to better explain the problem, why it matters, and how to fix it.
#9755 bff7bdb Thanks @ematipico! - Improved performance of fix-all operations (--write). Biome is now smarter when it runs lint rules and assist actions. First, it runs only rules that have code fixes, and then runs the rest of the rules.
#8651 aafca2d Thanks @siketyan! - Add a new lint rule useDisposables for JavaScript, which detects disposable objects assigned to variables without using or await using syntax. Disposable objects that implement the Disposable or AsyncDisposable interface are intended to be disposed of after use. Not disposing them can lead to resource or memory leaks, depending on the implementation.

Invalid:
```
1
function createDisposable(): Disposable {
2
  return {
3
    [Symbol.dispose]() {
4
      // do something
5
    },
6
  };
7
}
8

9
const disposable = createDisposable();
```
Valid:
```
1
function createDisposable(): Disposable {
2
  return {
3
    [Symbol.dispose]() {
4
      // do something
5
    },
6
  };
7
}
8

9
using disposable = createDisposable();
```
#9788 53b8e57 Thanks @MeGaNeKoS! - Fixed #7760: Added support for CSS scroll-driven animation timeline-range-name keyframe selectors (cover, contain, entry, exit, entry-crossing, exit-crossing). Biome no longer reports parse errors on keyframes like entry 0% { ... } or exit 100% { ... }.
#9728 5085424 Thanks @mkosei! - Fixed #9696: Astro frontmatter now correctly parses regular expression literals like /\d{4}/.
#9261 16b6c49 Thanks @ematipico! - Fixed #8409: CSS formatter now correctly places comments after the colon in property declarations.

Previously, comments that appeared after the colon in CSS property values were incorrectly moved before the property name:
```
1
[lang]:lang(ja) {
2
  /* system-ui,*/ font-family:
3
  font-family: /* system-ui,*/
4
    Hiragino Sans,
5
    sans-serif;
6
}
```
#9441 957ea4c Thanks @soconnor-seeq! - Fixed #1630: LSP project selection now prefers the most specific project root in nested workspaces.
#9878 de6210f Thanks @ematipico! - Fixed #9118: noUnusedImports no longer reports false positives for default imports used inside Svelte, Vue and Astro components.
#9879 ce7e2b7 Thanks @dyc3! - Fixed a parser diagnostic’s message when vue syntax is disabled so that it no longer references the non-existant html.parser.vue option. This option will become available in 2.5.
#9880 7f67749 Thanks @dyc3! - Improved the diagnostics for useRegexpExec to better explain the problem, why it matters, and how to fix it.
#9846 b7134d9 Thanks @ematipico! - Fixed #9140: Biome now parses Astro’s attribute shorthand inside .astro files. The following snippet no longer reports a parse error:
```
1
---
2
const items = ['a', 'b'];
3
---
4
<ul>
5
  {items.map((item) => <li {item}>row</li>)}
6
</ul>
```
#9790 67df09d Thanks @dyc3! - Fixed #9781: Trailing comments after a top-level biome-ignore-all format suppression are now preserved instead of being dropped. This applies to JavaScript, CSS, HTML, JSONC, GraphQL, and Grit files.
#9745 d87073e Thanks @ematipico! - Fixed #9741: the LSP server now correctly returns the organizeImports code action when the client requests it via source.organizeImports.biome in the only filter. Previously, editors with codeAction/resolve support (e.g. Zed) received an empty response because the action was serialized with the wrong kind (source.biome.organizeImports instead of source.organizeImports.biome).
#9880 7f67749 Thanks @dyc3! - Improved the diagnostics for useArraySome to better explain the problem, why it matters, and how to fix it.
#9795 1d09f0f Thanks @dyc3! - Relaxed useExplicitType for trivially inferrable types.

Type annotations can now be omitted when types are trivially inferrable from:
- Binary expressions (const sum = 1 + 1)
- Comparison expressions (const isEqual = 'a' === 'b', const isTest = process.env.NODE_ENV === 'test')
- Logical expressions (const and = true && false)
- Class instantiation (const date = new Date())
- Array literals (const arr = [1, 2, 3])
- Conditional expressions (const val = true ? 'yes' : 'no')
- Function calls (const num = Math.random())
- Parameter defaults - any expression is now allowed (const fn = (max = MAX_ATTEMPTS) => ...)
Comparison expressions always return boolean, so any operands are now allowed (including property access like process.env.NODE_ENV).

Parameters with default values no longer require type annotations, as TypeScript can infer the type from the default value (even when referencing variables).

Also removed the redundant any type validation from this rule. The any type is now only validated by the dedicated noExplicitAny rule, following the Single Responsibility Principle.
#9809 e8cad58 Thanks @Netail! - Added the new nursery rule useQwikLoaderLocation, which enforces that Qwik loader functions are declared in the correct location.
#9877 fc9d715 Thanks @ematipico! - Fixed #9136 and #9653: noUndeclaredVariables and noUnusedVariables no longer report false positives on several Svelte template constructs that declare or reference bindings in the host grammar:
- {#snippet name(params)} — the snippet name and its parameters (including object, array, rest, and nested destructuring) are now tracked.
- {@render name(args)} — the snippet name used at the render site is now resolved against the snippet declaration.
- {#each items as item, index (key)} — the item binding (plain identifier or destructured), the optional index, and the optional key expression are now tracked.
- {@const name = value} — the declared name is now tracked as a binding and the initializer is analyzed for undeclared references.
- {@debug a, b, c} — each debugged identifier is now analyzed and reported if undeclared.
- Shorthand attributes <img {src} /> — the curly-shorthand attribute is now analyzed as an expression, so undeclared references inside it are reported.
For example, the following template no longer triggers either rule:
```
1
<script>
2
let items = [];
3
let total = 0;
4
</script>
5

6
{#snippet figure(image)}
7
    <figure>
8
        <img src={image.src} alt={image.caption} />
9
        <figcaption>{image.caption}</figcaption>
10
    </figure>
11
{/snippet}
12

13
{#each items as item}
14
    {@const price = item.price}
15
    {@render figure(item)}
16
    <span>{price}</span>
17
{/each}
18

19
{@debug items, total}
```
#9869 78bce77 Thanks @Netail! - Updated noDuplicateFieldDefinitionNames to also flag duplicate fields within type extensions, interface extensions & input extensions.
#9739 0bc2198 Thanks @dyc3! - Fixed Grit queries that use native Biome AST node names with the native field names that are in our .ungram grammar files. Queries such as JsConditionalExpression(consequent = $cons, alternate = $alt) now compile successfully in biome search and grit plugins.
#9811 2dddca3 Thanks @dyc3! - Updated noImpliedEval to flag new Function() usages, as its a form of indirect eval, and to include no-new-func as a rule source.
#9870 ccf9770 Thanks @Netail! - Marked eslint-qwik-plugin’s unused-server as redundant since it was covered by noUnusedVariables.
#9701 1417c3b Thanks @dyc3! - Added the new nursery rule noUselessTypeConversion, which reports redundant primitive conversion patterns such as String(value) when value is already a string.
#9248 49f00a3 Thanks @pkallos! - useNullishCoalescing now also detects ternary expressions that check for null or undefined and suggests rewriting them with ??. A new ignoreTernaryTests option allows disabling this behavior.
#9863 6a44619 Thanks @ematipico! - Fixed #9690: biome check --write is now idempotent on HTML files that contain embedded <style> or <script> blocks. Previously, each run reported “Fixed 1 file” even when the file content did not actually change, because the embedded language formatter’s output was not re-indented to match the surrounding HTML block.