All versions since 2.3.12

2.3.12

Patch Changes

#8653 047576d Thanks @dyc3! - Added new nursery rule noDuplicateAttributes to forbid duplicate attributes in HTML elements.
#8648 96d09f4 Thanks @BaeSeokJae! - Added a new nursery rule noVueOptionsApi.

Biome now reports Vue Options API usage, which is incompatible with Vue 3.6’s Vapor Mode. This rule detects Options API patterns in <script> blocks, defineComponent(), and createApp() calls, helping prepare codebases for Vapor Mode adoption.

For example, the following now triggers this rule:
```
1
<script>
2
export default {
3
  data() {
4
    return { count: 0 };
5
  },
6
};
7
</script>
```
#8832 b08270b Thanks @Exudev! - Fixed #8809, #7985, and #8136: the noSecrets rule no longer reports false positives on common CamelCase identifiers like paddingBottom, backgroundColor, unhandledRejection, uncaughtException, and IngestGatewayLogGroup.

The entropy calculation algorithm now uses “average run length” to distinguish between legitimate CamelCase patterns (which have longer runs of same-case letters) and suspicious alternating case patterns (which have short runs).
#8793 c19fb0e Thanks @TheBaconWizard! - Properly handle parameters metavariables for arrow_function GritQL queries. The following biome search command no longer throws an error:
Terminal window
```
1
biome search 'arrow_function(parameters=$parameters, body=$body)'
```
#8561 981affb Thanks @wataryooou! - Fixed noUnusedVariables to ignore type parameters declared in ambient contexts such as declare module blocks.
#8817 652cfbb Thanks @dyc3! - Fixed #8765: The HTML parser can now parse directive modifiers with a single colon, e.g. @keydown.:.
#8704 a1914d4 Thanks @Netail! - Added the nursery rule noRootType. Disallow the usage of specified root types. (e.g. mutation and/or subscription)

Invalid:
```
1
{
2
  "options": {
3
    "disallow": ["mutation"]
4
  }
5
}
```
```
1
type Mutation {
2
  SetMessage(message: String): String
3
}
```
#8712 251b47b Thanks @Netail! - Renamed the following GraphQL nursery rules to match the Biome standard:
- useUniqueArgumentNames -> noDuplicateArgumentNames
- useUniqueFieldDefinitionNames -> noDuplicateFieldDefinitionNames
- useUniqueGraphqlOperationName -> noDuplicateGraphqlOperationName
- useUniqueInputFieldNames -> noDuplicateInputFieldNames
- useUniqueVariableNames -> noDuplicateVariableNames
Run the biome migrate --write command to automatically update the configuration file.
#7602 957cd8e Thanks @kedevked! - Added the nursery lint rule useErrorCause.

This rule enforces that errors caught in a catch clause are not rethrown without wrapping them in a new Error object and specifying the original error as the cause. This helps preserve the error’s stack trace and context for better debugging.

It can be configured with the following option:
- requireCatchParameter: (default: true)
  - When true, the rule requires that catch clauses have a parameter. If a throw statement appears inside a catch clause without a parameter, it will be flagged.
Invalid examples:
```
1
try {
2
  foo();
3
} catch {
4
  throw new Error("fail");
5
}
```
```
1
try {
2
  foo();
3
} catch (err) {
4
  throw new Error(err.message);
5
}
```
Valid examples:
```
1
try {
2
  foo();
3
} catch (err) {
4
  throw new Error("fail", { cause: err });
5
}
```
```
1
try {
2
  foo();
3
} catch (error) {
4
  throw new Error("Something went wrong", { cause: error });
5
}
```
Valid example when requireCatchParameter is false:

Valid:
```
1
try {
2
  foo();
3
} catch {
4
  throw new Error("fail");
5
}
```
#8725 95aba98 Thanks @dyc3! - Fixed #8715: The CSS parser will now recover slightly better if a semicolon is missing from Tailwind’s @apply at-rule.
#8616 4ee3bda Thanks @Netail! - Added the nursery rule useLoneAnonymousOperation. Disallow anonymous operations when more than one operation specified in document.

Invalid:
```
1
query {
2
  fieldA
3
}
4

5
query B {
6
  fieldB
7
}
```
#8624 291c9f2 Thanks @taga3s! - Added the nursery rule useInlineScriptId to the Next.js domain. This rule enforces id attribute on next/script components with inline content or dangerouslySetInnerHTML.

