chore(deps): update dependency @biomejs/biome to v2.3.12 #49

renovate · 2026-01-03T18:01:09Z

This PR contains the following updates:

Package	Change	Age	Confidence
@biomejs/biome (source)	`2.3.10` → `2.3.12`

Release Notes

biomejs/biome (@biomejs/biome)

`v2.3.12`

Compare Source

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:
```
<script>
export default {
  data() {
    return { count: 0 };
  },
};
</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:
```
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:
```
{
  "options": {
    "disallow": ["mutation"]
  }
}
```
```
type Mutation {
  SetMessage(message: String): String
}
```
#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:
```
try {
  foo();
} catch {
  throw new Error("fail");
}
```
```
try {
  foo();
} catch (err) {
  throw new Error(err.message);
}
```
Valid examples:
```
try {
  foo();
} catch (err) {
  throw new Error("fail", { cause: err });
}
```
```
try {
  foo();
} catch (error) {
  throw new Error("Something went wrong", { cause: error });
}
```
Valid example when requireCatchParameter is false:

Valid:
```
try {
  foo();
} catch {
  throw new Error("fail");
}
```
#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:
```
query {
  fieldA
}

query B {
  fieldB
}
```
#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:
```
import Script from "next/script";

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

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

const [[x, y], setXY] = useState([1, 2]);
useEffect(() => {
  console.log(x, y);
}, [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:
```
var f = function () {
  return /=foo/;
};
```
#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.
```
useMemo(() => Boolean(myObj!.x), [myObj!.x]); // No longer reports incorrect diagnostics
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:
```
enum A {
  TEST
  TesT
}
```
#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:
```
query Foo {
  id
}

fragment Bar on Baz {
  id
}
```
#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.
```
const varA = Math.random(),
  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.
```
const fe = fetchEntity;
useEffect(() => {
  fe(id);
}, [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.

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

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

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

#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.
```
function myEffect() {
  console.log(foo, bar);
}
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.
```
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.
```
// maxLines: 2
const a = 1;
const b = 2;
const c = 3;
```
#8753 71b5c6e Thanks @Netail! - Added the nursery rule noExcessiveClassesPerFile. Enforce a maximum number of classes per file.

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

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

`v2.3.11`

Compare Source

Patch Changes

#8583 83be210 Thanks @dyc3! - Added the new nursery rule useVueValidTemplateRoot.

This rule validates only root-level <template> elements in Vue single-file components. If the <template> has a src attribute, it must be empty. Otherwise, it must contain content.

Invalid examples:
```
<template src="./foo.html">content</template>
```
```
<template></template>
```
Valid examples:
```
<template>content</template>
```
```
<template src="./foo.html"></template>
```
#8586 df8fe06 Thanks @dyc3! - Added a new nursery rule useVueConsistentVBindStyle. Enforces consistent v-bind style (:prop shorthand vs v-bind:prop longhand). Default prefers shorthand; configurable via rule options.
#8587 9a8c98d Thanks @dyc3! - Added the rule useVueVForKey, which enforces that any element using v-for also specifies a key.

Invalid
```
<li v-for="item in items">{{ item }}</li>
```
Valid
```
<li v-for="item in items" :key="item.id">{{ item }}</li>
```
#8586 df8fe06 Thanks @dyc3! - Added a new nursery rule useVueConsistentVOnStyle. Enforces consistent v-on style (@event shorthand vs v-on:event longhand). Default prefers shorthand; configurable via rule options.
#8583 83be210 Thanks @dyc3! - Added the new nursery rule useVueValidVOnce. Enforces that usages of the v-once directive in Vue.js SFC are valid.
```

<div v-once />


<div v-once:aaa />
<div v-once.bbb />
<div v-once="ccc" />
```
#8498 d80fa41 Thanks @tt-a1i! - Fixed #8494. Extended noUndeclaredEnvVars to support bracket notation (process.env["VAR"], import.meta.env["VAR"]), Bun runtime (Bun.env.VAR, Bun.env["VAR"]), and Deno runtime (Deno.env.get("VAR")).
#8509 574a909 Thanks @ematipico! - Added support for parsing and formatting the Svelte {#await} syntax, when html.experimentalFullSupportEnabled is set to true.
```
-{#await promise  then name }
+{#await promise then name}

-{:catch    name}
+{:catch name}

{/await}
```
#8316 d64e92d Thanks @washbin! - Added the new nursery rule noMultiAssign. This rule helps to prevent multiple chained assignments.

For example, the following code triggers because there are two assignment expressions in the same statement.
```
const a = (b = 0);
```
#8592 a5f59cd Thanks @Netail! - Added the nursery rule useUniqueInputFieldNames. Require fields within an input object to be unique.

Invalid:
```
query A($x: Int, $x: Int) {
  field
}
```
#8524 17a6156 Thanks @JacquesLeupin! - Fixed #8488: Relative plugin paths are now resolved from the configuration file directory, including when configurations are merged (e.g. extends: "//").
#8655 3260ec9 Thanks @JacquesLeupin! - Fixed #8636: Biome's CSS formatter now breaks comma-separated declaration values at top-level commas when wrapping.

#8537 cc3e851 Thanks @dibashthapa! - Fixed #8491: Resolved false positive errors for safe boolean expressions. There are still pending fixes. Head to #8491 (comment) for more details

This new change will check for safe boolean expressions in variable declarations.

For example,

Valid:

let isOne = 1;
let isPositiveNumber = number > 0;

return (
  <div>
    {" "}
    {isOne && "One"} {isPositiveNumber && "Is positive"}
  </div>
);

Invalid:

let emptyStr = "";
let isZero = 0;

return (
  <div>
    {emptyStr && "Empty String"} {isZero && "Number is zero"}{" "}
  </div>
);

#8511 16a9036 Thanks @ematipico! - Improved the diagnostics of the rules useSortedClasses and noUnnecessaryConditions. The diagnostics now state that these rules are a work in progress and link to the relevant GitHub issue.
#8521 a704be9 Thanks @ToBinio! - Added the nursery rule useVueConsistentDefinePropsDeclaration, which enforces consistent defineProps declaration style.

Invalid

<script setup lang="ts">
const props = defineProps({
  kind: { type: String },
});
</script>

Valid

<script setup lang="ts">
const props = defineProps<{
  kind: string;
}>();
</script>

#8595 7c85bf0 Thanks @dyc3! - Fixed #8584: The HTML formatter will preserve whitespace after some elements and embedded expressions, which more closely aligns with Prettier's behavior.
```
- <h1>Hello, {framework}and Svelte!</h1>
+ <h1>Hello, {framework} and Svelte!</h1>
```
#8598 5e85d43 Thanks @Netail! - Added the nursery rule useUniqueFieldDefinitionNames. Require all fields of a type to be unique.

Invalid:
```
type SomeObject {
  foo: String
  foo: String
}
```
#8495 b573d14 Thanks @taga3s! - Fixed #8405: noMisusedPromises now emits warnings/errors when a function returns union types such as T | Promise<T> which is used in conditionals.
```
const a = (): boolean | Promise<boolean> => Promise.resolve(true);
if (a()) {
} // Now correctly flagged
```
#8632 0be7d12 Thanks @Bertie690! - The documentation & rule sources for lint/complexity/noBannedTypes have been updated to fix a few oversights.

In addition to some general typo fixes:
- The rule now recommends Record<keyof any, never> instead of Record<string, never> (the latter of which incorrectly allows symbol-keyed properties).
- The rule mentions an alternate method to enforce object emptiness involving unique symbol-based guards used by type-fest and many other packages:
```
declare const mySym: unique symbol;

// Since this type's only property is an unexported `unique symbol`, nothing that imports it can specify any properties directly
// (as far as excess property checks go)
export type EmptyObject = { [mySym]?: never };
export type IsEmptyObject<T> = T extends EmptyObject ? true : false;
```
The rule's listed sources have been updated as well to reflect the original source rule (ban-types) having been split into 3 separate rules circa April 2024.
#8580 a3a1ad2 Thanks @taga3s! - Added the nursery rule noBeforeInteractiveScriptOutsideDocument to the Next.js domain.
This rule prevents usage of next/script's beforeInteractive strategy outside of pages/_document.js.
#8493 5fc24f4 Thanks @ematipico! - Added support for parsing and formatting the Svelte {#each} syntax, when html.experimentalFullSupportEnabled is set to true.
```
- {#each items   as item  }
+ {#each items as item}

{/each}
```
#8546 0196c0e Thanks @Zaczero! - Hardened union static-member type flattening in edge cases (e.g. unions containing unknown or inferred expression types). This keeps inference conservative and avoids unstable type growth in node = node.parent-style loops.
#8569 1022c76 Thanks @ematipico! - Fixed an issue where the Biome HTML parser would emit a parse error when certain keywords are inside the text of HTML tags.
#8606 f50723b Thanks @dyc3! - Fixed #8563: fixed a bounds check on bogus regex literals that caused panics when doing type inference
#7410 ab9af9a Thanks @sgarcialaguna! - Added the new nursery rule noJsxPropsBind. This rule disallows .bind(), arrow functions, or function expressions in JSX props.

Invalid:
```
<Foo onClick={() => console.log("Hello!")}></Foo>
```
#8523 5f22f1c Thanks @ematipico! - Improved the diagnostics of nursery rules. Added a message to diagnostics emitted by nursery rules, so that users are aware of nature of nursery rules.
#8571 03666fd Thanks @dyc3! - Improved the performance of noRedeclare by eliminating string allocations
#8591 9dd9ca7 Thanks @Netail! - Added the nursery rule useUniqueArgumentNames. Enforce unique arguments for GraphQL fields & directives.

Invalid:
```
query {
  field(arg1: "value", arg1: "value")
}
```
#8521 a704be9 Thanks @ToBinio! - Update useVueDefineMacrosOrder to only run on <script setup> blocks.
#8344 7b982ba Thanks @ematipico! - Reduced the system calls when running the CLI. The performances might be noticeable in big projects that have multiple libraries and enable project rules.
#8588 958e24b Thanks @Netail! - Added the nursery rule useUniqueVariableNames. Enforce unique variable names for GraphQL operations.

Invalid:
```
query ($x: Int, $x: Int) {
  field
}
```
#8529 8794883 Thanks @mdevils! - Fixed #8499: useExhaustiveDependencies properly handles aliased destructured object keys when using stableResult configuration.
#8557 4df2f4d Thanks @dyc3! - Fixed an issue with the HTML formatter where it wouldn't add a space before the /> in self closing elements. This brings the HTML formatter more in line with Prettier.
```
-<Component/>
+<Component />
```
#8509 574a909 Thanks @ematipico! - Added support for parsing and formatting the Svelte {#snippet} syntax, when html.experimentalFullSupportEnabled is set to true.
```
-{#snippet    foo() }
+{#snippet foo()}

{/snippe}
```
#8248 1231a5c Thanks @emilyinure! - Added new nursery rule noReturnAssign, which disallows assignments inside return statements.

Invalid:
```
function f(a) {
  return (a = 1);
}
```
#8531 6b09620 Thanks @taga3s! - Fixed #8472: The CSS parser can now accept multiple comma separated parameters in :active-view-transition-type.
#8615 b9da66d Thanks @taga3s! - Remove next/script component name check from noBeforeInteractiveScriptOutsideDocument since it is a default export.
#8536 efbfbe2 Thanks @dyc3! - Fixed #8527: Improved type inference where analyzing code with repeated object property access and assignments (e.g. node = node.parent, a pattern common when traversing trees in a while loop) could hit an internal type limit. Biome now handles these cases without exceeding the type limit.
#8583 83be210 Thanks @dyc3! - Added the new nursery rule useVueValidVCloak. Enforces that usages of the v-cloak directive in Vue.js SFC are valid.
```

<div v-cloak />


<div v-cloak:aaa />
<div v-cloak.bbb />
<div v-cloak="ccc" />
```
#8583 83be210 Thanks @dyc3! - Added the new nursery rule useVueValidVPre. Enforces that usages of the v-pre directive in Vue.js SFC are valid.
```

<div v-pre />


<div v-pre:aaa />
<div v-pre.bbb />
<div v-pre="ccc" />
```
#8644 a3a27a7 Thanks @JacquesLeupin! - Added the nursery rule useVueVapor to enforce <script setup vapor> in Vue SFCs. For example <script setup> is invalid.
#8508 b86842c Thanks @tt-a1i! - Fixed #6783: now, when a path is provided via --stdin-file-path, Biome checks whether the file exists on disk. If the path doesn't exist (virtual path), ignore checks (files.includes and VCS ignore rules) are skipped.

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

github-actions bot added pr-in-progress testing labels Jan 3, 2026

chore(deps): update dependency @biomejs/biome to v2.3.12

1ad5b95

renovate bot force-pushed the renovate/biomejs-biome-2.x-lockfile branch from efcc106 to 1ad5b95 Compare January 23, 2026 16:53

renovate bot changed the title ~~chore(deps): update dependency @biomejs/biome to v2.3.11~~ chore(deps): update dependency @biomejs/biome to v2.3.12 Jan 23, 2026

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(deps): update dependency @biomejs/biome to v2.3.12 #49

chore(deps): update dependency @biomejs/biome to v2.3.12 #49

Uh oh!

renovate bot commented Jan 3, 2026 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

chore(deps): update dependency @biomejs/biome to v2.3.12 #49

Are you sure you want to change the base?

chore(deps): update dependency @biomejs/biome to v2.3.12 #49

Uh oh!

Conversation

renovate bot commented Jan 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

v2.3.12

Patch Changes

v2.3.11

Patch Changes

Invalid

Valid

Configuration

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

renovate bot commented Jan 3, 2026 •

edited

Loading

`v2.3.12`

`v2.3.11`