chore(deps): update @biomejs/biome to v2 #2063

renovate · 2025-06-17T18:29:38Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@biomejs/biome (source)	`1.9.4` -> `2.0.0`
@biomejs/biome (source)	`1.9.4` -> `2.0.0`

Release Notes

biomejs/biome (@biomejs/biome)

`v2.0.0`

Compare Source

Major Changes

9d5d95f Thanks @arendjr! - Biome now resolves globs and paths from the configuration. Before, paths and globs were resolved from the working directory.
9d5d95f Thanks @arendjr! - Biome now raises a warning diagnostic for suppression comments that have <explanation> as reason.

<explanation> is provided as a placeholder when applying the suppression code fix from LSP editors.
9d5d95f Thanks @arendjr! - Removed the --config-path argument from the biome lsp-proxy and biome start commands.

The option was overriding the configuration path for all workspaces opened in the Biome daemon, which led to a configuration mismatch problem when multiple projects are opened in some editors or IDEs.

If you are using one of our official plugins for IDEs or editors, it is recommended to update it to the latest version of the plugin, or you will get unexpected behavior.

If you are a developer of a plugin, please update your plugin to use the workspace/configuration response instead of using the --config-path argument. Biome's LSP will resolve a configuration in the workspace automatically, so it is recommended to keep it empty unless you are using a custom configuration path.

9d5d95f Thanks @arendjr! - Downgraded some code fixes to unsafe which were previously safe.

The following rules have now a unsafe fix:

If you want to keep applying these fixes automatically, configure the rule fix as safe:

{
  "linter": {
    "rules": {
      "correctness": {
        "noFlatMapIdentity": {
          "level": "error",
          "fix": "safe"
        },
        "noUnusedImports": {
          "level": "error",
          "fix": "safe"
        }
      }
    }
  }
}

9d5d95f Thanks @arendjr! - Previously the lint rules noControlCharactersInRegex and noMisleadingCharacterClass checked both regular expression literals like /regex/ and dynamically built regular expressions like new RegExp("regex").

Checking dynamically built regular expressions has many limitations, edge cases, and complexities.
In addition, other rules that lint regular expressions don't check dynamically built regular expressions.

Rather than add support for other rules and have half-baked checking, we decided to remove support for dynamically built regular expressions.

Now the lint rules noControlCharactersInRegex and noMisleadingCharacterClass only check literals of regular expressions.

9d5d95f Thanks @arendjr! - The lint rule noRestrictedGlobals now supports customizing message for each global name.

For example, the following configuration:

{
  "options": {
    "deniedGlobals": {
      "$": "jQuery is not allowed. Use native DOM manipulation instead."
    }
  }
}

emits a diagnostic:

index.js:1:13 lint/style/noRestrictedGlobals ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ⚠ Do not use the global variable $.

  > 1 │ console.log($)
      │             ^
    2 │

  ℹ jQuery is not allowed. Use native DOM manipulation instead.

Breaking Change: The option deniedGlobals is now a record instead of an array. Run biome migrate to migrate the configuration automatically.

9d5d95f Thanks @arendjr! - Removed include and ignore fields in favor of the new field includes.

The Biome configuration file allows users to specify which files should be processed using glob patterns.
Prior to Biome 2.0, this was done using the include and ignore fields.
In Biome 2.0, include and ignore are removed and replaced by includes.
You can run biome migrate to convert include and ignore into includes automatically.

includes uses a different glob pattern format that fixes many issues and many other limitations that Biome users reported.

includes accepts an array of glob patterns.
A glob pattern starting with a ! is a negated pattern also called exception.
This replaces ignore patterns and allows users to create chains of include and ignore patterns.
Thus, it is now possible to include again a file previously ignored.
This was not possible with include and ignore, because ignore has priority over include.