The following code is invalid:
```
1
import Script from "next/script";
2

3
export default function Page() {
4
  return (
5
    <Script>{`console.log('Hello');`}</Script> // must have `id` attribute
6
  );
7
}
```

#8767 0d15370 Thanks @mdevils! - Fixed #3512: useExhaustiveDependencies now properly handles nested destructuring patterns from hook results.

1
const [[x, y], setXY] = useState([1, 2]);
2
useEffect(() => {
3
  console.log(x, y);
4
}, [x, y]); // x and y are now correctly recognized as unstable

#8757 17ed9d3 Thanks @Netail! - Added the nursery rule noDivRegex. Disallow equal signs explicitly at the beginning of regular expressions.

Invalid:
```
1
var f = function () {
2
  return /=foo/;
3
};
```
#8836 aab1d17 Thanks @dyc3! - Fixed #7858: Biome now parses Astro files with empty frontmatter blocks.
#8755 3a15c29 Thanks @arturalkaim! - Fixed #6670. The $filename metavariable can now be used in GritQL where clauses to filter matches by filename.
#8821 63e68a1 Thanks @playhardgopro! - Fixed several bugs in Vue conditional rules (useVueValidVIf, useVueValidVElse, and useVueValidVElseIf) related to whitespace handling, newlines, and self-closing tags.
#8767 0d15370 Thanks @mdevils! - Fixed #3685: useExhaustiveDependencies now properly handles transparent expression wrappers like non-null assertions and type assertions in dependency comparisons.
```
1
useMemo(() => Boolean(myObj!.x), [myObj!.x]); // No longer reports incorrect diagnostics
2
useMemo(() => myObj!.x?.y === true, [myObj!.x?.y]); // Now correctly matches dependencies
```
#8597 f764007 Thanks @Netail! - Added the nursery rule noDuplicateEnumValueNames. Enforce unique enum value names.

Invalid:
```
1
enum A {
2
  TEST
3
  TesT
4
}
```
#8679 33dfd7c Thanks @ematipico! - Fixed #8678. Now Biome correctly parses components inside Vue, Svelte and Astro files when they have the same name of self-closing elements.
#8617 31a9bfe Thanks @Netail! - Added the nursery rule useLoneExecutableDefinition. Require queries, mutations, subscriptions or fragments to be located in separate files.

Invalid:
```
1
query Foo {
2
  id
3
}
4

5
fragment Bar on Baz {
6
  id
7
}
```
#8697 8519669 Thanks @Faizanq! - Added the nursery lint rule noExcessiveLinesPerFile to CSS and GraphQL.
#8711 365f7aa Thanks @Netail! - Added new nursery rule noDuplicateEnumValues, which disallows defining an enum with multiple members initialized to the same value.
#8767 0d15370 Thanks @mdevils! - Fixed #5914: useExhaustiveDependencies now properly handles variables declared in the same statement.
```
1
const varA = Math.random(),
2
  varB = useMemo(() => varA, [varA]); // varA is now correctly recognized as needed
```
#8767 0d15370 Thanks @mdevils! - Fixed #8427: useExhaustiveDependencies now properly resolves variable references to detect captured dependencies.
```
1
const fe = fetchEntity;
2
useEffect(() => {
3
  fe(id);
4
}, [id, fe]); // fe is now correctly detected as needed
```

#8767 0d15370 Thanks @mdevils! - Fixed #8484: useExhaustiveDependencies now properly handles member access on stable hook results.

1
const stableObj = useStable();
2
useMemo(() => {
3
  return stableObj.stableValue; // stableObj.stableValue is now correctly recognized as stable
4
}, []);

#8767 0d15370 Thanks @mdevils! - Fixed #7982: useExhaustiveDependencies now properly handles callback expressions with type assertions.

1
const callback = useCallback(
2
  (() => {
3
    return count * 2;
4
  }) as Function,
5
  [count], // count is now correctly detected
6
);

