chore(deps): update dependency @biomejs/biome to v2.2.3 #29

renovate · 2025-07-29T15:12:27Z

This PR contains the following updates:

Package	Change	Age	Confidence
@biomejs/biome (source)	`2.1.2` -> `2.2.3`

Release Notes

biomejs/biome (@biomejs/biome)

`v2.2.3`

Compare Source

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:
```
import type { T } from "mod";
// becomes
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

const f = () => {
  return 1;
};

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:

import.source("foo");
import.source("x", { with: { attr: "val" } });
import.defer("foo");
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:

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

For CSS, you can suppress a plugin as follows:

body {
  /* biome-ignore-start lint/plugin/useLowercaseColors: reason */
  color: #fff;
  /* biome-ignore-end lint/plugin/useLowercaseColors: reason */
}

#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.
```
try {
    // Do something
- } catch (unused) {}
+ } catch {}
```

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

.bar {
-  --123456789012345678901234567890: var(--1234567890123456789012345678901234567);
+  --123456789012345678901234567890: var(
+    --1234567890123456789012345678901234567
+  );
}

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

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

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

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

#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.
```
export {};
declare global {
  interface HTMLElement {
    foo(): void;
  }
}
```
#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:
```
class test {
  private thing: number = 0; // incorrectly flagged

