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

renovate · 2025-07-01T01:29:03Z

This PR contains the following updates:

Package	Change	Age	Confidence
@biomejs/biome (source)	`^1.9.4` -> `^2.1.1`

Release Notes

biomejs/biome (@biomejs/biome)

`v2.1.1`

Compare Source

Patch Changes

#6781 9bbd34f Thanks @siketyan! - Fixed the FileFeaturesResult interface in the WASM API was defined as a mapped object but the actual value was a Map object.
#6761 cf3c2ce Thanks @dyc3! - Fixed #6759, a false positive for noFocusedTests that was triggered by calling any function with the name fit on any object.

The following code will now pass the noFocusedTests rule:
```
import foo from "foo";
foo.fit();
```

`v2.1.0`

Compare Source

Minor Changes

#6512 0c0bf82 Thanks @arendjr! - The rule noFloatingPromises can now detect floating arrays of Promises.

Invalid examples

// This gets flagged because the Promises are not handled.
[1, 2, 3].map(async (x) => x + 1);

Valid examples

await Promise.all([1, 2, 3].map(async (x) => x + 1));

#6637 6918085 Thanks @arendjr! - Type inference is now able to handle the sequence operator (,), as well as post- and pre-update operators: ++.

Example

let x = 5;

// We now infer that `x++` resolves to a number, while the expression as a whole
// becomes a Promise:
x++, new Promise((resolve) => resolve("comma"));

#6752 c9eaca4 Thanks @arendjr! - Fixed #6646: .gitignore files are now picked up even when running Biome from a nested directory, or when the ignore file itself is ignored through files.includes.
#6746 90aeead Thanks @arendjr! - biome migrate no longer enables style rules that were recommended in v1, because that would be undesirable for users upgrading from 2.0.

Users who are upgrading from Biome 1.x are therefore advised to first upgrade to Biome 2.0, and run the migration, before continuing to Biome 2.1 or later.

#6583 d415a3f Thanks @arendjr! - Added the nursery rule noMisusedPromises.

It signals Promises in places where conditionals or iterables are expected.

Invalid examples

const promise = Promise.resolve("value");

// Using a `Promise` as conditional is always truthy:
if (promise) {
  /* ... */
}

// Spreading a `Promise` has no effect:
console.log({ foo: 42, ...promise });

// This does not `await` the `Promise`s from the callbacks,
// so it does not behave as you may expect:
[1, 2, 3].forEach(async (value) => {
  await fetch(`/${value}`);
});

Valid examples

const promise = Promise.resolve("value");

if (await promise) {
  /* ... */
}

console.log({ foo: 42, ...(await promise) });

#6405 cd4a9bb Thanks @vladimir-ivanov! - Added the ignoreRestSiblings option to the noUnusedFunctionParameters rule.

This option is used to ignore unused function parameters that are siblings of the rest parameter.

The default is false, which means that unused function parameters that are siblings of the rest parameter will be reported.

Example
```
{
  "rules": {
    "noUnusedFunctionParameters": ["error", { "ignoreRestSiblings": true }]
  }
}
```
#6614 0840021 Thanks @arendjr! - We have implemented a more targeted version of the scanner, which ensures that if you provide file paths to handle on the CLI, the scanner will exclude directories that are not relevant to those paths.

Note that for many commands, such as biome check and biome format, the file paths to handle are implicitly set to the current working directory if you do not provide any path explicitly. The targeted scanner also works with such implicit paths, which means that if you run Biome from a subfolder, other folders that are part of the project are automatically exempted.

Use cases where you invoke Biome from the root of the project without providing a path, as well as those where project rules are enabled, are not expected to see performance benefits from this.

Implemented #6234, and fixed #6483 and #6563.
#6488 c5ee385 Thanks @ianzone! - nx.json and project.json have been added to the list of well-known files.
#6720 52e36ae Thanks @minht11! - Added # @biomejs/biome symbol to [organizeImports](https://biomejs.dev/assist/actions/organize-imports) :ALIAS:` group.

import { action } from '$lib' will be treated as alias import.

Patch Changes

