Registro de cambios

2.1.2

Patch Changes

#6865 b35bf64 Thanks @denbezrukov! - Fix #6485: Handle multiple semicolons correctly in blocks (#6485)
```
1
div {
2
  box-sizing: border-box;
3
  color: red;
4
}
```
#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:
```
1
item
2
.as_any_css_declaration_with_semicolon()
3
.as_css_declaration_with_semicolon()
```
Now, it can be done directly with:
```
1
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:

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

1
interface Bar {
2
  child: { grandChild: { [BAR]: typeof BAR; enumFoo: EnumFoo } };
3
}
4
const BAR = "bar";
5
enum EnumFoo {
6
  BAR = "bar",
7
}

#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:
```
1
const numbers: number[];
2
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

1
const txStatements: Array<(tx) => Promise<any>> = [];
2

3
db.transaction((tx: any) => {
4
  for (const stmt of txStatements) {
5
    // We correctly flag this resolves to a `Promise`:
6
    stmt(tx);
7
  }
8
});

Valid example

1
async function valid(db) {
2
  const txStatements: Array<(tx: any) => void> = [(tx) => tx.insert().run()];
3

4
  db.transaction((tx: any) => {
5
    for (const stmt of txStatements) {
6
      // We don't flag a false positive here anymore:
7
      stmt(tx);
8
    }
9
  });
10
}

#6757 13a0818 Thanks @mdevils! - Added the rule noVueReservedProps, resolves #6309.

It prevents the use of reserved Vue prop names such as key and ref which can cause conflicts and unexpected behavior in Vue components.

Invalid example

1
import { defineComponent } from "vue";
2

3
export default defineComponent({
4
  props: ["ref", "key", "foo"],
5
});

1
<script setup>
2
defineProps({
3
  ref: String,
4
  key: String,
5
  foo: String,
6
});
7
</script>

Valid examples

1
import { defineComponent } from "vue";
2

3
export default defineComponent({
4
  props: ["foo"],
5
});

1
<script setup>
2
defineProps({ foo: String });
3
</script>

#6840 1a57b51 Thanks @denbezrukov! - Allow multiple identifiers in ::part() pseudo-element selector.
```
1
::part(first second) {
2
}
```
#6845 4fd44ec Thanks @arendjr! - Fixed #6510: The scanner no longer shows diagnostics on inaccessible files unless --verbose is used.
#6844 b7e2d4d Thanks @sterliakov! - Fixed #6837: Fixed regression with multiple consecutive line suppression comments using instances (like // biome-ignore lint/correctness/useExhaustiveDependencies(depName): reason).
#6818 5f3f5a6 Thanks @siketyan! - Fixed an issue where textDocument/codeAction in the LSP could respond with outdated text edits after the workspace watcher observed outdated changes to the file.
#6804 3e6ab16 Thanks @arendjr! - noFloatingPromises will no longer suggest to add await keyword inside synchronous callbacks nested inside async functions.
#6901 c9e969a Thanks @arendjr! - Fixed #6777: Fixed type inference handling of this to avoid infinite recursion.

Thanks to @sterliakov for the thorough investigation!

#6855 d1581c7 Thanks @vladimir-ivanov! - Fixed #6775: useReadonlyClassProperties now also captures mutations inside function arguments.

Example:

1
class Counter {
2
  private counter: number;
3
  count() {
4
    console.log(this.counter++);
5
    const counterString = `${this.counter++}`;
6
  }
7
}

#6839 4cd62d8 Thanks @ematipico! - Fixed a bug where Biome didn’t throw any error when vcs.useIgnoreFile is set to true, and there wasn’t any ignore file read. Now Biome correctly throws an error if no ignore files are found.
#6911 6d68074 Thanks @arendjr! - Fixed #6838: Reduce resource consumption in the Biome Language Server by using non-recursive filesystem watchers instead of recursive ones.

Watchers are responsible for notifying Biome of changes to files in the filesystem. We used to set up a single recursive watcher, but that meant that Biome would receive filesystem notifications for all files in your project, even for ignored folders such as build/ or dist/ folders.

With this patch, we set up non-recursive watchers only for the folders that are relevant to a project.

Related to this, we also solved an issue where incoming notifications were incorrectly filtered, causing ignored files to be processed and stored in our module graph anyway.

2.1.1

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:
```
1
import foo from "foo";
2
foo.fit();
```

2.1.0

Minor Changes

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

Invalid examples

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

Valid examples

1
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

1
let x = 5;
2