The semantics of * and **/* have changed too.
Before, with include and ignore, the glob * was interpreted as **/*.
Now, with includes, the globs * and **/* are interpreted differently.
The first pattern matches all files that are inside a folder.
The second pattern recursively matches all files and sub-folders inside a folder.

Let's take an example.
Given the following file hierarchy of a project...
```
├── biome.json
├── src
│   ├── file.js
│   ├── file.ts
│   ├── out.gen.js
│   ├── file.test.js
│   └── test
│       └── special.test.js
└── test ...
```
...we want:
1. Ignore all files ending with .test.js, except special.test.ts.
2. Ignore all files of the test directory.
  The test directory is located at the root of the project.
3. Execute the linter on files in the src directory, that don't end with .gen.js.
  The src directory is located at the root of the project.
4. Enable the noDefaultExport lint rule on files ending with .ts.
Prior to Biome 2.0, the configuration might look like:
```
{
  "files": {
    "ignore": ["*.test.js", "test"]
  },
  "linter": {
    "include": ["src/**"],
    "ignore": ["*.gen.js"],
    "enabled": true
  },
  "overrides": [
    {
      "include": ["*.ts"],
      "linter": { "rules": { "style": { "noDefaultExport": "on" } } }
    }
  ]
}
```
Unfortunately, the configuration doesn't quite fit what we want:
1. There is no way to ignore files and unignore one of them.
  Thus, we ignore all files ending with .test.js, including special.test.ts.
2. The configuration ignores all directories named test, including src/test.
3. The linter is executed on all files of all directories named src
All these issues and limitations are fixed with includes.
Here the migrated configuration:
```
{
  "files": {
    "includes": ["**", "!**/*.test.js", "**/special.test.ts", "!test"]
  },
  "linter": {
    "includes": ["src/**", "!**/*.gen.js"],
    "enabled": true
  },
  "overrides": [
    {
      "includes": ["**/*.ts"],
      "linter": { "rules": { "style": { "noDefaultExport": "on" } } }
    }
  ]
}
```
1. All files named special.test.ts are unignored because the pattern appear after the pattern that ignore files ending with .test.js.
2. Only the test directory at the project's root is ignored because the pattern doesn't start with **/.
3. The linter is executed on the src directory at the project's root only.
Because includes pattern have a different pattern format than include and ignore we made some adjustments:
- We added the pattern ** in files.includes to ensure that all files are included before ignoring some of them.
- We added the prefix **/ for patterns that must match at any level of the file hierarchy.
9d5d95f Thanks @arendjr! - noUndeclaredVariables no longer reports TypeScript types.

In TypeScript projects, developers often use global declaration files to declare global types.
Biome is currently unable to detect these global types.
This creates many false positives for noUndeclaredVariables.

TypeScript is better suited to perform this kind of check.
As proof of this, TypeScript ESLint doesn't provide any rule that extends the no-undef ESLint rule.

This is why Biome 1.9 introduced a new option checkTypes which, when it is set to false, ignores undeclared type references.
The option was set to true by default.

This option is now set to false by default.
To get the previous behavior, you have to set checkTypes to true:
```
{
  "linter": {
    "rules": {
      "correctness": {
        "noUndeclaredVariables": {
          "level": "on",
          "options": { "checkTypes": true }
        }
      }
    }
  }
}
```
9d5d95f Thanks @arendjr! - The rule noUnusedVariables no longer reports unused function parameters. Use noUnusedFunctionParameters.
9d5d95f Thanks @arendjr! - Fixed #5564. noTypeOnlyImportAttributes now ignores files ending with the extension .ts when the type field of package.json is set to commonjs.
9d5d95f Thanks @arendjr! - The Biome formatter no longer adds a trailing comma in .json files, even when json.formatter.trailingCommas is set to true.
9d5d95f Thanks @arendjr! - Prettier 3.4 introduced a change in their normalization process of string literals: it no longer unescapes useless escape sequences.
Biome now matches the new behavior of Prettier when formatting code.
This affects the JSON and JavaScript formatters.
9d5d95f Thanks @arendjr! - Reduced accepted values for formatter options:
- The option --quote-style doesn't accept Single and Double anymore.
- The option --quote-properties doesn't accept AsNeeded and Preserve anymore.
- The option --semicolons doesn't accept AsNeeded and Always anymore.
- The option --arrow-parenthesis doesn't accept AsNeeded and Always anymore.
- The option --trailing-commas doesn't accept ES5, All and None anymore.
- The option --attribute-position doesn't accept Single and Multiline anymore.

9d5d95f Thanks @arendjr! - Removed the option enumMemberCase from the lint rule useNamingConvention.

enumMemberCase is an option that allows to customize the enforced case for TypeScript's enum members.
The option was introduced prior to the conventions option that allows to do the same thing.

The following configuration...

{
  "linter": {
    "rules": {
      "style": {
        "useNamingConvention": {
          "level": "on",
          "options": {
            "enumMemberCase": "PascalCase"
          }
        }
      }
    }
  }
}

...must be rewritten as:

{
  "linter": {
    "rules": {
      "style": {
        "useNamingConvention": {
          "level": "on",
          "options": {
            "conventions": [
              {
                "selector": { "kind": "enumMember" },
                "formats": ["PascalCase"]
              }
            ]
          }
        }
      }
    }
  }
}

Run biome migrate --write to turn enumMemberCase into conventions automatically.

9d5d95f Thanks @arendjr! - Removed support for BIOME_LOG_DIR.

The environment variable BIOME_LOG_DIR isn't supported anymore.

Use BIOME_LOG_PATH instead.
9d5d95f Thanks @arendjr! - Remove deprecated rules.

The following deprecated rules have been deleted:
- noInvalidNewBuiltin
- noNewSymbol
- useShorthandArrayType
- useSingleCaseStatement
- noConsoleLog
Run the command biome migrate --write to update the configuration.
9d5d95f Thanks @arendjr! - Removed the deprecated indentSize option.

The deprecated option indentSize, and its relative CLI options, has been removed:
- Configuration file: formatter.indentSize
- Configuration file: javascript.formatter.indentSize
- Configuration file: json.formatter.indentSize
- CLI option --indent-size
- CLI option --javascript-formatter-indent-size
- CLI option --json-formatter-indent-size
Use indentWidth and its relative CLI options instead.
9d5d95f Thanks @arendjr! - Removed ROME_BINARY. Use BIOME_BINARY instead.
9d5d95f Thanks @arendjr! - Removed support for legacy suppressions.

Biome used to support "legacy suppressions" that looked like this:
```
// biome-ignore lint(complexity/useWhile): reason
```
This format is no longer supported.
9d5d95f Thanks @arendjr! - Removed support for max_line_length from .editorconfig, as it isn't part of the official spec anymore.
9d5d95f Thanks @arendjr! - Removed support for rome-ignore suppression comments.

Use biome-ignore suppression comments instead.
9d5d95f Thanks @arendjr! - Removed support for rome.json.

Use biome.json or biome.jsonc instead.
9d5d95f Thanks @arendjr! - Removed the option all from the linter.

The options linter.rules.all and linter.rules.<group>.all has been removed.

The number of rules in Biome have increased in scope and use cases, and sometimes some of them can conflict with each other.

The option was useful at the beginning, but now it's deemed harmful, because it can unexpected behaviours in users projects.

To automatically remove it, run the following command:
```
biome migrate --write
```

9d5d95f Thanks @arendjr! - Removed the option trailingComma from the configuration and the CLI. Use the option trailingCommas instead:

{
  "javascript": {
    "formatter": {
-      "trailingComma": "es5"
+      "trailingCommas": "es5"
    }
  }
}

-biome format --trailing-comma=es5
+biome format --trailing-commas=es5

9d5d95f Thanks @arendjr! - Removed --apply and --apply-unsafe.

The CLI options --apply and --apply-unasfe aren't accepted anymore. Use --write and --write --unafe instead:
```
-biome check --apply-unsafe
+biome check --write --unsafe
```
```
-biome check --apply
+biome check --write
```

9d5d95f Thanks @arendjr! - Removed support for assert syntax.

Biome now longer supports the assert syntax, use the new with syntax instead

-import {test} from "foo.json" assert { for: "for" }
-export * from "mod" assert { type: "json" }
+import {test} from "foo.json" with { for: "for" }
+export * from "mod" with { type: "json" }

9d5d95f Thanks @arendjr! - Fixed #5495: The rule
noBlankTarget has been
updated to accept the rel="noopener" in addition to rel="noreferrer".
In addition, an option has been added that allows rel="noreferrer" to be
disabled.

The rule has been moved from the a11y group to the security group.
9d5d95f Thanks @arendjr! - The rule useImportRestrictions has been renamed to noPrivateImports, and its
functionality has been significantly upgraded.

Previously, the rule would assume that any direct imports from modules inside
other directories should be forbidden due to their package private visibility.

The updated rule allows configuring the default visibility of exports, and
recognises JSDoc comments to override this visibility. The default visibility
is now **public**, but can be set to **package**, or even **private**.
Refer to the documentation of the rule to understand how to leverage the JSDoc comments.

noPrivateImports is now recommended by default.
9d5d95f Thanks @arendjr! - The Biome daemon now reuses its workspace across connections. This allows multiple clients to
reuse the same documents and other cached data that we extract from them.

This primarily affects our IDE extensions: If you open multiple IDEs/windows for the same project,
they'll connect to the same daemon and reuse each other's workspace.

The Biome CLI is unaffected unless you opt in with the --use-server argument.
9d5d95f Thanks @arendjr! - Biome no longer treats too large files as errors.

Previously, files that exceed the configured size limit would throw an error, and the CLI would exit with an error code.

Now, the CLI ignores the file, emits an information diagnostic and doesn't exit with an error code.
9d5d95f Thanks @arendjr! - Change the group of some rules, promote nursery rules and update the recommended rule set.

The following rules have been moved to a new group:
- complexity/noArguments
- complexity/noCommaOperator
- complexity/noFlatMapIdentity
- complexity/noUselessContinue
- complexity/useNumericLiterals
- correctness/useValidTypeof
- performance/noNamespaceImport
- style/useArrayLiterals
- suspicious/noWith
New rules are incubated in the nursery group.
Once stable, we promote them to a stable group.
Use the biomem igrate command to automatically migrate nursery rules that have been promoted.

The following CSS rules have been promoted:
- correctness/noMissingVarFunction
- correctness/noUnknownPseudoClass
- correctness/noUnknownPseudoElement
- correctness/noUnknownTypeSelector
- style/noDescendingSpecificity
- style/noValueAtRule
- suspcious/noDuplicateCustomProperties
- suspcious/noDuplicateProperties
The following GraphQL rules have been promoted:
- style/useDeprecatedReason
- suspicious/noDuplicatedFields
The following JavaScript rules have been promoted:
- a11y/noStaticElementInteractions
- a11y/useAriaPropsSupportedByRole(recommended)
- a11y/useValidAutocomplete
- complexity/noUselessEscapeInRegex
- complexity/noUselessStringRaw
- performance/noDynamicNamespaceImportAccess
- performance/noImgElement
- style/noCommonJs
- style/noEnum
- style/noExportedImports
- style/noHeadElement
- style/noNestedTernary
- style/noProcessEnv
- style/noRestrictedImports
- style/noRestrictedTypes
- style/noSubstr
- style/useAtIndex
- style/useCollapsedIf
- style/useComponentExportOnlyModules
- style/useConsistentCurlyBraces
- style/useConsistentMemberAccessibility
- style/useTrimStartEnd
- suspicious/noDocumentCookie
- suspicious/noDocumentImportInPage
- suspicious/noDuplicateElseIf
- suspicious/noHeadImportInDocument
- suspicious/noIrregularWhitespace
- suspicious/noOctalEscape
- suspicious/noTemplateCurlyInString
- suspicious/useAdjacentOverloadSignatures
- suspicious/useGoogleFontDisplay
- suspicious/useGuardForIn
- suspicious/useStrictMode
Moreover, the following JavaScript rules are now recommended:
- complexity/noUselessUndefinedInitialization
- complexity/useArrayLiterals
- correctness/noConstantMathMinMaxClamp
- correctness/noUnusedFunctionParameters (recommended by ESLint)
- correctness/noUnusedImports
- correctness/noUnusedPrivateClassMembers (recommended by ESLint)
- correctness/noUnusedVariables (recommended by ESLint)
- complexity/useDateNow
And the following style rules are no longer recommended:
- style/useNumberNamespace
- style/useAsConstAssertion
- style/noParameterAssign
- style/noInferrableTypes
- style/useDefaultParameterLast
- style/noUnusedTemplateLiteral
- style/useEnumInitializers
- style/noUselessElse
- style/useSelfClosingElements
- style/useSingleVarDeclarator
9d5d95f Thanks @arendjr! - Update the default severity level of lint rules.

Every diagnostic emitted by Biome has a severity level set to error, warn, or info.
Previously, all recommended lint rules had a default severity level set to error.
All other lint rules had a default severity level set to warn.

We have adjusted the default severity level of every rule, whether recommended or not, to better communicate the severity that a diagnostic highlights.
- Rules that report hard errors, likely erroneous code, dangerous code, or accessibility issues now have a default severity level of error.
- Rules that report possibly erroneous codes, or code that could be cleaner if rewritten in another way now have a default severity level of warn.
- Rules that reports stylistic suggestions now have a default severity level of info.
You can use the CLI option --diagnostic-level=error to display only errors, or --diagnostic-level=warning to display both errors and warnings.
By default, all diagnostics are shown.
You can also use the CLI option --error-on-warnings to make the command fail when warnings are emitted.
9d5d95f Thanks @arendjr! - Reworked some recommended rules recommended to be less pedantic and blocking. This is a breaking change if your project relied on those rules to block the CI in case of violations; if that's the case, you should raise their severity level to error.

Some rules aren't recommended anymore, and some others return a different severity.

The following rules return a warning diagnostic:
- noDelete
- noForEach
- noSuspiciousSemicolonInJsx
- noThisInStatic
- noUnusedLabels
The following rules return an information diagnostic:
- noUselessCatch
- noUselessConstructor
- noUselessEmptyExport
- noUselessFragments
- noUselessLabel
- noUselessLoneBlockStatements
- noUselessSwitchCase
- noUselessTernary
- noUselessThisAlias
- noUselessTypeConstraint
- noFlatMapIdentity
The following rules aren't recommended anymore:
- noDelete
- noForEach
The rule noRenderReturnValue and useExhaustiveDependencies are only recommended when the react domain is enabled.
9d5d95f Thanks @arendjr! - Renamed the global option --skip-errors to --skip-parse-errors.
9d5d95f Thanks @arendjr! - Remove the code action quickfix.suppressRule.

The code action quickfix.suppressRule was removed in favour of two new code actions:
- quickfix.suppressRule.inline.biome: a code action that adds a suppression comment for each violation.
- quickfix.suppressRule.topLevel.biome: a code action that adds a suppression comment at the top of the file which suppresses a rule for the whole file.
Given the following code
```
let foo = "one";
debugger;
```
The code action quickfix.suppressRule.inline.biome will result in the following code:
```
// biome-ignore lint/style/useConst: <explanation>
let foo = "one";
// biome-ignore lint/suspicious/noDebugger: <explanation>
debugger;
```
The code action quickfix.suppressRule.topLevel.biome, instead, will result in the following code:
```
/** biome-ignore lint/suspicious/noDebugger: <explanation> */
/** biome-ignore lint/style/useConst: <explanation> */

