chore(deps): update dependency @biomejs/biome to v2.2.0 #42

renovate · 2025-07-08T14:07:06Z

This PR contains the following updates:

Package	Change	Age	Confidence
@biomejs/biome (source)	`2.0.6` -> `2.2.0`

Release Notes

biomejs/biome (@biomejs/biome)

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

Invalid example

<script>
export default {
  data: {
    $el: "",
    _foo: "bar",
  },
};
</script>

<script>
export default {
  computed: {
    $data() {
      return this.someData;
    },
  },
};
</script>

Valid examples

<script>
export default {
  data() {
    return {
      message: "Hello Vue!",
      count: 0,
    };
  },
};
</script>

<script>
export default {
  computed: {
    displayMessage() {
      return this.message;
    },
  },
};
</script>

#6941 734d708 Thanks @JamBalaya56562! - Added @eslint-react/no-nested-component-definitions as a rule source for noNestedComponentDefinitions. Now it will get picked up by biome migrate --eslint.
#6463 0a16d54 Thanks @JamBalaya56562! - Fixed a website link for the useComponentExportOnlyModules linter rule to point to the correct URL.
#6944 e53f2fe Thanks @sterliakov! - Fixed #6910: Biome now ignores type casts and assertions when evaluating numbers for noMagicNumbers rule.
#6991 476cd55 Thanks @denbezrukov! - Fixed #6973: Add support for parsing the :active-view-transition-type() pseudo-class
```
:active-view-transition-type(first second) {
}
```
#6992 0b1e194 Thanks @ematipico! - Added a new JSON rule called noQuickfixBiome, which disallow the use of code action quickfix.biome inside code editor settings.
#6943 249306d Thanks @JamBalaya56562! - Fixed @vitest/eslint-plugin source url.
#6947 4c7ed0f Thanks @JamBalaya56562! - Fixed ESLint migration for the rule prefer-for from eslint-plugin-solid to Biome's useForComponent.
#6976 72ebadc Thanks @siketyan! - Fixed #6692: The rules noUnusedVariables and noUnusedFunctionParameters no longer cause an infinite loop when the suggested name is not applicable (e.g. the suggested name is already declared in the scope).
#6990 333f5d0 Thanks @rvanlaarhoven! - Fixed the documentation URL for lint/correctness/noUnknownPseudoClass
#7000 4021165 Thanks @harxki! - Fixed #6795: noUnassignedVariables now correctly recognizes variables used in JSX ref attributes.
#7044 b091ddf Thanks @ematipico! - Fixed #6622, now the rule useSemanticElements works for JSX self-closing elements too.
#7014 c4864e8 Thanks @siketyan! - Fixed #6516: The biome migrate command no longer break the member list with trailing comments.

#6979 29cb6da Thanks @unvalley! - Fixed #6767: useSortedClasses now correctly removes leading and trailing whitespace in className.

Previously, trailing spaces in className were not fully removed.

// Think we have this code:
<div className="text-sm font-bold            " />

// Before: applied fix, but a trailing space was preserved
<div className="font-bold text-sm " />

// After: applied fix, trailing spaces removed
<div className="font-bold text-sm" />

#7055 ee4828d Thanks @dyc3! - Added the nursery rule useReactFunctionComponents. This rule enforces the preference to use function components instead of class components.

Valid:
```
function Foo() {
  return <div>Hello, world!</div>;
}
```
Invalid:
```
class Foo extends React.Component {
  render() {
    return <div>Hello, world!</div>;
  }
}
```
#6924 2d21be9 Thanks @ematipico! - Fixed #113, where the Biome Language Server didn't correctly update the diagnostics when the configuration file is modified in the editor. Now the diagnostics are correctly updated every time the configuration file is modified and saved.
#6931 e6b2380 Thanks @arendjr! - Fixed #6915: useHookAtTopLevel no longer hangs when rules call themselves recursively.
#7012 01c0ab4 Thanks @siketyan! - Fixed #5837: Invalid suppression comments such as biome-ignore-all-start or biome-ignore-all-end no longer causes a panic.
#6949 48462f8 Thanks @fireairforce! - Support parse import defer(which is a stage3 proposal). The syntax look like this:
```
import defer * as foo from "<specifier>";
```

#6938 5feb5a6 Thanks @vladimir-ivanov! - Fixed #6919 and #6920:
useReadonlyClassProperties now does checks for mutations in async class methods.

Example:

class Counter3 {
  private counter: number;
  async count() {
    this.counter = 1;
    const counterString = `${this.counter++}`;
  }
}

#6942 cfda528 Thanks @sterliakov! - Fixed #6939. Biome now understands this binding in classes outside of methods.

`v2.1.2`

Compare Source

Patch Changes