3
// We now infer that `x++` resolves to a number, while the expression as a whole
4
// becomes a Promise:
5
(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

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

3
// Using a `Promise` as conditional is always truthy:
4
if (promise) {
5
  /* ... */
6
}
7

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

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

Valid examples

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

3
if (await promise) {
4
  /* ... */
5
}
6

7
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
```
1
{
2
  "rules": {
3
    "noUnusedFunctionParameters": ["error", { "ignoreRestSiblings": true }]
4
  }
5
}
```
#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 $ symbol to organizeImports :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:
```
1
`import $source`
```
will now match:
```
1
import "main.css";
```

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

Examples

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

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

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

12
type Params = {
13
  booleanOption: boolean | Nullish;
14
  falsyOption: false | Nullish;
15
};
16

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

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

#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
```
1
type MaybeResult<T> = T extends Function ? Promise<string> : undefined;
2

3
// We can now detect this function _might_ return a `Promise`:
4
function doStuff<T>(input: T): MaybeResult<T> {
5
  /* ... */
6
}
```
#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.
```
1
import type {} from "@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:
```
1
  i The 'fdescribe' method is often used for debugging or during implementation.
2

3
  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:

1
class GetterWithMutationValue {
2
  #value: string;
3

4
  get value() {
5
    if (!this.#value) {
6
      this.#value = "defaultValue";
7
    }
8

9
    return this.#value;
10
  }
11
}

1
class ClassPropertyArrowFunctionWithMutation {
2
  private bar: string | null = null;
3

4
  readonly action = () => {
5
    this.bar = "init";
6
  };
7
}

#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

1
const sneakyObject = {
2
  doSomething() {
3
    return Promise.resolve("This is a floating promise!");
4
  },
5
};
6

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

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

Examples

1
const sneakyObject2 = {
2
  get something() {
3
    return new Promise((_, reject) => reject("This is a floating promise!"));
4
  },
5
};
6
// We now detect this is a Promise:
7
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
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
```
1
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.
```
1
<meta foo="bar" />
2
<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.
```
1
@container style (--responsive: true) {}
2
@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

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

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

6
// On the other hand, we know the following is never a `Promise`:
7
const alwaysFalsy = 0;
8
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:

1
import { MemoryFileSystem, Workspace } from "@biomejs/wasm-web";
2

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

6
fs.insert("/index.js", new TextEncoder().encode("let foo = 1;"));
7
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.

2.0.6

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:
```
1
function foo() {
2
  const x = 0;
3
  const y = 1;
4
  const z = 2;
5
}
```
The following code is now reported as valid when the limit of maximum lines is set to 3:
```
1
const bar = () => {
2
  const x = 0;
3
  const z = 2;
4
};
```
#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:
```
1
@layer my-demo-layer {
2
  @starting-style {
3
    div.showing {
4
      background-color: red;
5
    }
6
  }
7
}
```
#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:
```
1
{
2
  "exports": {
3
    ".": "./biome.json"
4
  }
5
}
```
You may now use one of these as well:
```
1
{
2
  "exports": {
3
    ".": {
4
      "biome": "./biome.json"
5
    }
6
  }
7
}
```
Or:
```
1
{
2
  "exports": {
3
    ".": {
4
      "default": "./biome.json"
5
    }
6
  }
7
}
```
#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:
```
1
let x;
2
if (x) {
3
  console.log(1);
4
}
```
The following code is now reported as valid:
```
1
let x = 1;
2
if (x) {
3
  console.log(1);
4
}
```
#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:
```
1
!!foo;
2
!!(foo + bar);
```
Example (Invalid): Number conversion using unary operators:
```
1
+foo;
2
-(-foo);
3
foo - 0;
4
foo * 1;
5
foo / 1;
```
Example (Invalid): String conversion using concatenation:
```
1
"" + foo;
2
foo + "";
3
`` + foo;
4
foo += "";
```
Example (Invalid): Index checking using bitwise NOT:
```
1
~foo.indexOf(1);
2
~foo.bar.indexOf(2);
```
Example (Valid): Using explicit type conversion functions:
```
1
Boolean(foo);
2
Number(foo);
3
String(foo);
4
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:
```
1
function f(a: number): void;
2
function f(a: string): void;
```
```
1
interface I {
2
  a(): void;
3
  a(x: number): void;
4
}
```
Example (Valid): Unified signatures:
```
1
function f(a: number | string): void {}
```
```
1
interface I {
2
  a(x?: number): void;
3
}
```
Example (Valid): Different return types cannot be merged:
```
1
interface I {
2
  f(): void;
3
  f(x: number): number;
4
}
```
#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:

1
class Price {
2
  #price: string;
3

4
  @Input()
5
  set some(value: string | number) {
6
    if (
7
      value === undefined ||
8
      value === null ||
9
      value === "undefined" ||
10
      value === "null" ||
11
      Number.isNaN(value)
12
    ) {
13
      this.#price = "";
14
    } else {
15
      this.#price = "" + value;
16
    }
17
  }
18
}

#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:
```
1
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.

2.0.5

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.

1
.font-heading {
2
 font-feature-settings: var(--heading-salt), var(--heading-ss06),
3
   var(--heading-ss11), var(--heading-cv09), var(--heading-liga),
4
   var(--heading-calt);
5

6
  font-feature-settings:
7
    var(--heading-salt), var(--heading-ss06), var(--heading-ss11),
8
    var(--heading-cv09), var(--heading-liga), var(--heading-calt);
9
}

#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:
```
1
import bar from "foo";
2
import { bar } from "foo";
3
import { bar, baz } from "foo";
```

2.0.4

Patch Changes

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

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

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

7
  constructor(initializedInConstructor: string) {
8
    this.initializedInConstructor = initializedInConstructor;
9
  }
10
}

2.0.2

Patch Changes

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

2.0.1

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.

2.0.0

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:

1
{
2
  "linter": {
3
    "rules": {
4
      "correctness": {
5
        "noFlatMapIdentity": {
6
          "level": "error",
7
          "fix": "safe"
8
        },
9
        "noUnusedImports": {
10
          "level": "error",
11
          "fix": "safe"
12
        }
13
      }
14
    }
15
  }
16
}

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:

1
{
2
  "options": {
3
    "deniedGlobals": {
4
      "$": "jQuery is not allowed. Use native DOM manipulation instead."
5
    }
6
  }
7
}

emits a diagnostic:

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

3
  ⚠ Do not use the global variable $.
4

5
  > 1 │ console.log($)
6
      │             ^
7
    2 │
8

9
  ℹ 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…
```
1
├── biome.json
2
├── src
3
│   ├── file.js
4
│   ├── file.ts
5
│   ├── out.gen.js
6
│   ├── file.test.js
7
│   └── test
8
│       └── special.test.js
9
└── 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:
```
1
{
2
  "files": {
3
    "ignore": ["*.test.js", "test"]
4
  },
5
  "linter": {
6
    "include": ["src/**"],
7
    "ignore": ["*.gen.js"],
8
    "enabled": true
9
  },
10
  "overrides": [
11
    {
12
      "include": ["*.ts"],
13
      "linter": { "rules": { "style": { "noDefaultExport": "on" } } }
14
    }
15
  ]
16
}
```
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:
```
1
{
2
  "files": {
3
    "includes": ["**", "!**/*.test.js", "**/special.test.ts", "!test"]
4
  },
5
  "linter": {
6
    "includes": ["src/**", "!**/*.gen.js"],
7
    "enabled": true
8
  },
9
  "overrides": [
10
    {
11
      "includes": ["**/*.ts"],
12
      "linter": { "rules": { "style": { "noDefaultExport": "on" } } }
13
    }
14
  ]
15
}
```
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:
```
1
{
2
  "linter": {
3
    "rules": {
4
      "correctness": {
5
        "noUndeclaredVariables": {
6
          "level": "on",
7
          "options": { "checkTypes": true }
8
        }
9
      }
10
    }
11
  }
12
}
```
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 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.

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…

1
{
2
  "linter": {
3
    "rules": {
4
      "style": {
5
        "useNamingConvention": {
6
          "level": "on",
7
          "options": {
8
            "enumMemberCase": "PascalCase"
9
          }
10
        }
11
      }
12
    }
13
  }
14
}

…must be rewritten as:

1
{
2
  "linter": {
3
    "rules": {
4
      "style": {
5
        "useNamingConvention": {
6
          "level": "on",
7
          "options": {
8
            "conventions": [
9
              {
10
                "selector": { "kind": "enumMember" },
11
                "formats": ["PascalCase"]
12
              }
13
            ]
14
          }
15
        }
16
      }
17
    }
18
  }
19
}

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

Removed support for BIOME_LOG_DIR.

The environment variable BIOME_LOG_DIR isn’t supported anymore.

Use BIOME_LOG_PATH instead.
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.
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.
Removed ROME_BINARY. Use BIOME_BINARY instead.
Removed support for legacy suppressions.

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

Use biome-ignore suppression comments instead.
Removed support for rome.json.

Use biome.json or biome.jsonc instead.
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:
Terminal window
```
1
biome migrate --write
```

Removed the option trailingComma from the configuration and the CLI. Use the option trailingCommas instead:

1
{
2
  "javascript": {
3
    "formatter": {
4
      "trailingComma": "es5"
5
      "trailingCommas": "es5"
6
    }
7
  }
8
}

1
biome format --trailing-comma=es5
2
biome format --trailing-commas=es5

Removed --apply and --apply-unsafe.

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

Removed support for assert syntax.

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

1
import {test} from "foo.json" assert { for: "for" }
2
export * from "mod" assert { type: "json" }
3
import {test} from "foo.json" with { for: "for" }
4
export * from "mod" with { type: "json" }

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.
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.
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.
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.
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 biome migrate 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
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.
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.
Renamed the global option --skip-errors to --skip-parse-errors.
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
```
1
let foo = "one";
2
debugger;
```
The code action quickfix.suppressRule.inline.biome will result in the following code:
```
1
// biome-ignore lint/style/useConst: <explanation>
2
let foo = "one";
3
// biome-ignore lint/suspicious/noDebugger: <explanation>
4
debugger;
```
The code action quickfix.suppressRule.topLevel.biome, instead, will result in the following code:
```
1
/** biome-ignore lint/suspicious/noDebugger: <explanation> */
2
/** biome-ignore lint/style/useConst: <explanation> */
3

4
let foo = "one";
5
debugger;
```
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.
```
1
{ "name": "project", "dependencies": { "foo": "latest" } }
2
{
3
 "projectName": "project",
4
 "dependencies": {
5
   "foo": "^1.0.0"
6
 }
7
}
```
The organizeImports is now part of Biome Assist.
The rule noVar now belongs to the suspicious group
The rule useWhile now belongs to the complexity group.
The rule useImportExtensions has been updated to suggest actual file extensions instead of guesses based on heuristics.

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.
Fixed #4545: useNamingConvention now correctly ignores declarations inside TypeScript’s external modules.

The following interface name is no longer reported by the rule:
```
1
declare module "myExternalModule" {
2
  export interface my_INTERFACE {}
3
}
```
The rule useAltText no longer checks the element’s attributes containing object spread.

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

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.

1
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:

1
{
2
    "linter": {
3
        "rules": {
4
            "style": {
5
                "useFilenamingConvention": {
6
                    "level": "on",
7
                    "options": {
8
                        "requireAscii": false
9
                    }
10
                }
11
                "useFilenamingConvention": {
12
                    "level": "on",
13
                    "options": {
14
                        "requireAscii": false
15
                    }
16
                }
17
            }
18
        }
19
    }
20
}

Renamed the rule noUnnecessaryContinue to noUselessContinue. Run the command biome migrate to update your configuration.
Renamed the rule noMultipleSpacesInRegularExpressionLiterals to noAdjacentSpacesInRegex. Run the command biome migrate to update your configuration.

Minor Changes

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

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

1
// Base
2
// from
3
const obj = {
4
  b: 1,
5
  a: 1,
6
  ...g,
7
  ba: 2,
8
  ab: 1,
9
  set aab(v) {
10
    this._aab = v;
11
  },
12
  [getProp()]: 2,
13
  aba: 2,
14
  abc: 3,
15
  abb: 3,
16
  get aaa() {
17
    return "";
18
  },
19
};
20
// to
21
const obj = {
22
  a: 1,
23
  b: 1,
24
  ...g,
25
  set aab(v) {
26
    this._aab = v;
27
  },
28
  ab: 1,
29
  ba: 2,
30
  [getProp()]: 2,
31
  get aaa() {
32
    return "";
33
  },
34
  aba: 2,
35
  abb: 3,
36
  abc: 3,
37
};

Added the new rule noFloatingPromises.
Added the new rule noImportCycles.
Added the new rule noTsIgnore.
Added the new rule noUnwantedPolyfillio.
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:
```
1
const obj = {
2
  foo: "bar",
3
};
```
```
1
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.
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.

The rule noFocusedTests can now detect the usage of focused tests inside loops.

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

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

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:
```
1
{
2
  "linter": {
3
    "rules": {
4
      "style": "info"
5
    }
6
  }
7
}
```
You can also enable all rules that belong to a group using the default severity of the rule using the "on" option:
```
1
{
2
  "linter": {
3
    "rules": {
4
      "complexity": "on"
5
    }
6
  }
7
}
```
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:
```
1
{
2
  "assist": {
3
    "enabled": false
4
  }
5
}
```
You can turn on the actions that you want to use in your configuration. For example, you can enable the useSortedKeys action like this:
```
1
{
2
  "assist": {
3
    "actions": {
4
      "source": {
5
        "useSortedKeys": "on"
6
      }
7
    }
8
  }
9
}
```
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:
```
1
{
2
  "editor.codeActionsOnSave": {
3
    "source.biome.useSortedKeys": "explicit"
4
  }
5
}
```
In Zed, you can achieve the same by adding the following snippet in ~/.config/zed/settings.json:
```
1
{
2
  "code_actions_on_format": {
3
    "source.biome.useSortedKeys": true
4
  }
5
}
```
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…
```
1
{
2
  "rules": {
3
    "@typescript-eslint/dot-notation": "error",
4
    "dot-notation": "off"
5
  }
6
}
```
…is now migrated to…
```
1
{
2
  "linter": {
3
    "rules": {
4
      "complexity": {
5
        "useLiteralKeys": "error"
6
      }
7
    }
8
  }
9
}
```
…because error is higher than off.
Add useSymbolDescription.

Enhanced the command migrate eslint. Now the command shows which ESLint rules were migrated, and which rules aren’t supported yet.

1
./eslint.config.js migrate ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
2

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

5
  ℹ Migrated rules:
6

7
  - getter-return
8
  - prefer-const
9
  - @typescript-eslint/require-await
10

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

13
  - @typescript-eslint/parameter-properties
14

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

17
  - @typescript-eslint/switch-exhaustiveness-check
18

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

21
  - semi
22

23
  ℹ Unsupported rules:
24

25
  - block-scoped-var
26

27
configuration ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
28

29
  ℹ Migration results:
30

31
  - ./biome.json: configuration successfully migrated.

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:
```
1
// biome-ignore syntax/correctness/noTypeOnlyImportAttributes: bug
2
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.
Add a new lint rule noConstantBinaryExpression. This rule is inspired from ESLint’s no-constant-binary-expression rule.
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.
Fixed #3574: noUnusedImports now reports empty named imports and suggests their removal.

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

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:

1
class User {
2
  get name() {
3
    return this._name;
4
  }
5
  constructor() {}
6
  set name(value) {
7
    this._name = value;
8
  }
9
}

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

1
const user = {
2
  set name(value) {
3
    this._name = value;
4
  },
5
  get name() {
6
    return this._name;
7
  },
8
};

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

1
class User {
2
  get name() {
3
    return this._name;
4
  }
5
  set name(value) {
6
    this._name = value;
7
  }
8
  get age() {
9
    return this._age;
10
  }
11
  set age(age) {
12
    this._age = age;
13
  }
14
}

Added new rule useConsistentResponse which suggests to use static Response.json() and Response.redirect() methods instead of new Response when possible.

Example:
```
1
new Response(JSON.stringify({ value: 1 }));
2
Response.json({ value: 1 });
```
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:
```
1
{
2
  "linter": {
3
    "rules": {
4
      "correctness": {
5
        "noSwitchDeclarations": {
6
          "level": "error",
7
          "fix": "safe"
8
        }
9
      }
10
    }
11
  }
12
}
```
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:
```
1
{
2
  "editor.codeActionsOnSave": {
3
    "quickfix.biome.correctness.noSwitchDeclarations": "explicit"
4
  }
5
}
```
Upon save, Biome will inform the editor the apply the code action of the rule noSwitchDeclarations.
Fixed #3401: noUnusedImports now keeps comments separated from the import with a blank line.

For example:
```
1
// Orphan comment
2

3
// Header comment
4
import {} from "mod";
```
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.
The formatter option bracketSpacing is now also supported in JSON files.
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:
```
1
if (typeof foo === bar) {
2
  // ...
3
}
```
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):
```
1
function ParentComponent() {
2
  function ChildComponent() {
3
    return <div>Hello</div>;
4
  }
5
  return <ChildComponent />;
6
}
```
Example (Valid):
```
1
function ChildComponent() {
2
  return <div>Hello</div>;
3
}
4
function ParentComponent() {
5
  return <ChildComponent />;
6
}
```
Added the new rule noDestructuredProps, which disallow the use of destructured props in Solid projects.
You can now enable lint rules using the default severity suggested by Biome using the new variant "on", when enabling a rule.