#6712 2649ac6 Thanks @sterliakov! - Fixed #6595: Biome now supports // biome-ignore-all file-level suppressions in files that start with a shebang (#!).
#6758 28dc49e Thanks @arendjr! - Fixed #6573: Grit plugins can now match bare imports.

Example

The following snippet:
```
`import $source`
```
will now match:
```
import "main.css";
```

#6550 b424f46 Thanks @arendjr! - Type inference is now able to handle logical expressions: &&, ||, and ??.

Examples

// We can now infer that because `true` is truthy, the entire expression
// evaluates to a `Promise`.
true && Promise.reject("logical operator bypass");

// And we know that this doesn't:
false && Promise.reject("logical operator bypass");

// Truthiness, falsiness, and non-nullishness can all be determined on more
// complex expressions as well. So the following also works:
type Nullish = null | undefined;

type Params = {
  booleanOption: boolean | Nullish;
  falsyOption: false | Nullish;
};

function foo({ booleanOption, falsyOption }: Params) {
  // This may be a Promise:
  booleanOption ?? Promise.reject("logical operator bypass");

  // But this never is:
  falsyOption && Promise.reject("logical operator bypass");
}

#6413 4aa0e50 Thanks @wojtekmaj! - Improved error message in useDateNow rule.
#6673 341e062 Thanks @dyc3! - Fixed a case where the HTML formatter would mangle embedded language tags if whitespaceSensitivity was set to strict
#6642 a991229 Thanks @unvalley! - Fixed #4494: The noSecrets rule now correctly uses the entropyThreshold option to detect secret like strings.
#6520 0c43545 Thanks @arendjr! - Type inference is now able to handle ternary conditions in type aliases.

Note that we don't attempt to evaluate the condition itself. The resulting type is simply a union of both conditional outcomes.

Example
```
type MaybeResult<T> = T extends Function ? Promise<string> : undefined;

// We can now detect this function _might_ return a `Promise`:
function doStuff<T>(input: T): MaybeResult<T> {
  /* ... */
}
```
#6711 1937691 Thanks @sterliakov! - Fixed #6654: Fixed range highlighting of <explanation> placeholder in inline suppression block comments.
#6756 d12b26f Thanks @dyc3! - Fixed #6669: Added an exception to noUnusedImports to allow type augmentation imports.
```
import type {} from "@&#8203;mui/lab/themeAugmentation";
```
#6643 df15ad6 Thanks @skewb1k! - Fixed #4994: LSP server registered some capabilities even when the client did not support dynamic registration.
#6599 5e611fa Thanks @vladimir-ivanov! - Fixed #6380: The noFocusedTests rule now correctly displays the function name in the diagnostic message when a test is focused.

Every instance of a focused test function (like fdescribe, fit, ftest and only) had the word 'only' hardcoded. This has been updated to use the actual function name, so the message is now more accurate and specific.

Example for fdescribe:
```
  i The 'fdescribe' method is often used for debugging or during implementation.

  i Consider removing 'f' prefix from 'fdescribe' to ensure all tests are executed.
```

#6671 0c9ab43 Thanks @vladimir-ivanov! - Fixed #6634: The useReadonlyClassProperties rule now correctly flags mutations in class getters and in arrow functions within class properties.

Examples:

class GetterWithMutationValue {
  #value: string;

  get value() {
    if (!this.#value) {
      this.#value = "defaultValue";
    }

    return this.#value;
  }
}

class ClassPropertyArrowFunctionWithMutation {
  private bar: string | null = null;

  readonly action = () => {
    this.bar = "init";
  };
}

#6682 ca04cea Thanks @ematipico! - Fixed #6668: Biome Assist is now enabled by default for CSS files.

#6525 66b089c Thanks @arendjr! - Type inference can now infer the return types of functions and methods without annotations.

Examples

const sneakyObject = {
  doSomething() {
    return Promise.resolve("This is a floating promise!");
  },
};

// We can now detect that `doSomething()` returns a `Promise`.
sneakyObject.doSomething();

#6531 c06df79 Thanks @arendjr! - Biome's type inference now detects the type of properties with getters.

Examples

const sneakyObject2 = {
  get something() {
    return new Promise((_, reject) => reject("This is a floating promise!"));
  },
};
// We now detect this is a Promise:
sneakyObject2.something;