  public incrementThing(): void {
    const temp = { x: 0 };
    temp.x = this.thing++;
  }
}
```

`v2.2.2`

Compare Source

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

// Before
-      import "./sub/index";
+      import "./sub/index/index.js";

// After
-      import "./sub/index";
+      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.
```
// Before
!Boolean(b0 && b1);
// After
!(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.

`v2.2.0`

Compare Source

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.
```
{
  "options": {
    "patterns": [
      {
        "group": ["import-foo/*", "!import-foo/baz"],
        "message": "import-foo is deprecated, except for modules in import-foo/baz."
      }
    ]
  }
}
```
Invalid examples
```
import foo from "import-foo/foo";
import bar from "import-foo/bar";
```
Valid examples
```
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/.
```
{
  "options": {
    "patterns": [
      {
        "group": ["import-foo/*"],
        "importNamePattern": "[xyz]"
      }
    ]
  }
}
```
Invalid examples
```
import { x } from "import-foo/foo";
```
Valid examples
```
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/.
```
{
  "options": {
    "patterns": [
      {
        "group": ["import-foo/*"],
        "importNamePattern": "[xyz]",
        "invertImportNamePattern": true
      }
    ]
  }
}
```
Invalid examples
```
import { foo } from "import-foo/foo";
```
Valid examples
```
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
{
  "files": {
    "includes": [
-      "!dist/**",
-      "!**/fixtures/**",
+      "!dist",
+      "!**/fixtures",
    ]
  }
}
```
#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:

{
  formatter: {
    javascript: {
      operatorLinebreak: "before", // defaults to "after"
    },
  },
}

Will cause this JavaScript file:

const VERY_LONG_CONDITION_1234123412341234123412341234 = false;

if (
  VERY_LONG_CONDITION_1234123412341234123412341234 &&
  VERY_LONG_CONDITION_1234123412341234123412341234 &&
  VERY_LONG_CONDITION_1234123412341234123412341234 &&
  VERY_LONG_CONDITION_1234123412341234123412341234
) {
  console.log("DONE");
}

to be formatted like this:

const VERY_LONG_CONDITION_1234123412341234123412341234 = false;
if (
  VERY_LONG_CONDITION_1234123412341234123412341234 &&
  VERY_LONG_CONDITION_1234123412341234123412341234 &&
  VERY_LONG_CONDITION_1234123412341234123412341234 &&
  VERY_LONG_CONDITION_1234123412341234123412341234
) {
  console.log("DONE");
}

#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 noUselessStringEscapes to the suspicious group.
Promoted useConsistentIterableCallbackReturnValues 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:

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
{
  files: {
    includes: ["!dist/**"], // this is an error
  },
}
```
#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:

reporter/parse ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  i The following files have parsing errors.

  - index.css

reporter/format ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  i The following files needs to be formatted.

  - index.css
  - index.ts
  - main.ts

reporter/violations ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  i Some lint rules or assist actions reported some violations.

  Rule Name                                        Diagnostics

  lint/correctness/noUnknownFunction               14 (2 error(s), 12 warning(s), 0 info(s))
  lint/suspicious/noImplicitAnyLet                 16 (12 error(s), 4 warning(s), 0 info(s))
  lint/suspicious/noDoubleEquals                   8 (8 error(s), 0 warning(s), 0 info(s))
  assist/source/organizeImports                    2 (2 error(s), 0 warning(s), 0 info(s))
  lint/suspicious/noRedeclare                      12 (12 error(s), 0 warning(s), 0 info(s))
  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:

// biome.json
{
  // rule options
  useExhaustiveDependencies: {
    level: "error",
    options: {
      hooks: [
        {
          name: "useCustomHook",
          stableResult: ["setMyState"],
        },
      ],
    },
  },
}

This will allow the following to be validated:

const { myState, setMyState } = useCustomHook();
const toggleMyState = useCallback(() => {
  setMyState(!myState);
}, [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:
```
let v;
function f() {
  return v;
}
v = 0;
```
This can produce false positives in the case where f is called before v has been written, as in the following code:
```
let v;
function f() {
  return v;
}
console.log(f()); // print `undefined`
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:
```
c {
  font-family:
    SF Mono,
    Liberation Mono,
    sans-serif;
}
d {
  font:
    1em SF Mono,
    Liberation Mono,
    sans-serif;
}
```

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

// biome.json
{
  html: {
    // This is the new, experimental option.
    parser: {
      interpolation: true,
    },
  },
}

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

// Invalid - too many parameters (default max: 4)
function processData(
  name,
  age,
  email,
  phone,
  address,
  city,
  country,
  zipCode,
) {
  // ...
}

// Valid - within parameter limit
function processData(userData) {
  const { name, age, email, phone, address, city, country, zipCode } =
    userData;
  // ...
}

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

#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.
```
"use client";

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

// Valid - synchronous client component
export default function MyComponent() {
  return <div>Hello</div>;
}
```
#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:
```
{
  "devDependencies": {
    "type-fest": "*"
  }
}
```
foo.ts:
```
import type { SetRequired } from "type-fest";
```
Note that you still need to declare the package in the devDependencies section in package.json.

`v2.1.4`

Compare Source

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:
```
useVisibleTask$(() => {
  console.log("Component is visible");
});
```
Valid:
```
useTask$(() => {
  console.log("Task executed");
});
```
#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:
```
// Always truthy literal conditions
if (true) {
  console.log("always runs");
}
```
```
// Unnecessary condition on constrained string type
function foo(arg: "bar" | "baz") {
  if (arg) {
    // This check is unnecessary
  }
}
```
#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:
```
<img src="/image.png" />
<img src="https://example.com/image.png" />
<img src="/image.png" width="200" />
<img src="/image.png" height="200" />
```
Valid:
```
<img width="200" height="600" src="/static/images/portrait-01.webp" />
<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:
```
<a>Link</a>
```
```
<a target="_blank">External</a>
```
Valid:
```
<a href="/home">Home</a>
```
```
<a href="https://example.com" target="_blank">
  External
</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.
```
// Invalid - non-null assertion after optional chaining
obj?.prop!;
obj?.method()!;
obj?.[key]!;
obj?.prop!;

// Valid - proper optional chaining usage
obj?.prop;
obj?.method();
obj?.prop ?? defaultValue;
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:
```
{
  "linter": {
    "rules": {
      "nursery": {
        "noImportCycles": {
          "options": {
            "ignoreTypes": false
          }
        }
      }
    }
  }
}
```
#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:
```
<div class={classnames({ active: true, disabled: false })} />
```
Valid:
```
<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:
```
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:
```
// With default option (interface)
// ❌ Invalid
type Point = { x: number; y: number };

// ✅ Valid
interface Point {
  x: number;
  y: number;
}

// With option { style: "type" }
// ❌ Invalid
interface Point {
  x: number;
  y: number;
}

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

`v2.1.3`

Compare Source

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 # @biomejs/biome (like $el, $data, $props) and keys starting with _` in data properties, which can cause conflicts and unexpected behavior in Vue components.

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

renovate bot changed the title ~~chore(deps): update dependency @biomejs/biome to v2.1.3~~ chore(deps): update dependency @biomejs/biome to v2.1.4 Aug 7, 2025

renovate bot force-pushed the renovate/biomejs-biome-2.x branch 2 times, most recently from 7d89e0d to 63ff6be Compare August 14, 2025 11:09

renovate bot changed the title ~~chore(deps): update dependency @biomejs/biome to v2.1.4~~ chore(deps): update dependency @biomejs/biome to v2.2.0 Aug 14, 2025

renovate bot force-pushed the renovate/biomejs-biome-2.x branch from 63ff6be to 3f9f37f Compare August 23, 2025 13:02

renovate bot changed the title ~~chore(deps): update dependency @biomejs/biome to v2.2.0~~ chore(deps): update dependency @biomejs/biome to v2.2.2 Aug 23, 2025

chore(deps): update dependency @biomejs/biome to v2.2.3

b6f6fce

renovate bot force-pushed the renovate/biomejs-biome-2.x branch from 3f9f37f to b6f6fce Compare September 5, 2025 13:01

renovate bot changed the title ~~chore(deps): update dependency @biomejs/biome to v2.2.2~~ chore(deps): update dependency @biomejs/biome to v2.2.3 Sep 5, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

chore(deps): update dependency @biomejs/biome to v2.2.3 #29

chore(deps): update dependency @biomejs/biome to v2.2.3 #29

Uh oh!

renovate bot commented Jul 29, 2025 •

edited

Loading

Uh oh!

Uh oh!

chore(deps): update dependency @biomejs/biome to v2.2.3 #29

Are you sure you want to change the base?

chore(deps): update dependency @biomejs/biome to v2.2.3 #29

Uh oh!

Conversation

renovate bot commented Jul 29, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

v2.2.3

Patch Changes

Invalid

v2.2.2

Patch Changes

Example

v2.2.0

Minor Changes

Promoted rules

CSS

GraphQL

JavaScript/TypeScript

Renamed rules

Patch Changes

v2.1.4

Patch Changes

v2.1.3

Patch Changes

Configuration

Uh oh!

Uh oh!

renovate bot commented Jul 29, 2025 •

edited

Loading

`v2.2.3`

`v2.2.2`

`v2.2.0`

`v2.1.4`

`v2.1.3`