All versions since 2.2.2

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 Latest

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
}
```

All versions since 2.2.2

2.2.2

Patch Changes

Example

2.2.3 Latest

Patch Changes

Invalid