#6865 b35bf64 Thanks @denbezrukov! - Fix #6485: Handle multiple semicolons correctly in blocks (#6485)
```
div {
  box-sizing: border-box;
  color: red;
}
```
#6798 3579ffa Thanks @dyc3! - Fixed #6762, Biome now knows that ~/.config/zed/settings.json and ~/.config/Code/User/settings.json allows comments by default.
#6839 4cd62d8 Thanks @ematipico! - Fixed #6838, where the Biome File Watcher incorrectly watched and stored ignored files, causing possible memory leaks when those files were dynamically created (e.g. built files).
#6879 0059cd9 Thanks @denbezrukov! - Refactor: remove one level of indirection for CSS declarations with semicolon
Previously, accessing a declaration from a list required an extra step:
```
item
.as_any_css_declaration_with_semicolon()
.as_css_declaration_with_semicolon()
```
Now, it can be done directly with:
```
item.as_css_declaration_with_semicolon()
```
#6839 4cd62d8 Thanks @ematipico! - Fixed a bug where the Biome Language Server didn't correctly ignore specific files when vcs.useIgnoreFile is set to true.
#6884 5ff50f8 Thanks @arendjr! - Improved the performance of noImportCycles by ~30%.
#6903 241dd9e Thanks @arendjr! - Fixed #6829: Fixed a false positive reported by useImportExtensions when importing a .js file that had a matching .d.ts file in the same folder.
#6846 446112e Thanks @darricheng! - Fixed an issue where biome was using the wrong string quotes when the classes string has quotes, resulting in invalid code after applying the fix.
#6823 eebc48e Thanks @arendjr! - Improved #6172: Optimised the way function arguments are stored in Biome's type inference. This led to about 10% performance improvement in RedisCommander.d.ts and about 2% on @next/font type definitions.
#6878 3402976 Thanks @ematipico! - Fixed a bug where the Biome Language Server would apply an unsafe fix when using the code action quickfix.biome.

Now Biome no longer applies an unsafe code fix when using the code action quickfix.biome.

#6794 4d5fc0e Thanks @vladimir-ivanov! - Fixed #6719: The noInvalidUseBeforeDeclaration rule covers additional use cases.

Examples:

type Bar = { [BAR]: true };
const BAR = "bar";

interface Bar {
  child: { grandChild: { [BAR]: typeof BAR; enumFoo: EnumFoo } };
}
const BAR = "bar";
enum EnumFoo {
  BAR = "bar",
}

#6863 531e97e Thanks @dyc3! - Biome now considers whether the linter is enabled when figuring out how the project should be scanned. Resolves #6815.
#6832 bdbc2b1 Thanks @togami2864! - Fixed #6165: Fixed false negative in noUnusedPrivateClassMembers rule when checking member usage in classes
#6839 4cd62d8 Thanks @ematipico! - Fixed a bug where the root ignore file wasn't correctly loaded during the scanning phase, causing false positives and incorrect expectations among users.

Now, when using vcs.useIgnoreFile, the the globs specified in the ignore file from the project root will have the same semantics as the files.includes setting of the root configuration.

Refer to the relative web page to understand how they work.
#6898 5beb024 Thanks @arendjr! - Fixed #6891: Improved type inference for array indices.

Example:
```
const numbers: number[];
numbers[42]; // This now infers to `number | undefined`.
```
#6809 8192451 Thanks @arendjr! - Fixed #6796: Fixed a false positive that happened in noFloatingPromises when calling functions that were declared as part of for ... of syntax inside async functions.

Instead, the variables declared inside for ... of loops are now correctly
inferred if the expression being iterated evaluates to an Array (support for other iterables will follow later).

Invalid example
```
const txStatements: Array<(tx) => Promise<any>> = [];

db.transaction((tx: any) => {
  for (const stmt of txStatements) {
    // We correctly flag this resolves to a `Promise`:
    stmt(tx);
  }
});
```
Valid example
```
async function valid(db) {
  const txStatements: Array
```

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 force-pushed the renovate/biomejs-biome-2.x-lockfile branch from 597de0f to 8e97d2e Compare July 8, 2025 19:50

renovate bot changed the title ~~chore(deps): update dependency @biomejs/biome to v2.1.0~~ chore(deps): update dependency @biomejs/biome to v2.1.1 Jul 8, 2025

renovate bot force-pushed the renovate/biomejs-biome-2.x-lockfile branch from 8e97d2e to eeb2783 Compare July 17, 2025 17:48

renovate bot changed the title ~~chore(deps): update dependency @biomejs/biome to v2.1.1~~ chore(deps): update dependency @biomejs/biome to v2.1.2 Jul 17, 2025

renovate bot force-pushed the renovate/biomejs-biome-2.x-lockfile branch from eeb2783 to 6475940 Compare July 29, 2025 16:52

renovate bot changed the title ~~chore(deps): update dependency @biomejs/biome to v2.1.2~~ chore(deps): update dependency @biomejs/biome to v2.1.3 Jul 29, 2025

renovate bot force-pushed the renovate/biomejs-biome-2.x-lockfile branch from 6475940 to 3d2a8ab Compare August 7, 2025 17:35

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

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

5179991

renovate bot force-pushed the renovate/biomejs-biome-2.x-lockfile branch from 3d2a8ab to 5179991 Compare August 14, 2025 11:07

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

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

chore(deps): update dependency @biomejs/biome to v2.2.0 #42

chore(deps): update dependency @biomejs/biome to v2.2.0 #42

Uh oh!

renovate bot commented Jul 8, 2025 •

edited

Loading

Uh oh!

Uh oh!

chore(deps): update dependency @biomejs/biome to v2.2.0 #42

Are you sure you want to change the base?

chore(deps): update dependency @biomejs/biome to v2.2.0 #42

Uh oh!

Conversation

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

Uh oh!

Release Notes

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

Invalid example

Valid examples

v2.1.2

Patch Changes

Configuration

Uh oh!

Uh oh!

renovate bot commented Jul 8, 2025 •

edited

Loading

`v2.2.0`

`v2.1.4`

`v2.1.3`

`v2.1.2`