For example, the default severity of the rule style.noVar is error, so you would use "on", and then linting a code that uses var, will result in an error:
```
1
{
2
  "linter": {
3
    "recommended": false,
4
    "rules": {
5
      "style": {
6
        "noVar": "on"
7
      }
8
    }
9
  }
10
}
```
main.js
```
1
var name = "tobias";
```
The command biome lint main.js will result in an error due to the default severity assigned to noVar.

Refer to the documentation page of each rule to know their suggested diagnostic severity, or use the command biome explain <RULE_NAME>:
Terminal window
```
1
biome explain noVar
```
Biome VCS integration now supports nested ignore files.

For git, if a .gitignore is found in a nested folder root/packages/foo/, and it contains the pattern dist/, only files and directories inside root/packages/foo/dist are matched.
Added the rule useUniqueElementIds. This rule disallows the use of static IDs in React components. It encourages to generate unique IDs for accessibility purposes using useId.

The following code is now reported as invalid:
```
1
function App() {
2
  return <div id="static-id" />;
3
}
```
The following code is now reported as valid:
```
1
import { useId } from "react";
2
function App() {
3
  const id = useId();
4
  return <div id={id} />;
5
}
```

Added the new JavaScript rule useConsistentObjectDefinition rule. The rule enforces a consistent style for the definition of objects:

