Version History

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