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

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 Latest

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);
```

All versions since 2.2.2

2.2.2

Patch Changes

Example

2.2.3

Patch Changes

Invalid

2.2.4

Patch Changes

Example

2.2.5 Latest

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

All versions since 2.2.2

2.2.2

Patch Changes

Example

2.2.3

Patch Changes

Invalid

2.2.4

Patch Changes

Example

2.2.5 Latest

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

`style: "always"`

`style: "never"`

`style: "asNeeded"`

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