let foo = "one";
debugger;
```
9d5d95f Thanks @arendjr! - Changed default formatting of package.json.

When Biome encounters a file called package.json, by default it will format the file with all objects and arrays expanded.
```
- { "name": "project", "dependencies": { "foo": "latest" } }
+ {
+  "projectName": "project",
+  "dependencies": {
+    "foo": "^1.0.0"
+  }
+ }
```
9d5d95f Thanks @arendjr! - The organizeImports is now part of Biome Assist.
9d5d95f Thanks @arendjr! - The rule noVar now belongs to the suspicious group
9d5d95f Thanks @arendjr! - The rule useWhile now belongs to the complexity group.
9d5d95f Thanks @arendjr! - The rule useImportExtensions has been updated to suggest actual file extensions instead of guesses based on hueristics.

As part of this, the suggestedExtensions option has been removed. A simpler,
new option called forceJsExtensions has been introduced for those who use
tsc's "module": "node16" setting.

The rule also no longer reports diagnostics to add an extension when the path
doesn't exist at all, with or without extension.
9d5d95f Thanks @arendjr! - Fixed #4545: useNamingConvention now correctly ignores declarations inside TypeScript's external modules.

The following interface name is no longer reported by the rule:
```
declare module "myExternalModule" {
  export interface my_INTERFACE {}
}
```
9d5d95f Thanks @arendjr! - The rule useAltText no longer checks the element's attributes containing object spread.

The following code doesn't trigger the rule anymore:
```
<img src="test.png" alt={alt} {...restProps}></img>
```

9d5d95f Thanks @arendjr! - The rule useNamingConvention no longer accepts non-ASCII characters by default.

Prior to Biome 2.0, non-ASCII names were accepted by default. They are now rejected.

For example, the following code is now reported as invalid by the useNamingConvention rule.

let johnCafé;

If you want to allow non ASCII filenames and non-ASCII identifiers, you need to set the requireAscii options in your Biome configuration file to false:

{
    "linter": {
        "rules": {
            "style": {
                "useFilenamingConvention": {
                    "level": "on",
                    "options": {
                        "requireAscii": false
                    }
                }
                "useFilenamingConvention": {
                    "level": "on",
                    "options": {
                        "requireAscii": false
                    }
                }
            }
        }
    }
}

9d5d95f Thanks @arendjr! - Renamed the rule noUnnecessaryContinue to noUselessContinue. Run the command biome migrate to update your configuration.
9d5d95f Thanks @arendjr! - Renamed the rule noMultipleSpacesInRegularExpressionLiterals to noAdjacentSpacesInRegex. Run the command biome migrate to update your configuration.

Minor Changes

9d5d95f Thanks @arendjr! - An option called allowNoReferrer has been added to the
noBlankTarget rule.

By default, noBlankTarget accepts both rel="noopener" and rel="noreferrer"
with links that have target="_blank". This is because the latter implies the
former, so either one is sufficient to mitigate the security risk.

However, allowing rel="noreferrer" may still be undesirable, because it can
break tracking, which may be an undesirable side-effect. As such, you can set
allowNoReferrer: false to only accept rel="noopener".
9d5d95f Thanks @arendjr! - Added new option javascript.parser.jsxEverywhere. This new option allows to control whether Biome should expect JSX syntax in .js/.mjs/.cjs files.

When jsxEverywhere is set to false, having JSX syntax like <div></div> inside .js/.mjs/.cjs files will result in a parsing error.

Despite the name of the option, JSX is never supported inside .ts files. This is because TypeScript generics syntax may conflict with JSX in such files.

This option defaults to true.

9d5d95f Thanks @arendjr! - Add a new JS assist rule - useSortedKeys which enforces ordering of a JS object properties.
This rule will consider spread/calculated keys e.g [k]: 1 as non-sortable.
Instead, whenever it encounters a non-sortable key, it will sort all the
previous sortable keys up until the nearest non-sortable key, if one exist.
This prevents breaking the override of certain keys using spread keys.

Source: https://perfectionist.dev/rules/sort-objects

// Base
// from
const obj = {
  b: 1,
  a: 1,
  ...g,
  ba: 2,
  ab: 1,
  set aab(v) {
    this._aab = v;
  },
  [getProp()]: 2,
  aba: 2,
  abc: 3,
  abb: 3,
  get aaa() {
    return "";
  },
};
// to
const obj = {
  a: 1,
  b: 1,
  ...g,
  set aab(v) {
    this._aab = v;
  },
  ab: 1,
  ba: 2,
  [getProp()]: 2,
  get aaa() {
    return "";
  },
  aba: 2,
  abb: 3,
  abc: 3,
};

9d5d95f Thanks @arendjr! - Added the new rule noFloatingPromises.
9d5d95f Thanks @arendjr! - Added the new rule noImportCycles.
9d5d95f Thanks @arendjr! - Added the new rule noTsIgnore.
9d5d95f Thanks @arendjr! - Added the new rule noUnwantedPolyfillio.
9d5d95f Thanks @arendjr! - Added a format option expand for Javascript and JSON formatters.
The option allows to enforce the formatting of arrays and objects on multiple lines, regardless of their length.
It has three options:

When set to auto (default), objects are expanded if the first property has a leading newline.
Arrays are collapsed when they fit to a single line.
For example, both styles below are considered as already formatted:
```
const obj = {
  foo: "bar",
};
```
```
const obj = { foo: "bar" };
```
When set to always, objects and arrays are always expanded.

When set to never, objects and arrays are never expanded when they fit in a single line.
It is equivalent to Prettier's Object Wrap option with collapse.
9d5d95f Thanks @arendjr! - The nursery rule noUnresolvedImports has been added.

Importing a non-existing export is an error at runtime or build time. With this
rule, Biome can detect such incorrect imports and report errors for them.

Note that if you use TypeScript, you probably don't want to use this rule, since
TypeScript already performs such checks for you.

9d5d95f Thanks @arendjr! - The rule noFocusedTests can now detect the usage of focused tests inside loops.

// invalid
describe.only.each([["a"], ["b"]])("%s", (a) => {});
it.only.each([["a"], ["b"]])("%s", (a) => {});
test.only.each([["a"], ["b"]])("%s", (a) => {});

// valid
describe.each([["a"], ["b"]])("%s", (a) => {});
it.each([["a"], ["b"]])("%s", (a) => {});
test.each([["a"], ["b"]])("%s", (a) => {});

9d5d95f Thanks @arendjr! - Linter groups now accept new options to enable/disable all rules that belong to a group, and control the severity
of the rules that belong to those groups.

For example, you can downgrade the severity of rules that belong to "style" to emit "info" diagnostics:
```
{
  "linter": {
    "rules": {
      "style": "info"
    }
  }
}
```
You can also enable all rules that belong to a group using the default severity of the rule using the "on" option:
```
{
  "linter": {
    "rules": {
      "complexity": "on"
    }
  }
}
```
9d5d95f Thanks @arendjr! - Biome assist is a new feature of the Biome analyzer. The assist is meant to provide actions. Actions differ from linter rules in that they aren't meant to signal errors.

The assist will provide code actions that users can opt into via configuration or via IDEs/editors, using the Language Server Protocol.

The assist is enabled by default. However, you can turn if off via configuration:
```
{
  "assist": {
    "enabled": false
  }
}
```
You can turn on the actions that you want to use in your configuration. For example, you can enable the useSortedKeys action like this:
```
{
  "assist": {
    "actions": {
      "source": {
        "useSortedKeys": "on"
      }
    }
  }
}
```
Alternatively, IDE/editor users can decide which action to apply on save directly from the editor settings, as long as the assist is enabled.

For example, in VS Code you can apply the useSortedKeys action when saving a file by adding the following snippet in settings.json:
```
{
  "editor.codeActionsOnSave": {
    "source.biome.useSortedKeys": "explicit"
  }
}
```
In Zed, you can achieve the same by adding the following snippet in ~/.config/zed/settings.json:
```
{
  "code_actions_on_format": {
    "source.biome.useSortedKeys": true
  }
}
```
9d5d95f Thanks @arendjr! - Biome migrate eslint outputs a better overriding behavior.

A Biome rule can have multiple ESLint equivalent rules.
For example, useLiteralKeys has two ESLint equivalent rules: dot-notation and @typescript-eslint/dot-notation.

Previously, Biome wouldn't always enable a Biome rule even if one of its equivalent rules was enabled.
Now Biome uses the higher severity level of all the equivalent ESLint rules to set the severity level of the Biome rule.

The following ESLint configuration...
```
{
  "rules": {
    "@&#8203;typescript-eslint/dot-notation": "error",
    "dot-notation": "off"
  }
}
```
...is now migrated to...
```
{
  "linter": {
    "rules": {
      "complexity": {
        "useLiteralKeys": "error"
      }
    }
  }
}
```
...because error is higher than off.
9d5d95f Thanks @arendjr! - Add useSymbolDescription.

9d5d95f Thanks @arendjr! - Enhanced the command migrate eslint. Now the command shows which ESLint rules were migrated,
and which rules aren't supported yet.

./eslint.config.js migrate ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ℹ 42% (3/7) of the rules have been migrated.

  ℹ Migrated rules:

  - getter-return
  - prefer-const
  - @&#8203;typescript-eslint/require-await

  ℹ Rules that can be migrated to an inspired rule using --include-inspired:

  - @&#8203;typescript-eslint/parameter-properties

  ℹ Rules that can be migrated to a nursery rule using --include-nursery:

  - @&#8203;typescript-eslint/switch-exhaustiveness-check

  ℹ Stylistic rules that the formatter may support (manual migration required):

  - semi

  ℹ Unsupported rules:

  - block-scoped-var

configuration ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ℹ Migration results:

  - ./biome.json: configuration successfully migrated.

9d5d95f Thanks @arendjr! - Suppression of syntax rules

Added support for suppressing syntax rules. Syntax rules are particular rules meant to complement the parser, hence they can't be configured.

Biome now allows to suppress those rules. This can, for example, be useful in case the rule is affected by a bug. However, this is more an escape hatch, so if a syntax rule requires a suppression, please file an issue.

Example:
```
// biome-ignore syntax/correctness/noTypeOnlyImportAttributes: bug
import type { MyType } from "my-esm-pkg" with { "resolution-mode": "import" };
```
Biome now requires all biome-ignore-start suppressions to have an equivalent biome-ignore-end comment.
9d5d95f Thanks @arendjr! - Add a new lint rule noConstantBinaryExpression.
This rule is inspired from ESLint's no-constant-binary-expression rule.
9d5d95f Thanks @arendjr! - The CLI options --only and --skip now accept rule and action names without prefixing the group name.

Previously --only=noDebugger was rejected.
You had to add the group name: --only=suspicious/noDebugger.
9d5d95f Thanks @arendjr! - Fixed #3574: noUnusedImports now reports empty named imports and suggests their removal.

The rule now suggests the removal of empty named imports such as:
```
- import {} from "mod";
```

9d5d95f Thanks @arendjr! - Added the new rule useAdjacentGetterSetter, which enforces getters and setters for the same property
to be adjacent in class and object definitions.

Example (Invalid): Name getter and setter are not adjacent:

class User {
  get name() {
    return this._name;
  }
  constructor() {}
  set name(value) {
    this._name = value;
  }
}

**Example (Invalid): Getter should go before the setter.

const user = {
  set name(value) {
    this._name = value;
  },
  get name() {
    return this._name;
  },
};

Example (Valid): Name getter and setter are adjacent:

class User {
  get name() {
    return this._name;
  }
  set name(value) {
    this._name = value;
  }
  get age() {
    return this._age;
  }
  set age(age) {
    this._age = age;
  }
}

9d5d95f Thanks @arendjr! - Added new rule useConsistentResponse which suggests to use static Response.json() and Response.redirect() methods instead of new Response when possible.

Example:
```
new Response(JSON.stringify({ value: 1 }));
Response.json({ value: 1 });
```
9d5d95f Thanks @arendjr! - Biome users can now configure code actions from linter rules as well as assist actions directly in the settings of their IDE/editor.

For example, let's consider the lint rule noSwitchDeclarations, which has an unsafe fix.
Previously, if you wanted to use this rule, you were "forced" to enable it via configuration, and if you wanted to apply its fix when you saved a file, you were forced to mark the fix as safe:
```
{
  "linter": {
    "rules": {
      "correctness": {
        "noSwitchDeclarations": {
          "level": "error",
          "fix": "safe"
        }
      }
    }
  }
}
```
Now, you can benefit from the code action without making the fix safe for the entire project. IDEs and editors that are LSP compatible allow to list a series of "filters" or code actions that can be applied on save. In the case of VS Code, you will need to add the following snippet in the settings.json:
```
{
  "editor.codeActionsOnSave": {
    "quickfix.biome.correctness.noSwitchDeclarations": "explicit"
  }
}
```
Upon save, Biome will inform the editor the apply the code action of the rule noSwitchDeclarations.
9d5d95f Thanks @arendjr! - Fixed #3401: noUnusedImports now keeps comments separated from the import with a blank line.

For example:
```
  // Orphan comment