#8766 39eb545 Thanks @Netail! - Fixed #8761: Reverted wrapping the URL of rule descriptions with <>, causing broken URLs in VSCode.
#8767 0d15370 Thanks @mdevils! - Fixed #3080: useExhaustiveDependencies now properly analyzes captures within referenced functions passed to hooks.
```
1
function myEffect() {
2
  console.log(foo, bar);
3
}
4
useEffect(myEffect, [foo, bar]); // foo and bar are now correctly detected
```
#8740 4962ed0 Thanks @Netail! - Extra rule source references. biome migrate eslint should do a bit better detecting rules in your eslint configurations.
#8776 395746f Thanks @codiini! - Fixed #6003: noUselessUndefinedInitialization no longer reports exported variables initialized to undefined. In Svelte 4, this pattern is used to declare optional component props.
#8767 0d15370 Thanks @mdevils! - Fixed #4248: useExhaustiveDependencies now correctly handles function props passed as callbacks.
```
1
const data = React.useMemo(getData, [getData]); // getData is now correctly recognized as needed
```
#8819 bc191ff Thanks @Netail! - Fixed #6567: noUnknownProperty now ignores unknown properties in at-rules which support descriptors.
#8787 adb652f Thanks @tuyuritio! - Fixed #8777: Add support for :active-view-transition pseudo-class.
#8639 6577e32 Thanks @ohnoah! - Added the nursery lint rule noExcessiveLinesPerFile. Biome now reports files that exceed a configurable line limit.
```
1
// maxLines: 2
2
const a = 1;
3
const b = 2;
4
const c = 3;
```
#8753 71b5c6e Thanks @Netail! - Added the nursery rule noExcessiveClassesPerFile. Enforce a maximum number of classes per file.

Invalid:
```
1
class Foo {}
2
class Bar {}
```
#8754 d6b2bda Thanks @Netail! - Added the nursery rule noFloatingClasses. Disallow new operators outside of assignments or comparisons.

Invalid:
```
1
new Date();
```

2.3.13

Patch Changes

#8815 f924f23 Thanks @dyc3! - Improved useVueValidVOn to be more closely aligned with the source rule. It will now properly allow modifiers for all possible keyboard events. It should have better performance when there are no violations of the rule as well.

Now treated valid:
```
1
<div @keydown.arrow-down="handler"></div>
2
<div @keydown.a="handler"></div>
3
<div @keydown.b="handler"></div>
4
<div @keydown.27="foo"></div>
```
#8856 85f81f9 Thanks @dyc3! - Fixed #8710: Biome now parses Vue dynamic slot shorthand arguments that use template literals in [].
#8850 2a190e0 Thanks @dyc3! - Fixed #8708: Tailwind @utility directives now parse functional utility names like px-* when Tailwind directives are enabled.
#8863 79386e0 Thanks @dyc3! - Fixed an issue with biome migrate eslint where it couldn’t detect rules for CSS, GraphQL, and HTML.
#8771 6f56b6e Thanks @lghuahua! - Fix the --reporter=summary output incorrectly merging and displaying wrong issue counts for different rules. Fixes #8730
#8714 ac3a71f Thanks @Netail! - Added new nursery rule use-consistent-enum-value-type. This rule disallows enums from having both number and string members.

2.3.14 Latest

Patch Changes

#8921 29e2435 Thanks @siketyan! - Fixed #8759: The useConsistentTypeDefinitions rule no longer converts empty object type declarations into interfaces, as it will conflict with the noEmptyInterface rule and can cause an infinite loop when both rules are enabled.
#8928 ccaeac4 Thanks @taga3s! - Added the nursery rule useGlobalThis. This rule enforces using globalThis over window, self and global.
#8602 9a18daa Thanks @dyc3! - Added the new nursery rule noVueArrowFuncInWatch. This rule forbids using arrow functions in watchers in Vue components, because arrow functions do not give access to the component instance (via this), while regular functions do.
#8905 9b1eea8 Thanks @ryan-m-walker! - Fixed #8428: Improved parsing recovery when encountering qualified rules inside CSS @page at-rule blocks.
#8900 f788cff Thanks @mdevils! - Fixed #8802: useExhaustiveDependencies now correctly suggests dependencies without including callback-scoped variables or method names.

When accessing object properties with a callback-scoped variable, only the object path is suggested:
```
1
// Now correctly suggests `props.value` instead of `props.value[day]`
2
useMemo(() => {
3
  return WeekdayValues.filter((day) => props.value[day]);
4
}, [props.value]);
```
When calling methods on objects, only the object is suggested as a dependency:
```
1
// Now correctly suggests `props.data` instead of `props.data.forEach`
2
useMemo(() => {
3
  props.data.forEach((item) => console.log(item));
4
}, [props.data]);
```
#8913 e1e20ea Thanks @dyc3! - Fixed #8363: HTML parser no longer crashes when encountering a < character followed by a digit in text content (e.g., <12 months). The parser now correctly emits an “Unescaped < bracket character” error instead of treating <12 as a tag name and crashing.
#8910 2fb63a4 Thanks @dyc3! - Fixed #8774: Type aliases with generic parameters that have extends constraints now properly indent comments after the equals sign.