#6587 a330fcc Thanks @Conaclos! - organizeImports is now able to sort named specifiers and import attributes with bogus nodes.
#6618 6174869 Thanks @Shinyaigeek! - Fixed #6610: JSON import attributes are now correctly detected when they contain extra whitespace.
#6753 fce5d2c Thanks @dyc3! - Improved the error messages when Biome is provided incompatible arguments on the CLI.
#6587 a330fcc Thanks @Conaclos! - Fixed #6491: The action of useSortedKeys removed comments or wrongly transferred them to distinct nodes.
#6696 92964a7 Thanks @unvalley! - Fixed #6633: The noImplicitCoercion rule no longer reports diagnostics for 1 / value expressions.
```
1 / value; // no error
```
#6683 43d871e Thanks @ematipico! - Fixed #6537: Biome no longer removes the trailing comma from JSON files when formatter.json.trailingCommas is explicitly set to "all".
#6693 bfdce0b Thanks @dyc3! - Fixed #6691: The HTML parser will now consider . to be a valid character for tag names.
#6716 ead03d1 Thanks @siketyan! - The Biome LSP server no longer responds with an error for a textDocument/codeActions request when Biome doesn't support a feature for the file (e.g. Code actions aren't supported in GritQL files).
#6679 7bf9a60 Thanks @marko-hologram! - Fixed #6638: JavaScript formatter overrides options now correctly override expand option. JSON formatter overrides options now correctly override bracketSpacing and expand options.
#6717 7f5b541 Thanks @siketyan! - Fixed #6688: the noUselessFragments no longer reports <Fragment /> elements that includes HTML character entities.
#6600 853e1b5 Thanks @daivinhtran! - Fixed #4677: The noUnusedImports rule won't produce diagnostics for types used in comments of static members anymore.
#6662 3afc804 Thanks @arendjr! - If a nested configuration file is ignored by the root configuration, it will now actually be ignored.

Biome has an exception in place for configuration files so they cannot be ignored, because the configuration files are vital to Biome itself. But this exception was incorrectly applied to nested configurations as well. Now only the root configuration is exempt from being ignored.
#6596 c0718ca Thanks @ematipico! - Fixed #6566: Biome no longer errors when using the option --files-ignore-unknown=true in stdin mode.

Biome has also become less strict when using --stdin-file-path in stdin mode. It will no longer error if the file path doesn't contain an extension, but instead it will return the original content.
#6562 153eda7 Thanks @vladimir-ivanov! - Added the nursery rule noMagicNumbers. The rule detects and reports the use of "magic numbers" — numeric literals that are used directly in code without being assigned to a named constant.

Example
```
let total = price * 1.23; // Magic number for tax rate will highlight 1.23 as magic number
```
#6663 af78d6d Thanks @ematipico! - Fixed #6656: Biome now correctly formats HTML void elements such as <meta> when they contain a self-closing slash.
```
- <meta foo="bar" />
+ <meta foo="bar">
```
#6732 31e4396 Thanks @vladimir-ivanov! - Resolved #6281: Improved performance of handling package.json files in the scanner.
#6625 19cb475 Thanks @arendjr! - Fixed #6616: Fixed an issue with extending configurations that contained an explicit root field while the configuration in the project did not.
#6650 19aab18 Thanks @sterliakov! - Fixed #6621: Improved handling of multiple adjacent line suppressions. Biome now handles such suppressions separately, tracking whether each one is used.
#6700 cdd6e17 Thanks @denbezrukov! - Fixed #6680: Biome incorrectly formatted container-style queries by inserting misplaced spaces.
```
- @&#8203;container style (--responsive: true) {}
+ @&#8203;container style(--responsive: true) {}
```
#6709 ecf3954 Thanks @dyc3! - Fixed #6038: Fixed a false positive in noShadow where a function parameter in a type definition was erroneously flagged as a violation.

#6593 a4acbb7 Thanks @arendjr! - Type inference is now able to handle ternary conditions in expressions.

Examples

const condition = Math.random() > -1; // Always true, but dynamic to linter