By default, the rule enforces a shorthand style:

1
const validShorthand = {
2
  // Property shorthand
3
  foo,
4

5
  // Method shorthand
6
  method() {
7
    return "method";
8
  },
9
};

Alternatively, the rule can be configured to enforce an explicit style:

1
const invalidExplicit = {
2
  // Basic property shorthand violations
3
  foo: foo,
4

5
  // Method shorthand violations
6
  method: function () {
7
    return "method";
8
  },
9
};

Introduced more advanced logging capabilities:

Every Biome CLI command can now be passed a --log-file=<path> argument, which will write all log messages for that invocation to the given path instead of stdout.

In addition, the --log-level parameter now also accepts a tracing value. When --log-level=tracing is used, Biome also prints timing information from tracing spans to the log.

Combined with Biome’s ability to print logs in JSON format, and the jq command line utility, this allows you to perform advanced analysis on Biome’s internal performance.

For example, if you want to figure out which paths take the longest when building the module graph, you can use the following commands:
Terminal window
```
1
biome lint --log-level=tracing --log-kind=json --log-file=tracing.json
2
cat tracing.json | jq '. | select(.span.name == "update_module_graph") | { path: .span.path, time_busy: .["time.busy"], time_idle: .["time.idle"] }' > filtered.json
```
Now you will have a file called filtered.json with all the relevant timings, together with the paths used during the invocations.
Added options to suspicious/noConfusingLabels to allow specific labels.

Fixed #4549: noUnknownProperty now accepts more known CSS properties.

1
['anchor-default', 'anchor-scroll', 'inset-area', 'position-animation', 'position-fallback', 'position-fallback-bounds', 'position-try-options']
2
['anchor-scope', 'interpolate-size', 'line-fit-edge', 'masonry', 'masonry-auto-tracks', 'masonry-direction', 'masonry-fill', 'masonry-flow', 'masonry-slack', 'masonry-template-areas', 'masonry-template-tracks', 'position-anchor', 'position-area', 'position-try-fallbacks', 'position-visibility', 'scroll-start-target', 'text-box', 'view-transition-class', 'view-transition-group']

This change replaces deprecated properties, improving CSS validation.

LSP clients can now override the configuration path for each workspace, by responding to workspace/configuration requests.
Added the new CSS rule noImportantStyles, which prevents the use of !important inside CSS declarations.
Biome now emits a warning diagnostic if the configuration contains an out-of-sync schema URL.
Introduced a new configuration setting files.experimentalScannerIgnores.

This setting may be used to configure a set of file and folder names that should be unconditionally ignored by Biome’s scanner.

Biome maintains an internal list of default ignore entries, which is based on user feedback and which may change in any release. This setting allows overriding this internal list completely.

This is considered an advanced feature that users should not need to tweak themselves, but they can as a last resort. This setting can only be configured in root configurations, and is ignored in nested configs.

Entries must be file or folder names. Specific paths and globs are not supported.

Examples where this may be useful:
```
1
{
2
  "files": {
3
    "experimentalScannerIgnores": [
4
      // You almost certainly don't want to scan your `.git` folder, which
5
      // is why it's already ignored by default:
6
      ".git",
7

8
      // But the scanner does scan `node_modules` by default. If you
9
      // *really* don't want this, you can ignore it like this:
10
      "node_modules",
11

12
      // But it's probably better to ignore a specific dependency.
13
      // For instance, one that happens to be particularly slow to scan:
14
      "RedisCommander.d.ts",
15
    ],
16
  },
17
}
```
Please be aware that rules relying on the module graph or type inference information may be negatively affected if dependencies of your project aren’t (fully) scanned.
Added the new rule useSingleJsDocAsterisk which enforces JSDoc comment lines to start with a single asterisk.
```
1
// Invalid
2
/**
3
 ** Description
4
 */
5

6
// Valid
7
/**
8
 * Description
9
 */
```
The CLI flag --javascript-attribute-position was renamed to --javascript-formatter-attribute-position for consistency.
Introduced the domains linter feature. The Biome linter now has a new way to opt-in rules, with a concept called domains.

Domains can be seen as concepts shared by different rules.

You can enable and disable multiple rules that belong to a domain. When you assign "all", Biome will enable all the rules, when you assign "none", Biome will disable the rules, when you assign “recommended”, Biome will enable all rules of the domain that are recommended.
biome.jsonc
```
1
{
2
  linter: {
3
    domains: {
4
      test: "all", // all rules that belong to this domain are enabled
5
      react: "recommended", // only the recommended rules from this domain are enabled
6
      solid: "none", // rules related to Solid are disabled
7
    },
8
  },
9
}
```
New domains introduced:
- test: it will enable rules:
  - noExportsInTest
  - noExcessiveNestedTestSuites
  - noDuplicateTestHooks
  - noFocusedTests And it will inject the following globals:
  - after
  - afterAll
  - afterEach
  - before
  - beforeEach
  - beforeAll
  - describe
  - it
  - expect
  - test
- next: it will enable rules for Next.js projects:
  - useExhaustiveDependencies
  - useHookAtTopLevel
  - noImgElement
  - noHeadImportInDocument
  - noHeadImportInDocument
- react: it will enable rules for React projects:
  - useExhaustiveDependencies
  - useHookAtTopLevel
- solid: it will enable rules for Solid projects:
  - noReactSpecificProps
For more information regarding how Biome enables rules via domains, please refer to the documentation page of each rule.
Biome now prints diagnostics sorted by their severity. The order is the following:
1. information
2. warning
3. error
This means that error diagnostics are printed last, so users can see them first.
Added the new rule useIterableCallbackReturn, which enforces consistent return values in iterable callbacks.

The following methods require a return value in their callback:
- every
- filter
- find
- findIndex
- findLast
- findLastIndex
- flatMap
- map
- reduce
- reduceRight
- some
- sort
- toSorted — from (when called on Array)
The rule disallows a return value inside the callback of the method forEach.

Examples:
```
1
[].map(() => {
2
  // Missing return value
3
});
```
```
1
[].forEach(() => {
2
  return 1; // Disallowed
3
});
```

Added the new rule noReactPropAssign, based on the react-hooks rule react-hooks/react-compiler

The following code is now reported as invalid:

1
function Foo(props) {
2
  props.bar = `Hello ${props.bar}`;
3
  return <div>{props.bar}</div>;
4
}

The following code is now reported as valid:

1
function Foo({ bar }) {
2
  bar = `Hello ${bar}`;
3
  return <div>{bar}</div>;
4
}

Added new rule noBitwiseOperators, which disallows bitwise operators.

The Biome analyzer now supports a new top-level suppression. These suppression have to be placed at the top of the file, and they must be followed by two newlines ( \n\n\).

The analyzer rules specified inside the block comment will be suppressed for the whole file.

In the example, we suppress the rules lint/style/useConst and lint/suspicious/noDebugger for the whole file:

1
/**
2
 * biome-ignore-all lint/style/useConst: i like let
3
 * biome-ignore-all lint/suspicious/noDebugger: needed now
4
 */
5

6
let path = "/path";
7
let _tmp = undefined;
8
debugger;

In this other example, we suppress lint/suspicious/noEmptyBlock for a whole CSS file:

1
/**
2
/* biome-ignore-all lint/suspicious/noEmptyBlock: it's fine to have empty blocks
3
*/
4

5
a {
6
}
7
span {
8
}

A new diagnostic is emitted if biome-ignore-all suppression isn’t placed at the top of the file:

1
file.js:3:1 suppressions/incorrect ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
2

3
  ! Top level suppressions can only be used at the beginning of the file.
4

5
    2 │ let foo = 2;
6
  > 3 │ /**
7
      │ ^^^
8
  > 4 │ * biome-ignore-all lint/style/useConst: reason
9
  > 5 │ */