Previously, comments after the = in type aliases with extends constraints were not indented:
```
1
type A<B, C extends D> = // Some comment
2
undefined;
3
type A<B, C extends D> =
4
    // Some comment
5
    undefined;
```
#8916 ea4bd04 Thanks @ryan-m-walker! - Fixed #4013, where comments in member chains caused unnecessary line breaks.
```
1
// Before
2
aFunction.b().c.d();
3

4
// After
5
aFunction.b().c.d();
```

#8945 fa66fe3 Thanks @fireairforce! - Fixed #8354: Don’t remove quotes when type memeber is new.

1
// Input:
2
type X = {
3
  "new"(): string;
4
  "foo"(): string;
5
};
6

7
// Format Output:
8
type X = {
9
  "new()": string;
10
  foo(): string;
11
};

#8927 0ef3da5 Thanks @littleKitchen! - Fixed #8907: useExhaustiveDependencies now correctly recognizes stable hook results (like useState setters and useRef values) when declared with let.
#8931 4561751 Thanks @koshin01! - Added the new nursery rule noRedundantDefaultExport, which flags redundant default exports where the default export references the same identifier as a named export.

#8900 f788cff Thanks @mdevils! - Fixed #8883: useExhaustiveDependencies no longer produces false positives when props are destructured in the function body of arrow function components without parentheses around the parameter.

1
type Props = { msg: string };
2

3
// Arrow function without parentheses around `props`
4
const Component: React.FC<Props> = (props) => {
5
  const { msg } = props;
6
  // Previously, this incorrectly reported `msg` as unnecessary
7
  useEffect(() => console.log(msg), [msg]);
8
};

#8861 3531687 Thanks @dyc3! - Added the noDeprecatedMediaType CSS rule to flag deprecated media types like tv and handheld.
#8775 7ea71cd Thanks @igas! - Fixed the noUnnecessararyConditions rule to prevent trigger for optional fallback patterns.
#8860 95f1eea Thanks @dyc3! - Added the nursery rule noHexColors, which flags the use of hexadecimal color codes in CSS and suggests using named colors or RGB/RGBA/HSL/HSLA formats instead.
#8786 d876a38 Thanks @Bertie690! - Added the nursery rule useConsistentMethodSignatures.
Inspired by the similarly named version from typescript-eslint, this rule aims to enforce a consistent style for methods used inside object types and interfaces.

Examples

Invalid code with style set to "property" (the default):
```
1
interface Foo {
2
  method(a: string): void;
3
}
```
Invalid code with style set to "method":
```
1
type Bar = {
2
  prop: (a: string) => void;
3
}
```
#8864 5e97119 Thanks @dyc3! - Improved the summary provided by biome migrate eslint to be clearer on why rules were not migrated. Biome now specifies a reason when a rule is not migrated, such as being incompatible with the formatter or not implemented yet. This helps users make more informed decisions when migrating their ESLint configurations to Biome.
#8924 99b4cd1 Thanks @tmohammad78! - Fixed #8920: noUnknownFunction now knows about sibling-count, and sibling-index css functions

#8900 f788cff Thanks @mdevils! - Fixed #8885: useExhaustiveDependencies no longer incorrectly reports variables as unnecessary dependencies when they are derived from expressions containing post/pre-increment operators (++/--) or compound assignment operators (+=, -=, etc.).

1
let renderCount = 0;
2

3
export const MyComponent = () => {
4
  // `count` is now correctly recognized as a required dependency
5
  // because `renderCount++` can produce different values between renders
6
  const count = renderCount++;
7

8
  useEffect(() => {
9
    console.log(count);
10
  }, [count]); // no longer reports `count` as unnecessary
11
};

#8619 d78e01d Thanks @Netail! - Added the nursery rule useInputName. Require mutation arguments to be called “input”, and the input type to be called Mutation name + “Input”.

Invalid:
```
1
type Mutation {
2
  SetMessage(message: String): String
3
}
```
#8922 871b45e Thanks @siketyan! - Fixed #8829: Revamped the noGlobalDirnameFilename rule to catch many false negatives that have not been reported.

All versions since 2.3.12

2.3.12

Patch Changes

2.3.13

Patch Changes

2.3.14 Latest

Patch Changes

Examples