All versions since 2.3.7

2.3.7

Patch Changes

#8169 7fdcec8 Thanks @arendjr! - Fixed #7999: Correctly place await after leading comment in auto-fix action from noFloatingPromises rule.
#8157 12d5b42 Thanks @Conaclos! - Fixed #8148. noInvalidUseBeforeDeclaration no longer reports some valid use before declarations.

The following code is no longer reported as invalid:
```
1
class classA {
2
  C = C;
3
}
4
const C = 0;
```
#8178 6ba4157 Thanks @dyc3! - Fixed #8174, where the HTML parser would parse 2 directives as a single directive because it would not reject whitespace in Vue directives. This would cause the formatter to erroneously merge the 2 directives into one, resulting in broken code.
```
1
<Component v-else:property="123" />
2
<Component v-else :property="123" />
```
#8088 0eb08e8 Thanks @db295! - Fixed #7876: The noUnusedImports rule now ignores imports that are used by @linkcode and @linkplain (previously supported @link and @see).

The following code will no longer be a false positive:
```
1
import type { a } from "a"
2

3
/**
4
 * {@linkcode a}
5
 */
6
function func() {}
```
#8119 8d64655 Thanks @ematipico! - Improved the detection of the rule noUnnecessaryConditions. Now the rule isn’t triggered for variables that are mutated inside a module.

This logic deviates from the original rule, hence noUnnecessaryConditions is now marked as “inspired”.

In the following example, hey starts as false, but then it’s assigned to a string. The rule isn’t triggered inside the if check.
```
1
let hey = false;
2

3
function test() {
4
  hey = "string";
5
}
6

7
if (hey) {
8
}
```
#8149 e0a02bf Thanks @Netail! - Fixed #8144: Improve noSyncScripts, ignore script tags with type="module" as these are always non-blocking.
#8182 e9f068e Thanks @hirokiokada77! - Fixed #7877: Range suppressions now handle suppressed categories properly.

Valid:
```
1
// biome-ignore-start lint: explanation
2
const foo = 1;
3
// biome-ignore-end lint: explanation
```
#8111 bf1a836 Thanks @ryan-m-walker! - Added support for parsing and formatting the CSS if function.

Example
```
1
.basic-style {
2
  color: if(style(--scheme: dark): #eeeeee; else: #000000;);
3
}
```
#8173 7fc07c1 Thanks @ematipico! - Fixed #8138 by reverting an internal refactor that caused a regression to the rule noUnusedPrivateClassMembers.
#8119 8d64655 Thanks @ematipico! - Improved the type inference engine, by resolving types for variables that are assigned to multiple values.
#8158 fb1458b Thanks @dyc3! - Added the useVueValidVText lint rule to enforce valid v-text directives. The rule reports when v-text has an argument, has modifiers, or is missing a value.

Invalid:
```
1
<div v-text />
2

3
<div v-text:aaa="foo" />
4

5
<div v-text.bbb="foo" />
6

```
#8158 fb1458b Thanks @dyc3! - Fixed useVueValidVHtml so that it will now flag empty strings, e.g. v-html=""
#7078 bb7a15c Thanks @emilyinure! - Fixed #6675: Now only flags noAccumulatingSpread on Object.assign when a new object is being allocated on each iteration. Before, all cases using Object.assign with reduce parameters were warned despite not making new allocations.

The following code will no longer be a false positive:
```
1
foo.reduce((acc, bar) => Object.assign(acc, bar), {});
```
The following cases which do make new allocations will continue to warn:
```
1
foo.reduce((acc, bar) => Object.assign({}, acc, bar), {});
```
#8175 0c8349e Thanks @ryan-m-walker! - Fixed CSS formatting of dimension units to use correct casing for Q, Hz and kHz.

Before:
```
1
.cssUnits {
2
  a: 1Q;
3
  b: 1Hz;
4
  c: 1kHz;
5
}
```
After:
```
1
.cssUnits {
2
  a: 1Q;
3
  b: 1Hz;
4
  c: 1kHz;
5
}
```

2.3.8 Latest

Patch Changes

#8188 4ca088c Thanks @ematipico! - Fixed #7390, where Biome couldn’t apply the correct configuration passed via --config-path.

If you have multiple root configuration files, running any command with --config-path will now apply the chosen configuration file.
#8171 79adaea Thanks @dibashthapa! - Added the new rule noLeakedRender. This rule helps prevent potential leaks when rendering components that use binary expressions or ternaries.