10
      │ ^^
11
    6 │ let bar = 33;
12

13
  i Rename this to biome-ignore
14

15
    2 │ let foo = 2;
16
    3 │ /**
17
  > 4 │ * biome-ignore-all lint/style/useConst: reason
18
      │   ^^^^^^^^^^^^^^^^
19
    5 │ */
20
    6 │ let bar = 33;

Added the new rule useNumericSeparators, which encourages the use of numeric separators to improve readability.
useImportExtensions now checks imports with sub extensions.
```
1
- import 'styles.css'
2
+ import 'styles.css.ts'
```
It’s possible to override the option files.maxSize. This option is helpful if you need to process specific files that exceed the default maxSize:
```
1
{
2
  "overrides": [{
3
    "includes": ["dist/**"]
4
    "files": {
5
      "maxSize": 20000
6
    }
7
  }]
8
}
```
Added the new CLI option called --threads to the ci command. It allows to control the numbers of threads that can be used when using the Biome CLI.

It’s possible to use the environment variable BIOME_THREADS as an alternatives.

This feature is useful when running the CLI in environments that have limited resources, for example CI/CD.
Terminal window
```
1
biome ci --threads=1
2
BIOME_THREADS=1 biome ci
```
Added the new rule useObjectSpread, which prefers object spread syntax over Object.assign() when constructing new objects.

Example (Invalid): Using Object.assign with an empty object:
```
1
Object.assign({}, foo);
2
Object.assign({}, { foo: "bar" });
```
Example (Invalid): Using Object.assign with object literal as first argument:
```
1
Object.assign({ foo: "bar" }, baz);
2
Object.assign({}, baz, { foo: "bar" });
```
Example (Valid): Using object spread syntax:
```
1
({ ...foo });
2
({ ...baz, foo: "bar" });
```
Example (Valid): Modifying existing objects is allowed:
```
1
Object.assign(foo, { bar: baz });
2
Object.assign(foo, bar, baz);
```
Added an option to the lint command called --suppress. The new option suppresses a violation instead of applying a rule fix. The option accepts a string that is used as reason of the suppression comment.

When running the following command, it will add the suppression comment:
Terminal window
```
1
biome lint --write --suppress="Migration to Biome"
```
```
1
debugger;
2
foo == bar;
```
```
1
 // biome-ignore lint/suspicious/noDebugger: Migration to Biome
2
debugger;
3
 // biome-ignore lint/suspicious/noDoubleEquals: Migration to Biome
4
foo == bar;
```

Add an ignoreRestSiblings option into noUnusedVariables.

When this option is set to false, the rule will not ignore variables that created using the rest pattern:

1
{
2
  "linter": {
3
    "rules": {
4
      "correctness": {
5
        "noUnusedVariables": {
6
          "level": "error",
7
          "options": {
8
            "ignoreRestSiblings": false
9
          }
10
        }
11
      }
12
    }
13
  }
14
}

1
const { lorem, ...test } = bar; // the variable "test" will trigger the rule
2
console.log(lorem);

Upgraded some unsafe fixes to safe fixes.

The following rules have now a safe fix:
- noExtraBooleanCast
- noNonoctalDecimalEscape
- noSwitchDeclarations
- noThisInStatic
- noUnusedTemplateLiteral
- noUselessContinue
- noUselessElse
- noUselessStringConcat
- useArrayLiterals
- useExponentiationOperator
- useNumberToFixedDigitsArgument
- useNumericLiterals
- useSimplifiedLogicExpression
Added support for monorepos. The feature will work out of the box for the majority of the users. If your project has nested configuration files, use the command biome migrate from the root of the project.

Monorepo support in Biome is done in a single way. Create a biome.json at the root of the project. This configuration file is now called the root configuration. Then, each nested configuration file must specify the new field "root": false.

We also introduced a new microsyntax for extending a nested configuration from the root configuration, which is "extends": "//". This new syntax means “this config extends from the root config”. When using this microsyntax, you may omit the "root": false field as it is implied.

Note that nested configs are not required to extend from the root config, and you can still have independent nested configs, as well as nested configs that extend from other files. In those cases, "root": false must be specified explicitly.
Added support for formatting .html files. The formatting is considered **experimental, ** and it’s only opt-in via configuration:
```
1
{
2
  "html": {
3
    "formatter": {
4
      "enabled": true
5
    }
6
  }
7
}
```
Biome formatter attempts to format as Prettier, however some default options might differ.

An option html.formatter.selfCloseVoidElements allows to control whether the trailing / of void elements should be printed.

By default, Biome formatter will remove the /:
```
1
<input />
2
<input>
```
If you come from Prettier and you want to keep the same formatting behaviour, you should set the option to "always":
```
1
{
2
  "html": {
3
    "formatter": {
4
      "selfCloseVoidElements": "always"
5
    }
6
  }
7
}
```
```
1
<input>
2
<input />
```
Use to the command biome migrate prettier to apply this change automatically.

Added an unsafe fix to the rule useExhaustiveDependencies.

For example, this violation will provide the following code fix:

1
import { useEffect } from "react";
2

3
function MyComponent() {
4
  let a = 1;
5
  useEffect(() => {}, [a]);
6
}

1
  × This hook specifies more dependencies than necessary: a
2

3
    3 │ function MyComponent() {
4
    4 │   let a = 1;
5
  > 5 │   useEffect(() => {}, [a]);
6
      │   ^^^^^^^^^
7
    6 │ }
8
    7 │
9

10
  i This dependency can be removed from the list.
11

12
    3 │ function MyComponent() {
13
    4 │   let a = 1;
14
  > 5 │   useEffect(() => {}, [a]);
15
      │                        ^
16
    6 │ }
17
    7 │
18

19
  i Unsafe fix: Remove the extra dependencies from the list.
20

21
    5 │ ··useEffect(()·=>·{},·[a]);
22
      │                        -

The rule useExhaustiveDependencies now reports a diagnostic when the dependency list is not an array literal.
Added the new rule useIndexOf, based on the unicorn rule prefer-array-index-of
Added a new rule useExhaustiveSwitchCases, which detects any missing cases for switch statements. Currently, it supports only literal union types.

For example:
```
1
type Day =
2
  | "Monday"
3
  | "Tuesday"
4
  | "Wednesday"
5
  | "Thursday"
6
  | "Friday"
7
  | "Saturday"
8
  | "Sunday";
9

10
const day: Day = "Monday";
11
let result = 0;
12

13
switch (day) {
14
  case "Monday": {
15
    result = 1;
16
    break;
17
  }
18
}
```
The switch statement is missing other cases than 'Monday', which will cause a runtime error. To fix this issue, add missing cases or a default case to the statement.
Fixed #4416: The rules useExportType and useImportType now ignore TypeScript declaration files.
Added the new rule useForComponent.

This rule enforces usage of Solid’s <For /> component for mapping an array to JSX elements.
Added new lint rule noShadow, a port of eslint’s no-shadow.

This rule disallows variable declarations from shadowing variables declared in an outer scope. For example:
```
1
const foo = 1;
2

3
function bar() {
4
  const foo = 2; // This variable shadows the outer foo
5
}
```
Add style option for the useImportType rule.

The rule now allows enforcing an import style for importing types. See the rule documentation for more details.
Added the new rule useJsonImportAttribute to enforce the use of import attributes for JSON modules.

This rule ensures that all imports of .json files include the with { type: "json" } assertion, which is required to inform the JavaScript runtime that the imported file should be parsed as JSON.
```
1
import jsonData from './data.json';
2
import jsonData from './data.json' with { type: "json" };
```
```
1
import jsonData from './data.json' with { someOtherAttribute: "value" };
2
import jsonData from './data.json' with { type: "json", someOtherAttribute: "value" };
```
This rule is based on the proposal in issue #6043.
useLiteralKeys now handles numeric keys and is declared as being the same rule as the ESLint no-useless-computed-key rule.
useNamingConmvention now ignores unused variables prefixed with an underscore _.