// We now detect that this may return a `Promise`.
condition ? Promise.reject("ternary bypass") : null;

// On the other hand, we know the following is never a `Promise`:
const alwaysFalsy = 0;
alwaysFalsy ? Promise.reject("ternary bypass") : null;

#6428 4b501d3 Thanks @siketyan! - Added MemoryFileSystem to the WASM API.

You can now insert a file from your JS code:

import { MemoryFileSystem, Workspace } from "@&#8203;biomejs/wasm-web";

const fs = new MemoryFileSystem();
const workspace = Workspace.withFileSystem(fs);

fs.insert("/index.js", new TextEncoder().encode("let foo = 1;"));
fs.remove("/index.js");

#6594 626d4a1 Thanks @ematipico! - Fixed #6528: Biome didn't return the correct output when applying source.fixAll.biome inside Astro/Vue/Svelte files that contained safe fixed.

`v2.0.6`

Compare Source

Patch Changes

#6557 fd68458 Thanks @ematipico! - Fixed a bug where Biome didn't provide all the available code actions when requested by the editor.
#6511 72623fa Thanks @Conaclos! - Fixed #6492. The
organizeImports assist action no longer duplicates a comment at the start of
the file when :BLANK_LINE: precedes the first import group.
#6557 fd68458 Thanks @ematipico! - Fixed #6287 where Biome Language Server didn't adhere to the settings.requireConfiguration option when pulling diagnostics and code actions.
Note that for this configuration be correctly applied, your editor must support dynamic registration capabilities.
#6551 0b63b1d Thanks @Conaclos! - Fixed #6536. useSortedKeys no longer panics in some edge cases where object spreads are involved.
#6503 9a8fe0f Thanks @ematipico! - Fixed #6482 where nursery rules that belonged to a domain were incorrectly enabled.
#6565 e85761c Thanks @daivinhtran! - Fixed #4677: Now the noUnusedImports rule won't produce diagnostics for types used in JSDoc comment of exports.
#6166 b8cbd83 Thanks @mehm8128! - Added the nursery rule noExcessiveLinesPerFunction.
This rule restrict a maximum number of lines of code in a function body.

The following code is now reported as invalid when the limit of maximum lines is set to 2:
```
function foo() {
  const x = 0;
  const y = 1;
  const z = 2;
}
```
The following code is now reported as valid when the limit of maximum lines is set to 3:
```
const bar = () => {
  const x = 0;
  const z = 2;
};
```
#6553 5f42630 Thanks @denbezrukov! - Fixed #6547. Now the Biome CSS parser correctly parses @starting-style when it's used inside other at-rules. The following example doesn't raise an error anymore:
```
@&#8203;layer my-demo-layer {
  @&#8203;starting-style {
    div.showing {
      background-color: red;
    }
  }
}
```
#6458 05402e3 Thanks @ematipico! - Fixed an issue where the rule useSemanticElements used the incorrect range when positioning suppression comments.
#6560 6d8a6b9 Thanks @siketyan! - Fixed #6559: the error message on detected a large file was outdated and referred a removed configuration option files.ignore.
#6458 05402e3 Thanks @ematipico! - Fixed #6384. The rule useAltText now emits a diagnostic with a correct range, so suppression comments can work correctly.
#6518 7a56288 Thanks @wojtekmaj! - Fixed #6508, where the rule noUselessFragments incorrectly flagged Fragments containing HTML entities as unnecessary.
#6517 c5217cf Thanks @arendjr! - Fixed #6515. When using the
extends field to extend a configuration from an NPM package, we now accept the
condition names "biome" and "default" for exporting the configuration in
the package.json.

This means that where previously your package.json had to contain an export
declaration similar to this:
```
{
  "exports": {
    ".": "./biome.json"
  }
}
```
You may now use one of these as well:
```
{
  "exports": {
    ".": {
      "biome": "./biome.json"
    }
  }
}
```
Or:
```
{
  "exports": {
    ".": {
      "default": "./biome.json"
    }
  }
}
```
#6219 a3a3715 Thanks @huangtiandi1999! - Added new nursery rule noUnassignedVariables, which disallows let or var variables that are read but never assigned.