For example, the following code triggers the rule because the component would render 0:
```
1
const Component = () => {
2
  const count = 0;
3
  return <div>{count && <span>Count: {count}</span>}</div>;
4
};
```
#8116 b537918 Thanks @Netail! - Added the nursery rule noDuplicatedSpreadProps. Disallow JSX prop spreading the same identifier multiple times.

Invalid:
```
1
<div {...props} something="else" {...props} />
```
#8256 f1e4696 Thanks @cormacrelf! - Fixed a bug where logs were discarded (the kind from --log-level=info etc.). This is a regression introduced after an internal refactor that wasn’t adequately tested.
#8226 3f19b52 Thanks @dyc3! - Fixed #8222: The HTML parser, with Vue directives enabled, can now parse v-slot shorthand syntax, e.g. <template #foo>.
#8007 182ecdc Thanks @brandonmcconnell! - Added support for dollar-sign-prefixed filenames in the useFilenamingConvention rule.

Biome now allows filenames starting with the dollar-sign (e.g. $postId.tsx) by default to support naming conventions used by frameworks such as TanStack Start for file-based-routing.
#8218 91484d1 Thanks @hirokiokada77! - Added the noMultiStr rule, which disallows creating multiline strings by escaping newlines.

Invalid:
```
1
const foo =
2
  "Line 1\n\
3
Line 2";
```
Valid:
```
1
const foo = "Line 1\nLine 2";
2
const bar = `Line 1
3
Line 2`;
```

#8225 98ca2ae Thanks @ongyuxing! - Fixed #7806: Prefer breaking after the assignment operator for conditional types with generic parameters to match Prettier.

1
type True = unknown extends Type<
2
  "many",
3
  "generic",
4
  "parameters",
5
  "one",
6
  "two",
7
  "three"
8
>
9
  ? true
10
  : false;
11
type True =
12
  unknown extends Type<"many", "generic", "parameters", "one", "two", "three">
13
    ? true
14
    : false;

#6765 23f7855 Thanks @emilyinure! - Fixed #6569: Allow files to export from themselves with noImportCycles.

This means the following is now allowed:

1
export function example() {
2
  return 1;
3
}
4

5
// Re-exports all named exports from the current module under a single namespace
6
// and then imports the namespace from the current module.
7
// Allows for encapsulating functions/variables into a namespace instead
8
// of using a static class.
9
export * as Example from "./example.js";
10

11
import { Example } from "./example.js";

#8214 68c052e Thanks @hirokiokada77! - Added the noEqualsToNull rule, which enforces the use of === and !== for comparison with null instead of == or !=.

Invalid:
```
1
foo == null;
2
foo != null;
```
Valid:
```
1
foo === null;
2
foo !== null;
```
#8219 793bb9a Thanks @dyc3! - Fixed #8190: The HTML parser will now parse Vue event handlers that contain : correctly, e.g. @update:modelValue="onUpdate".
#8259 4a9139b Thanks @hirokiokada77! - Fixed #8254: The noParameterAssign rule with propertyAssignment: "deny" was incorrectly reporting an error when a function parameter was used on the right-hand side of an assignment to a local variable’s property.

The rule should only flag assignments that modify the parameter binding or its properties (L-value), not the use of its value.

Valid:
```
1
(input) => {
2
  const local = { property: 0 };
3
  local.property = input;
4
};
```
#8201 cd2edd7 Thanks @Netail! - Added the nursery rule noTernary. Disallow ternary operators.

Invalid:
```
1
const foo = isBar ? baz : qux;
```
#8172 de98933 Thanks @JeremyMoeglich! - Fixed #8145: handling of large hex literals, which previously caused both false positives and false negatives.

This affects noPrecisionLoss and noConstantMathMinMaxClamp.
#8210 7b44e9e Thanks @Netail! - Corrected rule source reference. biome migrate eslint should do a bit better detecting rules in your eslint configurations.
#8213 e430555 Thanks @ruidosujeira! - Fixed #8209: Recognized formatting capability when either range or on-type formatting is supported, not only full-file formatting. This ensures editors and the language server correctly detect formatting support in files like JSONC.
#8202 6f49d95 Thanks @hirokiokada77! - Fixed #8079: Properly handle name and value metavariables for JsxAttribute GritQL queries.

The following biome search command no longer throws an error:
```
1
biome search 'JsxAttribute($name, $value) as $attr where { $name <: "style" }'
```
#8276 f7e836f Thanks @hirokiokada77! - Added the noProto rule, which disallows the use of the __proto__ property for getting or setting the prototype of an object.

Invalid:
```
1
obj.__proto__ = a;
2
const b = obj.__proto__;
```
Valid:
```
1
const a = Object.getPrototypeOf(obj);
2
Object.setPrototypeOf(obj, b);
```