This avoids conflicts with the unsafe fix of noUnusedVariables. The following code is now accepted because the variable is unused and prefixed with an underscore.
```
1
const _Unknown_Style = 0;
```
The package now requires v2 of the WebAssembly packages. The internal APIs of Workspace are now camelCase.
The rule useArrayLiterals now provides a code fix.
```
1
const xs = new Array();
2
const xs = [];
```
The code fix is currently marked as unsafe. We plan to make it safe in a future release of Biome.
The command migrate is now able to migrate nested configuration files.
Added the new rule noRestrictedElements, which prevents use of the specified HTML elements and components.
Added the new lint rule noAwaitInLoop.

Patch Changes

Fix #5001, where the CSS formatter removes whitespace from selector preceded by a comment
Fixed noUnusedVariables rule to suggest unsafe fix for unused function declarations.
Fixed a false positive of noUselessEscapeInRegex where \k was reported as useless in non-Unicode regular expressions.
Fixed an issue where the ordering of the diagnostics wasn’t predictable.
Fixed a bug where the environment variable BIOME_CONFIG_PATH wasn’t correctly picked up.
Biome logs a warning in case a folder contains biome.json and biome.jsonc, and it will use biome.json by default.
noUndeclaredVariables is now able to bind read of value to a type-only import in ambient contexts (#4526).

In the following code, A is now correctly bound to the type-only import. Previously, A was reported as an undeclared variable.
```
1
import type { A } from "mod";
2

3
declare class B extends A {}
```
Fix #4317, setter parameter can contain a trailing comma, the following example will now parsed correctly:
```
1
export class DummyClass {
2
  set input(value: string) {}
3
}
```
Fix #4575, don’t wrap selector indentation after css comments.
Fix #4258, where fixed css parse error with @-moz-document url-prefix().
Fixed #4391: Some files from the .vscode directory are no longer incorrectly parsed as JSON.
The biome format command now correctly handles the --skip-errors option, allowing it to skip files with syntax errors and continue formatting the remaining valid files. When this option is used, skipped syntax errors are reported as information, since the user is already aware of them.
biome migrate eslint now correctly resolves the scoped package named eslint-config.
Fixed #3836: The CSS parser will now correctly parse the following:
```
1
.foo {
2
  color: red;
3
}
```
Fixed a bug where the related diagnostics attached to the main diagnostics didn’t have a correct message.
Fixed noAccumulatingSpread not reporting calls to Object.assign. The following code will now be reported:
```
1
let a = [{ a: 1 }, { b: 2 }];
2
a.reduce((acc, val) => Object.assign(acc, val), []);
```
The summary reporter doesn’t take --max-diagnostics into account anymore.

Fixed #4553: noUselessFragments will now correctly fix JSX attributes:

1
<Suspense
2
  fallback={
3
    <>
4
      <span>Loading...</span>
5
    </>
6
  }
7
>
8
  {children}
9
</Suspense>

becomes:

1
<Suspense fallback={<span>Loading...</span>}>{children}</Suspense>

Fixed #4528: biome migrate eslint now correctly handles shared ESLint configuration that don’t follow the ESLint naming convention.

ESLint recommends that a package that exports a shared configuration be prefixed with eslint-config- or simply named eslint-config. This is only a recommendation. Packages that export shared configurations can have arbitrary names. Biome is now able to load any package.
Fixed #4993: useAwait now correctly warn on functions with decorator with callback argument.
Fixed #4756: noDuplicateProperties now throws lint errors properly when we use @supports.
Fixed #5981, where noUnknownPseudoClass didn’t take :global into consideration when cssModules is enabled.
Fixed #2406: Biome longer expands properties of object type annotations in the only function parameter to align with Prettier.
Fixed #4740: biome migrate eslint now correctly handles ESLint configuration with null values in file lists.
Fixed #4202: Align with Prettier in formatting test functions.
Fixed #342: The JavaScript parser now properly handles unterminated string literals, such as:
```
1
function Comp() {
2
  return (
3
      <a rel="
```
Fixed a bug where syntax rules didn’t provide an automatic way to suppress the rule. Now the LSP will show suppression actions if a syntax rule is violated.
Fixed a CSS parser error: @-moz-document url-prefix(https://example.com) and @-moz-document domain(example.com) are now valid.
Fixed #4967: The fix for useArrowFunction no longer breaks function bodies starting with {.
Fixed #5998. The rule noUnknownPseudoElement now correctly checks names of pseudo-element functions.
Fixed #5024: Added useJsxKeyInIterable rule to React domain.
Fixed #5410. Biome now correctly parse an .editorconfig that includes character classes in glob patterns.
Fixed #2260: The LSP server now returns correct text edits for the specified range in textDocument/rangeFormatting and textDocument/onTypeFormatting requests.
noUnusedVariables no longer reports top-level variables in a global declaration file as unused.
Type exports now support renaming types to default.

The following code is now parsed successfully:
```
1
export { type A as default } from "./b.ts";
```
Added proper support for arrow functions in the lint rule https://biomejs.dev/linter/rules/use-explicit-type/
The rule useNamingConvention no longer suggests renaming top-level variables in a global declaration file.
Improved context in error messages when migrating Prettier configurations
Allowed single spaces in useConsistentCurlyBraces rule.
Fixed #4413: The GraphQL formatter no longer adds a new line at the start of block comments on Windows.
Fixed #5407. Now the noUnusedImports code fix correctly keeps top-level comments that were attached to lone imports.
Fixed #3859: the --skip-parse-errors option is now applied to commands: lint, check, and ci.
The rage command now prints the configuration path relative to the working directory, if applicable.
Fixed #5606: We now correctly handle .mjs extensions in Node.js packages with "type": "commonjs".
Fixed #1597: useExhaustiveDependencies no longer gets confused about the stability of dependencies by parentheses or type assertions.
Fixed #4751 by checking fragments inside JSXElement and conditional expressions.

For example, the following two cases will now be reported:
```
1
<section>
2
  <>
3
    <div />
4
    <div />
5
  </>
6
</section>
```
```
1
showFullName ? <>{fullName}</> : <>{firstName}</>;
```
The rule noFallthroughSwitchCase no longer panics on some incomplete code snippets.
Fixed #5007: Resolved false positives in noMissingVarFunction for container-name.

Fixed #4841: Shebang and top leading comments in .cjs files are now handled correctly

Example: shebang only (keep it as is)

1
#!/usr/bin/env node

Example: comments only (keep it as is)

1
// comment

Example: with shebang

1
 #!/usr/bin/env node"use strict";
2
 #!/usr/bin/env node
3
 "use strict";
4
let some_variable = "some value";

Example: with comment

1
 // comment
2
 "use strict"; // comment
3
 "use strict";
4
 // comment
5
let some_variable = "some value";

Example: with shebang and comment

1
 #!/usr/bin/env node"use strict";
2
 // comment
3
 #!/usr/bin/env node
4
 "use strict";
5
 // comment
6
let some_variable = "some value";

Fixes useExhaustiveDependencies missing dependencies being defined after the hook itself failure.

Example:

1
import { useState, useEffect } from "react";
2

3
function MyComponent() {
4
  useEffect(() => {
5
    console.log(a);
6
  }, []);
7

8
  let a = 1;
9
}

Fixed #4714: Suppression comments no longer fail on functions that themselves contain suppression comments.

This now works correctly:

1
// biome-ignore lint/complexity/useArrowFunction: this suppression now works
2
const foo0 = function (bar: string) {
3
  // biome-ignore lint/style/noParameterAssign: even if there are other suppressions inside
4
  bar = "baz";
5
};

Add @vitest/eslint-plugin to list of Biome rule sources

Fixed useHookAtTopLevel rule to properly detect React components wrapped in memo and forwardRef, and correctly handle property accessors in control flow analysis.

The rule now correctly identifies hooks in components like:

1
const TestMemo = memo(
2
  forwardRef((props, ref) => {
3
    useEffect(() => {
4
      const [test, setTest] = useState(1); // now properly flagged
5
    }, []);
6
    return <div ref={ref}>test</div>;
7
  }),
8
);

And properly handles property accessors:

1
function ReactComponent() {
2
  const testObj = {
3
    get print() {
4
      return "hello"; // no longer considered component return
5
    },
6
  };
7
  const callback = useCallback(() => {}, []);
8
  return <></>;
9
}

noMisleadingCharacterClass no longer panics on malformed escape sequences that end with a multi-byte character (#4587).
Fixed the flag --bracket-spacing that was duplicated between the global configuration and the language-specific override for JavaScript.

Fixed #4715: The useJsxKeyInIterable rule now reports missing keys inside switch and if statements.

1
const data = [
2
  { value: "a", type: "string" },
3
  { value: 9, type: "number" },
4
  { value: "c", type: "string" },
5
];
6

7
const MyComponent = () => {
8
  return (
9
    <>
10
      {/* if statements */}
11
      {data.map((x) => {
12
        if (x.type === "string") {
13
          return <div>{x.value}</div>; // no key, emits diagnostic
14
        } else {
15
          return <div>{x.value}</div>; // no key, emits diagnostic
16
        }
17
      })}
18

19
      {/* switch statements */}
20
      {data.map((x) => {
21
        switch (x.type) {
22
          case "string":
23
            return <div>{x.value}</div>; // no key, emits diagnostic
24
          case "number":
25
            return <div>{x.value}</div>; // no key, emits diagnostic
26
          default:
27
            return <div key={x.value}>{x.value}</div>;
28
        }
29
      })}
30
    </>
31
  );
32
};

Fixed #4121: The CSS formatter no longer indents a selector when it has leading comments.
Fixed an issue where react lint rules could panic Biome when some incorrect code was analyzed.
Fixed #4982: the JavaScript parser now throws a syntax error for the following code:
```
1
type T = import;
2
type U = typeof import;
```
Fixed a bug with the --verbose CLI flag. Now the printed paths are relative to the working directory.
Fixed noNoninteractiveElementToInteractiveRole mistakenly flagging <li role="treeitem">,
Fixed #4622: Our JavaScript parser can now gracefully handle situations where we detect the parser to have stalled.

This means we don’t fail with an assertion anymore, but invalid code can trigger a regular diagnostic in such cases.
Fixed #342: The JavaScript parser now correctly handles invalid object member names, such as:
```
1
({
2
  params: { [paramName: string]: number } = {}
3
})
```
Fixed #6211: previously the import organizer emitted broken code when it merged an import at the start of the file with another import and placed the merged result after a third import.

The following code is now correctly organized:
```
1
import { B } from "bc";
2
import { C } from "bc";
3
import { A } from "a";
4
import { B, C } from "bc";
```
Fixed #4334: The formatter no longer inserts trailing a comma inside dynamic import expressions.
Fixed #5629: useHookAtTopLevel no longer report false-positives where the hook is at the top-level in a class method.
Fixed #5900: biome migrate eslint now support a nested files property in ESLint flat configs.
Fixed #3895: noUnusedImports no longer reports used values imported as types in an external module.
Fixed a case where the code fix for noUselessFragments would remove more than just the fragment.
Fixed #5919. Now Biome correctly loads the configuration passed via --config-path when its path starts with ./ e.g. --confi-path=./project/biome.json

Fixed #5031: CSS formatting has been improved for numbers:

1
.class {
2
  padding: .5em;
3
  marding: 1.0;
4
  padding: 0.5em;
5
  marding: 1;
6
}

Fixed #5989 where large octal escape sequences led to an overflow.
Implement improved error handling for the supports at rule
Fix #5053, now the rule correctly handles console.log inside arrow function expressions.
Fix #6105: css lint rules useSortedProperties should skip unknown properties.
Fixed #3229: Made formatting of compound selectors more consistent.
Fixed a bug where passing --max-diagnostics=0 would return a zero code even when errors were emitted.
Fixed a bug where Biome didn’t report any error when --stdin-file-path didn’t have any extension. Now Biome returns an error if --stdin-file-path doesn’t have an extension.
Fixed #5601: The useSortedClasses rule now properly preserves the original JSX quote style when sorting utility classes, preventing syntax errors.
The fix for useSelfClosingElements was marked as safe and the error message was improved.
Fixed overrides that include language-specific settings from having an effect for some languages
Fixed #6144: noUnusedImports reported incorrectly imports that were used as the type of parameters with the same name. In the following code, the import name was reported as unused.
```
1
import name from "mod";
2
function f(name: name.Readable): void {}
```

The lint rules useNamingConvention and useFilenamingConvention now accept character escapes at the start of a regex group.

Both these rules provide options that allow matching names against a regular expression. Previously, an escaped character at the start of a regex group reported an error. They are now accepted.

For example, the following configuration is now valid doesn’t emit an error anymore.

1
{
2
  "linter": {
3
    "rules": {
4
      "style": {
5
        "useNamingConvention": {
6
          "level": "on",
7
          "options": {
8
            "conventions": [
9
              {
10
                "selector": {
11
                  "kind": "let"
12
                },
13
                "match": "(\\n.*)"
14
              }
15
            ]
16
          }
17
        }
18
      }
19
    }
20
  }
21
}

Fixed #5617: noDuplicateObjectKeys now transfers the leading comments of the removed member.
Fixed #5409: noParameterAssign now reports reassigned parameter of unparenthesized arrow functions.

The following code is now reported as invalid.
```
1
const f = (param) => {
2
  param = {}; // Reassigning a function parameter is confusing.
3
};
```
Fixed #4875: Relative file paths are now clickable in the Jetbrains IDE terminal.
Fixed #4719: bracketSameLine now performs as expected when a comment is placed before the last JSX attribute.
Fixed #4564: Biome no longer panics when a multi-byte character is found in a unicode escape sequence.
Fixed #4950: Resolved a false positive of character class range operators in regular expressions.
Fixed handling of top-level variables by useExplicitType rule (#5932). Biome now allows all variables with explicit annotations, as well as variables with trivial RHS. Biome no longer emits duplicated errors when an untyped function is assigned to an untyped variable.
Fixed #4947: The useTemplate lint rule now ignores concatenated literals folded to multiple lines.
Fixed #4568: Broken import statements no longer can cause a panic in useExhaustiveDependencies.
Fixed #6042: noUselessEscapeInString now reports useless escapes after skipping ${ in template literals.
Fixed #6229 where the fix of noUnusedImports emitted an invalid syntax. Now the following case emits a code fix that is syntactically correct:
```
1
import Used, { NotUsed } from "foo";
2

3
Used();
```
Fix #5682: Object patterns with a nested assignment pattern no longer break properties.

For example, the following code:
```
1
const { foo: { bar } = { bar: false } } = props;
```
is used to be formatted into:
```
1
const { foo: { bar } = { bar: false } } = props;
```
, while Prettier does not expand properties in this case.
Fixed #5620, noConsole rule now correctly handles indirect console.log calls and references.
When pulling code actions from the LSP, now the first choice suggested by the client will be the safe fix.
Fixed #6022, now the rule noDuplicateProperties doesn’t trigger properties defined inside the @keyframes at rule
Enhanced the error message of the diagnostics emitted when Biome can’t parse a suppression comment.
Fixed link to the docs inside CLI markup
Fixed a bug where a suppression comment with an empty explanation was valid.

Now a suppression comment // biome-ignore lint: will raise a warning diagnostic.
Fixed #4026: Comments in grid-template are no longer moved by the formatter.
Fixed #3394: Resolved a false positive in useSortedClasses.
Fixed #342 and #4562: Biome no longer crashes when a declare statement is followed by an unexpected token.
Fixed false positive in the rule noUnknownFunction where the tech function was incorrectly flagged as an unknown function.
Fixed #4511: noLabelWithoutControl now detects <button> tags as input.
Fixed #6039: noUselessEscapeInString no longer reports \${ escape in template literals.
Fixed #5985, which caused the import organizer to fail the merging of a default import with a named import. The following code is now correctly organized:
```
1
import moment from 'moment';
2
import { Moment } from 'moment';
3
import moment, { Moment } from 'moment';
```
Fixed an issue where the explain command didn’t the diagnostic category when a rule was explained.
Improved the diagnostic of the rule noUnusedVariables. The rule message now provides the name of the unused binding.
Added RegExpStringIterator to the analyzer globals.
Fixed #4208: noUselessFragments now handles JsxAttributeInitializerClause, ensuring that fragments inside expressions like <A b=<></> /> are preserved.
Fixed #4533: noUnknownPseudoClass no longer reports pseudo classes after a webkit scrollbar pseudo element.

The following code will no longer report a diagnostic:
```
1
::-webkit-scrollbar-thumb:hover {
2
}
```
Updates the useJsxKeyInIterable rule to more closely match the behavior of the ESLint plugin (e.g. mark the whole fragment as incorrect when no key is present). This also adds the option to check shorthand fragments ( <></>)
Renamed the rule noDuplicatedFields to noDuplicateFields. Run the command biome migrate to update your configuration.
Fixed an issue where ignored files were incorrectly tracked by the Daemon.
Fixed #5116: noUnknownPseudoElement now supports ::slotted.
Fixed #5979: biome search now correctly skips files that don’t match the pattern’s target language.
Fixed #4323: Fixed the case where useSemanticElement accidentally showed recommendations for role="searchbox" instead of role="search".
Support setting indent_size to tab in .editorconfig, the following config will not cause error:
```
1
root = true
2
[*]
3
indent_size = tab
```
Fixed #4565: noControlCharactersInRegex no longer panics when it encounters an unterminated unicode escape sequence.
Fixed #5770, Biome’s configuration file is now respected by the migrate command during migration
Fixed an issue where the lexer didn’t report errors for unterminated regex or string literals, such as the following cases:
```
1
"string
2
'str
3
/\\217483
```
The useKeyWithClickEvents rule has been improved with better support for ARIA roles.

Key improvements:
1. Accessibility checks:
  
  Now the rule correctly handles the following cases:
  - If an element is hidden from screen readers
  - If an element has the presentation role
  - If an element is interactive
```
1
// No errors
2
<div aria-hidden="true" onClick={() => {}} /> // hidden from screen reader
3
<div role="presentation" onClick={() => {}} /> // presentation role
4
<button onClick={() => {}} /> // interactive role
```
  This change ensures the rule is more accurate and helpful.
2. Checks spread syntax:
  
  Spread syntax used to be ignored, but has been changed to be pointed out for more stringent checking.
```
1
// Errors
2
<div {...props} onClick={() => {}} />
3
// No errors
4
<div {...props} onClick={() => {}} onKeyDown={foo} />;
```
3. Refactor:
  
  Now the rule uses the aria roles to determine if an element is interactive.
  
  The changes shown here are meant to be closer to the original jsx-eslint’s click-events-have-key-events rule.
Fixed #6029: A new line before the semicolon in the previous statement is now kept after formatting.

For example, the following code:
```
1
const foo = 3;
2

3
[1, 2, 3].map((x) => x * 2);
```
when javascript.formatter.semicolons is always, it becomes:
```
1
const foo = 3;
2

3
[1, 2, 3].map((x) => x * 2);
```
when javascript.formatter.semicolons is asNeeded, the original code is considered as already formatted.
useArrayLiterals now reports all expressions using the Array constructors.

Previously, the rule reported only use of the Array constructor in expressions statements.
```
1
// This was reported
2
new Array();
3
// This was not reported
4
const xs = new Array();
```
Improved error handling for the container at-rule.
Fixed #4665: the LSP previously identified .cjs files as ESM files, making rules like noRedundantUseStrict reports incorrectly valid "use strict" directives.
Fixed #5382: useExportType no longer reports an identifier that bound by both a variable and a type.
Fixed #5826: useNumericSeparators no longer reports single-digit 0.

Fixed #5307, where CSS value lists were wrapped in a way that did not preserve semantic structure.

Biome now ensures that CSS value lists follow a more readable format, aligning with Prettier’s behavior.

Before:

1
* {
2
  box-shadow:
3
    0 0 0 1px #fff,
4
    0 0 0 3.2px rgba(89, 89, 235, 0.25),
5
    0 0 0 3.2px rgba(89, 89, 235, 0.25),
6
    0 0 0 3.2px red,
7
    0 0 0 3.2px rgba(89, 89, 235, 0.25);
8
}

After:

1
* {
2
  box-shadow:
3
    0 0 0 1px #fff,
4
    0 0 0 3.2px rgba(89, 89, 235, 0.25),
5
    0 0 0 3.2px rgba(89, 89, 235, 0.25),
6
    0 0 0 3.2px red,
7
    0 0 0 3.2px rgba(89, 89, 235, 0.25);
8
}

tsconfig.*.json files will now be treated the same as tsconfig.json files.
The summary reporter now prints the files processed and the files fixed when passing the --verbose flag.
Fixed #5693: useRegexLiterals now correctly handle useless escaped character in string literals.
useRegexLiterals now suggests a correct fix when the pattern contains an escaped anti-slash \/.

Previously the rule suggested the following fix that led to a syntax error:
```
1
new RegExp("\/");
2
/\\//
```
The rule now suggests a correct fix:
```
1
new RegExp("\/");
2
/\//
```
Fixed #5487.
Fixed useConsistentCurlyBraces breaks react/no-unescaped-entities rule

Added a check for forbidden characters: >, ", ' and }. If any of these characters are detected, curly braces will be preserved.

Example:
```
1
function MyComponent() {
2
  return <Foo>Jupiter {">"} Venus</Foo>;
3
}
```

The rule useNamingConvention now suggests a rename that preserves uppercase if possible.

For instance, Biome suggested renaming HTMLWrapper as htmlWrapper:

1
import HTMLWrapper from "HTMLWrapper.tsx";
2
import htmlWrapper from "HTMLWrapper.tsx";
3

4
function component() {
5
  return <HTMLWrapper> </HTMLWrapper>;
6
  return <htmlWrapper> </HTMLWrapper>;
7
}

Since both PascalCase and CamelCase are accepted, Biome now suggests renaming HTMLWrapper as HtmlWrapper:

1
import HTMLWrapper from "HTMLWrapper.tsx";
2
import HtmlWrapper from "HTMLWrapper.tsx";
3

4
function component() {
5
  return <HTMLWrapper> </HTMLWrapper>;
6
  return <HtmlWrapper> </HTMLWrapper>;
7
}

Fix a parsing error when a JsxElementName is JsxMemberExpression, and a JsLogicalExpression before it without a semicolon.

The following case will now not throw error:

1
import React from "react";
2

3
let b = 0;
4

5
function A() {
6
  const a = b > 0 && b < 1;
7

8
  return <React.Fragment>{a}</React.Fragment>;
9
}

Fixed Biome being unable to parse insert_final_newline = unset in EditorConfig files.
Fixed #4530: useArrowFunction now preserves directives.

Previously the rule removed the directives when a function expression was turned into an arrow function. The rule now correctly keeps the directives.
```
1
const withDirective = function () {
2
const withDirective = () => {
3
  "use server";
4
  return 0;
5
}
```
Fixed #4855: useSortedClasses now suggests code fixes that match the JSX quote style of the formatter.