The following code is now reported as invalid:
```
let x;
if (x) {
  console.log(1);
}
```
The following code is now reported as valid:
```
let x = 1;
if (x) {
  console.log(1);
}
```
#6395 f62e748 Thanks @mdevils! - Added the new nursery rule noImplicitCoercion, which disallows shorthand type conversions in favor of explicit type conversion functions.

Example (Invalid): Boolean conversion using double negation:
```
!!foo;
!!(foo + bar);
```
Example (Invalid): Number conversion using unary operators:
```
+foo;
-(-foo);
foo - 0;
foo * 1;
foo / 1;
```
Example (Invalid): String conversion using concatenation:
```
"" + foo;
foo + "";
`` + foo;
foo += "";
```
Example (Invalid): Index checking using bitwise NOT:
```
~foo.indexOf(1);
~foo.bar.indexOf(2);
```
Example (Valid): Using explicit type conversion functions:
```
Boolean(foo);
Number(foo);
String(foo);
foo.indexOf(1) !== -1;
```
#6544 f28b075 Thanks @daivinhtran! - Fixed #6536. Now the rule noUselessFragments produces diagnostics for a top-level useless fragment that is in a return statement.
#6320 5705f1a Thanks @mdevils! - Added the new nursery rule useUnifiedTypeSignature, which disallows overload signatures that can be unified into a single signature.

Overload signatures that can be merged into a single signature are redundant and should be avoided. This rule helps simplify function signatures by combining overloads by making parameters optional and/or using type unions.

Example (Invalid): Overload signatures that can be unified:
```
function f(a: number): void;
function f(a: string): void;
```
```
interface I {
  a(): void;
  a(x: number): void;
}
```
Example (Valid): Unified signatures:
```
function f(a: number | string): void {}
```
```
interface I {
  a(x?: number): void;
}
```
Example (Valid): Different return types cannot be merged:
```
interface I {
  f(): void;
  f(x: number): number;
}
```
#6545 2782175 Thanks @ematipico! - Fixed #6529, where the Biome Language Server would emit an error when the user would open a file that isn't part of its workspace (node_modules or external files).
Now the language server doesn't emit any errors and it exits gracefully.

#6524 a27b825 Thanks @vladimir-ivanov! - Fixed #6500: The useReadonlyClassProperties rule now correctly marks class properties as readonly when they are assigned in a constructor, setter or method,
even if the assignment occurs inside an if or else block.

The following code is now correctly detected by the rule:

class Price {
  #price: string;

  @&#8203;Input()
  set some(value: string | number) {
    if (
      value === undefined ||
      value === null ||
      value === "undefined" ||
      value === "null" ||
      Number.isNaN(value)
    ) {
      this.#price = "";
    } else {
      this.#price = "" + value;
    }
  }
}

#6355 e128ea9 Thanks @anthonyshew! - Added a new nursery rule noAlert that disallows the use of alert, confirm and prompt.

The following code is deemed incorrect:
```
alert("here!");
```
#6548 37e9799 Thanks @ematipico! - Fixed #6459, where the Biome LSP was not taking into account the correct settings when applying source.fixAll.biome code action.

`v2.0.5`

Compare Source

Patch Changes

#6461 38862e6 Thanks @ematipico! - Fixed #6419, a regression where stdin mode would create a temporary new file instead of using the one provided by the user. This was an intended regression.

Now Biome will use the file path passed via --std-file-path, and apply the configuration that matches it.
#6480 050047f Thanks @Conaclos! - Fixed #6371.
useNamingConvention now checks the string case of objects' property shorthand.

#6477 b98379d Thanks @ematipico! - Fixed an issue where Biome formatter didn't format consistently CSS value separated by commas.

.font-heading {
- font-feature-settings: var(--heading-salt), var(--heading-ss06),
-   var(--heading-ss11), var(--heading-cv09), var(--heading-liga),
-   var(--heading-calt);

+  font-feature-settings:
+    var(--heading-salt), var(--heading-ss06), var(--heading-ss11),
+    var(--heading-cv09), var(--heading-liga), var(--heading-calt);
}

#6248 ec7126c Thanks @fireairforce! - Fixed grit pattern matching for different kinds of import statements.