- // Header comment
- import {} from "mod";
```
9d5d95f Thanks @arendjr! - Added a new propertyAssignment option to the noParameterAssign rule.
This option allows to configure whether property assignments on function parameters are permitted.
By default, propertyAssignment is set to allow.
Setting it to deny enforces stricter immutability by disallowing property mutations on function parameters.
9d5d95f Thanks @arendjr! - The formatter option bracketSpacing is now also supported in JSON files.
9d5d95f Thanks @arendjr! - useValidTypeof now accepts comparisons with variables.

Previously, the rule required to compare a typeof expression against another typeof expression or a valid string literal. We now accept more cases, notably comparison against a variable:
```
if (typeof foo === bar) {
  // ...
}
```
9d5d95f Thanks @arendjr! - Added the new rule noNestedComponentDefinitions,
which disallows nested component definitions in React components.

This rule is useful for preventing potential performance issues and improving code readability by ensuring that components are defined at the top level.

Example (Invalid):
```
function ParentComponent() {
  function ChildComponent() {
    return <div>Hello</div>;
  }
  return <ChildComponent />;
}
```
**E

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), 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 these updates again.

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

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

Signed-off-by: Adam Setch <[email protected]>

sonarqubecloud · 2025-06-17T19:09:26Z

Quality Gate failed

Failed conditions
B Maintainability Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE

renovate · 2025-06-17T22:58:09Z

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

setchy · 2025-06-17T22:59:29Z

The issues reported by SonarQube are pre-existing and separate from this PR

bmulholland · 2025-06-19T10:20:29Z

src/shared/logger.ts

 }

 function logMessage(
-  // biome-ignore lint/suspicious/noExplicitAny: <explanation>


v2 is "smart" enough to not the placeholder explanation. Makes sense 😄

bmulholland

LGTM! Love upgrades like these.

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

048ef71

renovate bot requested review from afonsojramos, bmulholland and setchy as code owners June 17, 2025 18:29

renovate bot added the dependency Dependency updates label Jun 17, 2025

setchy added 2 commits June 17, 2025 15:00

apply biome fixes

ed24f57

Signed-off-by: Adam Setch <[email protected]>

apply biome fixes

f53a27a

Signed-off-by: Adam Setch <[email protected]>

bmulholland reviewed Jun 19, 2025

View reviewed changes

bmulholland approved these changes Jun 19, 2025

View reviewed changes

setchy merged commit c35f200 into main Jun 19, 2025
13 of 14 checks passed

setchy deleted the renovate/biomejs-biome-2.x branch June 19, 2025 12:13

setchy added this to the Release 6.5.0 milestone Jun 19, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

chore(deps): update @biomejs/biome to v2 #2063

chore(deps): update @biomejs/biome to v2 #2063

Uh oh!

renovate bot commented Jun 17, 2025

Uh oh!

sonarqubecloud bot commented Jun 17, 2025

Uh oh!

renovate bot commented Jun 17, 2025

Uh oh!

setchy commented Jun 17, 2025

Uh oh!

bmulholland Jun 19, 2025

Uh oh!

setchy Jun 19, 2025

Uh oh!

bmulholland left a comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Milestone

Development

Uh oh!

3 participants

chore(deps): update @biomejs/biome to v2 #2063

chore(deps): update @biomejs/biome to v2 #2063

Uh oh!

Conversation

renovate bot commented Jun 17, 2025

Release Notes

v2.0.0

Major Changes

Minor Changes

Configuration

Uh oh!

sonarqubecloud bot commented Jun 17, 2025

Quality Gate failed

Uh oh!

renovate bot commented Jun 17, 2025

Edited/Blocked Notification

Uh oh!

setchy commented Jun 17, 2025

Uh oh!

bmulholland Jun 19, 2025

Choose a reason for hiding this comment

Uh oh!

setchy Jun 19, 2025

Choose a reason for hiding this comment

Uh oh!

bmulholland left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Milestone

Development

Uh oh!

3 participants

`v2.0.0`