Version History

All versions All versions forward

Version 2.1.4

Patch Changes

#7121 b9642ab Thanks @arendjr! - Fixed #7111: Imported symbols using aliases are now correctly recognised.
#7103 80515ec Thanks @omasakun! - Fixed #6933 and #6994.

When the values of private member assignment expressions, increment expressions, etc. are used, those private members are no longer marked as unused.
#6887 0cc38f5 Thanks @ptkagori! - Added the noQwikUseVisibleTask rule to Qwik.

This rule is intended for use in Qwik applications to warn about the use of useVisibleTask$() functions which require careful consideration before use.

Invalid:
```
1
useVisibleTask$(() => {
2
  console.log("Component is visible");
3
});
```
Valid:
```
1
useTask$(() => {
2
  console.log("Task executed");
3
});
```
#7084 50ca155 Thanks @ematipico! - Added the new nursery rule noUnnecessararyConditions, which detects whenever some conditions don’t change during the life cycle of the program, and truthy or false, hence deemed redundant.

For example, the following snippets will trigger the rule:
```
1
// Always truthy literal conditions
2
if (true) {
3
  console.log("always runs");
4
}
```
```
1
// Unnecessary condition on constrained string type
2
function foo(arg: "bar" | "baz") {
3
  if (arg) {
4
    // This check is unnecessary
5
  }
6
}
```
#6887 0cc38f5 Thanks @ptkagori! - Added the useImageSize rule to Biome.

The useImageSize rule enforces the use of width and height attributes on <img> elements for performance reasons. This rule is intended to prevent layout shifts and improve Core Web Vitals by ensuring images have explicit dimensions.

Invalid:
```
1
<img src="/image.png" />
2
<img src="https://example.com/image.png" />
3
<img src="/image.png" width="200" />
4
<img src="/image.png" height="200" />
```
Valid:
```
1
<img width="200" height="600" src="/static/images/portrait-01.webp" />
2
<img width="100" height="100" src="https://example.com/image.png" />
```
#6887 0cc38f5 Thanks @ptkagori! - Added the useAnchorHref rule to Biome.

The useAnchorHref rule enforces the presence of an href attribute on <a> elements in JSX. This rule is intended to ensure that anchor elements are always valid and accessible.

Invalid:
```
1
<a>Link</a>
```
```
1
<a target="_blank">External</a>
```
Valid:
```
1
<a href="/home">Home</a>
```
```
1
<a href="https://example.com" target="_blank">
2
  External
3
</a>
```
#7100 29fcb05 Thanks @Jayllyz! - Added the rule noNonNullAssertedOptionalChain.

This rule prevents the use of non-null assertions (!) immediately after optional chaining expressions (?.). Optional chaining is designed to safely handle nullable values by returning undefined when the chain encounters null or undefined. Using a non-null assertion defeats this purpose and can lead to runtime errors.
```
1
// Invalid - non-null assertion after optional chaining
2
obj?.prop!;
3
obj?.method()!;
4
obj?.[key]!;
5
obj?.prop!;
6

7
// Valid - proper optional chaining usage
8
obj?.prop;
9
obj?.method();
10
obj?.prop ?? defaultValue;
11
obj!.prop?.method();
```
#7129 9f4538a Thanks @drwpow! - Removed option, combobox, listbox roles from useSemanticElements suggestions
#7106 236deaa Thanks @arendjr! - Fixed #6985: Inference of return types no longer mistakenly picks up return types of nested functions.
#7102 d3118c6 Thanks @omasakun! - Fixed #7101: noUnusedPrivateClassMembers now handles members declared as part of constructor arguments:
1. If a class member defined in a constructor argument is only used within the constructor, it removes the private modifier and makes it a plain method argument.
2. If it is not used at all, it will prefix it with an underscore, similar to noUnusedFunctionParameter.
#7104 5395297 Thanks @harxki! - Reverting to prevent regressions around ref handling
#7143 1a6933a Thanks @siketyan! - Fixed #6799: The noImportCycles rule now ignores type-only imports if the new ignoreTypes option is enabled (enabled by default).
[!WARNING] Breaking Change: The noImportCycles rule no longer detects import cycles that include one or more type-only imports by default. To keep the old behaviour, you can turn off the ignoreTypes option explicitly:
```
1
{
2
  "linter": {
3
    "rules": {
4
      "nursery": {
5
        "noImportCycles": {
6
          "options": {
7
            "ignoreTypes": false
8
          }
9
        }
10
      }
11
    }
12
  }
13
}
```
#7099 6cc84cb Thanks @arendjr! - Fixed #7062: Biome now correctly considers extended configs when determining the mode for the scanner.
#6887 0cc38f5 Thanks @ptkagori! - Added the useQwikClasslist rule to Biome.

This rule is intended for use in Qwik applications to encourage the use of the built-in class prop (which accepts a string, object, or array) instead of the classnames utility library.

Invalid:
```
1
<div class={classnames({ active: true, disabled: false })} />
```
Valid:
```
1
<div classlist={{ active: true, disabled: false }} />
```
#7019 57c15e6 Thanks @fireairforce! - Added support in the JS parser for import source(a stage3 proposal). The syntax looks like:
```
1
import source foo from "<specifier>";
```
#7053 655049e Thanks @jakeleventhal! - Added the useConsistentTypeDefinitions rule.

This rule enforces consistent usage of either interface or type for object type definitions in TypeScript.

The rule accepts an option to specify the preferred style:
- interface (default): Prefer using interface for object type definitions
- type: Prefer using type for object type definitions
Examples:
```
1
// With default option (interface)
2
// ❌ Invalid
3
type Point = { x: number; y: number };
4

5
// ✅ Valid
6
interface Point {
7
  x: number;
8
  y: number;
9
}
10

11
// With option { style: "type" }
12
// ❌ Invalid
13
interface Point {
14
  x: number;
15
  y: number;
16
}
17

18
// ✅ Valid
19
type Point = { x: number; y: number };
```
The rule will automatically fix simple cases where conversion is straightforward.