The grit pattern import $imports from "foo" will match the following code:
```
import bar from "foo";
import { bar } from "foo";
import { bar, baz } from "foo";
```

`v2.0.4`

Compare Source

Patch Changes

#6450 7472d9e Thanks @ematipico! - Fixed an issue where the binary wasn't correctly mapped.

`v2.0.3`

Patch Changes

#6439 7e4da4e Thanks @ematipico! - Fixed an issue where the correct rights aren't added to the binary during publishing

#6297 cc4b8c9 Thanks @vladimir-ivanov! - Added a new lint useReadonlyClassProperties rule.
This rule is a port of ESLint's prefer-readonly rule.

Example:

class Example {
  // All properties below can be marked as readonly
  public constantValue = 42;
  protected initializedInConstructor: string;
  private privateField = true;

  constructor(initializedInConstructor: string) {
    this.initializedInConstructor = initializedInConstructor;
  }
}

`v2.0.2`

Patch Changes

#6436 ec7c63d Thanks @ematipico! - Fixed an issue where binaries weren't copied anymore inside the @biomejs/cli-* packages.

`v2.0.1`

Compare Source

Patch Changes

#6425 00e97ad Thanks @siketyan! - Fixed #6391: the rule noUselessFragments no longer reports a fragment that contains whitespaces which aren't trimmed by the runtime.
#6417 dd88565 Thanks @ematipico! - Fixed #6360: The following pseudo classes and elements are no longer reported by noUnknownPseudoClass or noUnknownPseudoElement rules.
- :open
- ::details-content
- ::prefix
- ::search-text
- ::suffix
#6417 dd88565 Thanks @ematipico! - Fixed #6357, where the boolean values weren't correctly merged when using the extends functionality. Now Biome correctly merges the values.
#6417 dd88565 Thanks @ematipico! - Fixed #6341: Fixed an issue where Biome would throw an error for the language tags nb and nn.
#6385 94142dd Thanks @siketyan! - Fixed #6377: The rule noSelfCompare now correctly compares two function calls with different arguments.
#6417 dd88565 Thanks @ematipico! - Fixed #6278: useExhaustiveDependencies no longer adds duplicated dependencies into the list.
#6417 dd88565 Thanks @ematipico! - Fix #6396, where vi.useFakeTimers() and vi.useRealTimers() incorrectly triggered React Hooks-related rules
#6417 dd88565 Thanks @ematipico! - Fixed a bug where Biome didn't correctly discover nested configuration files when using the lint command and the linter is disabled in the root configuration.
#6422 594ec50 Thanks @ematipico! - Removed the experimental rename feature from Biome LSP, which caused some issues inside existing editors such as Zed.
#6388 c6942d2 Thanks @siketyan! - Fixed #6375: the formatter no longer inserts an extra empty line before a semicolon when it has leading comments.

`v2.0.0`

Compare Source

Major Changes

Biome now resolves globs and paths from the configuration. Before, paths and globs were resolved from the working directory.
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.
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.

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

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.

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.

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.
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 }
        }
      }
    }
  }
}
```
The rule noUnusedVariables no longer reports unused function parameters. Use noUnusedFunctionParameters.
Fixed #5564. noTypeOnlyImportAttributes now ignores files ending with the extension .ts when the type field of package.json is set to commonjs.
The Biome formatter no longer adds a trailing comma in .json files, even when json.formatter.trailingCommas is set to true.
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.
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 anymo

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, on day 1 of the month ( * 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 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 branch from 297b34d to 34b1bb0 Compare July 8, 2025 11:49

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

23cbde9

renovate bot force-pushed the renovate/biomejs-biome-2.x branch from 34b1bb0 to 23cbde9 Compare July 8, 2025 16:52

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

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

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

Uh oh!

renovate bot commented Jul 1, 2025 •

edited

Loading

Uh oh!

Uh oh!

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

Are you sure you want to change the base?

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

Uh oh!

Conversation

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

Uh oh!

Release Notes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Major Changes

Configuration

Uh oh!

Uh oh!

renovate bot commented Jul 1, 2025 •

edited

Loading