Update dependency @biomejs/biome to v2 by renovate[bot] · Pull Request #3240 · Team3132/attendance

renovate · 2026-01-04T06:58:22Z

Note: This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
@biomejs/biome (source)	`1.9.4` → `2.3.11`

Release Notes

biomejs/biome (@biomejs/biome)

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

`v2.3.10`

Compare Source

Patch Changes

#8417 c3a2557 Thanks @taga3s! - Fixed #7809: noRedeclare no longer reports redeclarations for infer type in conditional types.
#8477 90e8684 Thanks @dyc3! - Fixed #8475: fixed a regression in how noExtraNonNullAssertion flags extra non-null assertions
#8479 250b519 Thanks @dyc3! - Fixed #8473: The semantic model now indexes typescript constructor method definitions, and no longer panics if you use one (a regression in 2.3.9).
#8448 2af85c1 Thanks @mdevils! - Improved handling of defineProps() macro in Vue components. The noVueReservedKeys rule now avoids false positives in non-setup scripts.
#8420 42033b0 Thanks @vsn4ik! - Fixed the nursery rule noLeakedRender.

The biome migrate eslint command now correctly detects the rule react/jsx-no-leaked-render in your eslint configurations.
#8426 285d932 Thanks @anthonyshew! - Added a Turborepo domain and a new "noUndeclaredEnvVars" rule in it for warning users of unsafe environment variable usage in Turborepos.
#8410 a21db74 Thanks @ematipico! - Fixed #2988 where Biome couldn't handle properly characters that contain multiple code points when running in stdin mode.
#8372 b352ee4 Thanks @Netail! - Added the nursery rule noAmbiguousAnchorText, which disallows ambiguous anchor descriptions.

Invalid

<a>learn more</a>

`v2.3.9`

Compare Source

Patch Changes

#8232 84c9e08 Thanks @ruidosujeira! - Added the nursery rule noScriptUrl.

This rule disallows the use of javascript: URLs, which are considered a form of eval and can pose security risks such as XSS vulnerabilities.
```
<a href="javascript:alert('XSS')">Click me</a>
```
#8341 343dc4d Thanks @arendjr! - Added the nursery rule useAwaitThenable, which enforces that await is only used on Promise values.

Invalid

await "value";

const createValue = () => "value";
await createValue();

Caution

This is a first iteration of the rule, and does not yet detect generic "thenable" values.

#8034 e7e0f6c Thanks @Netail! - Added the nursery rule useRegexpExec. Enforce RegExp#exec over String#match if no global flag is provided.
#8137 d407efb Thanks @denbezrukov! - Reduced the internal memory used by the Biome formatter.
#8281 30b046f Thanks @tylersayshi! - Added the rule useRequiredScripts, which enforces presence of configurable entries in the scripts section of package.json files.

#8290 d74c8bd Thanks @dyc3! - The HTML formatter has been updated to match Prettier 3.7's behavior for handling <iframe>'s allow attribute.

- <iframe allow="layout-animations 'none'; unoptimized-images 'none'; oversized-images 'none'; sync-script 'none'; sync-xhr 'none'; unsized-media 'none';"></iframe>
+ <iframe
+ 	allow="
+ 		layout-animations 'none';
+ 		unoptimized-images 'none';
+ 		oversized-images 'none';
+ 		sync-script 'none';
+ 		sync-xhr 'none';
+ 		unsized-media 'none';
+ 	"
+ ></iframe>

#8302 d1d5014 Thanks @mlafeldt! - Fixed #8109: return statements in Astro frontmatter no longer trigger "Illegal return statement" errors when using experimentalFullSupportEnabled.
#8346 f3aee1a Thanks @arendjr! - Fixed #8292: Implement tracking
of types of TypeScript constructor parameter properties.

This resolves certain false negatives in noFloatingPromises and other typed
rules.

Example

class AsyncClass {
  async returnsPromise() {
    return "value";
  }
}

class ShouldBeReported {
  constructor(public field: AsyncClass) {}
  //          ^^^^^^^^^^^^----------------- Parameter property declaration

  async shouldBeReported() {
    // `noFloatingPromises` will now report the following usage:
    this.field.returnsPromise();
  }
}

#8326 153e3c6 Thanks @ematipico! - Improved the rule noBiomeFirstException. The rule can now inspect if extended configurations already contain the catch-all ** inside files.includes and, if so, the rule suggests removing ** from the user configuration.
#8433 397547a Thanks @dyc3! - Fixed #7920: The CSS parser, with Tailwind directives enabled, will no longer error when you use things like prefix(tw) in @import at rules.
#8378 cc2a62e Thanks @Bertie690! - Clarify diagnostic message for lint/style/useUnifiedTypeSignatures

The rule's diagnostic message now clearly states that multiple similar overload signatures are hard to read & maintain, as opposed to overload signatures in general.
#8296 9d3ef10 Thanks @dyc3! - biome rage now shows if you have experimental HTML full support enabled.
#8414 09acf2a Thanks @Bertie690! - Updated the documentation & diagnostic message for lint/nursery/noProto, mentioning the reasons for its longstanding deprecation and why more modern alternatives are preferred.

Notably, the rule clearly states that using __proto__ inside object literal definitions is still allowed, being a standard way to set the prototype of a newly created object.
#8445 c3df0e0 Thanks @tt-a1i! - Fix --changed and --staged flags throwing "No such file or directory" error when a file has been deleted or renamed in the working directory. The CLI now filters out files that no longer exist before processing.
#8459 b17d12b Thanks @ruidosujeira! - Fix #8435: resolved false positive in noUnusedVariables for generic type parameters in construct signature type members (new <T>(): T).
#8439 a78774b Thanks @tt-a1i! - Fixed #8011: useConsistentCurlyBraces no longer suggests removing curly braces from JSX expression children containing characters that would cause parsing issues or semantic changes when converted to plain JSX text ({, }, <, >, &).
#8436 a392c06 Thanks @ruidosujeira! - Fixed #8429. Formatter, linter, and assist settings now correctly inherit from global configuration when not explicitly specified in overrides.

Before this fix, when an override specified only one feature (e.g., only linter), other features would be incorrectly disabled instead of inheriting from global settings.

Example configuration that now works correctly:
```
{
  "formatter": { "enabled": true },
  "overrides": [
    {
      "includes": ["*.vue"],
      "linter": { "enabled": false }
    }
  ]
}
```
After this fix, .vue files will have the linter disabled (as specified in the override) but the formatter enabled (inherited from global settings).
#8411 9f1b3b0 Thanks @rriski! - Properly handle name, type_arguments, and attributes slots for JsxOpeningElement and JsxSelfClosingElement GritQL patterns.

The following biome search commands no longer throw errors:
```
biome search 'JsxOpeningElement(name = $elem_name) where { $elem_name <: "div" }'
biome search 'JsxSelfClosingElement(name = $elem_name) where { $elem_name <: "div" }'
```
#8441 cf37d0d Thanks @tt-a1i! - Fixed #6577: noUselessUndefined no longer reports () => undefined in arrow function expression bodies. Previously, the rule would flag this pattern and suggest replacing it with () => {}, which conflicts with the noEmptyBlockStatements rule.
#8444 8caa7a0 Thanks @tt-a1i! - Fix noUnknownMediaFeatureName false positive for prefers-reduced-transparency media feature. The feature name was misspelled as prefers-reduded-transparency in the keywords list.
#8443 c3fa5a1 Thanks @tt-a1i! - Fix useGenericFontNames false positive when a CSS variable is used as the last value in font-family or font. The rule now correctly ignores cases like font-family: "Noto Serif", var(--serif) and font: 1em Arial, var(--fallback).
#8281 30b046f Thanks @tylersayshi! - Fixed noDuplicateDependencies incorrectly triggering on files like _package.json.
#8315 c7915c4 Thanks @hirokiokada77! - Fixed #5213: The noDoneCallback rule no longer flags false positives when a method is called on a regular variable bound to identifiers such as before, after, beforeEach, and afterEach.
#8398 204844f Thanks @Bertie690! - The default value of the ignoreRestSiblings option for noUnusedVariables'
has been reverted to its prior value of true after an internal refactor accidentally changed it.

The diagnostic message has also been tweaked for readability.
#8242 9694e37 Thanks @dyc3! - Fixed bugs in the HTML parser so that it will flag invalid shorthand syntaxes instead of silently accepting them. For example, <Foo : foo="5" /> is now invalid because there is a space after the :.
#8297 efa694c Thanks @Yonom! - Added support for negative value utilities in useSortedClasses. Negative value utilities such as -ml-2 or -top-4 are now recognized and sorted correctly alongside their positive counterparts.
```
// Now detected as unsorted:
<div class="-ml-2 p-4 -mt-1" />
// Suggested fix:
<div class="-mt-1 -ml-2 p-4" />
```
#8335 3710702 Thanks @dibashthapa! - Added the new nursery rule useDestructuring. This rule helps to encourage destructuring from arrays and objects.

For example, the following code triggers because the variable name x matches the property foo.x, making it ideal for object destructuring syntax.
```
var x = foo.x;
```
#8383 59b2f9a Thanks @ematipico! - Fixed #7927: noExtraNonNullAssertion incorrectly flagged separate non-null assertions on both sides of an assignment.

The rule now correctly distinguishes between nested non-null assertions (still flagged) and separate non-null assertions on different sides of an assignment (allowed).

Examples

Valid (now allowed)

arr[0]! ^= arr[1]!;

Invalid (still flagged)

arr[0]!! ^= arr[1];
arr[0] ^= arr[1]!!;

#8401 382786b Thanks @Bertie690! - useExhaustiveDependencies now correctly validates custom hooks whose dependency arrays come before their callbacks.

Previously, a logical error caused the rule to be unable to detect dependency arrays placed before hook callbacks, producing spurious errors and blocking further diagnostics.

{
  "linter": {
    "rules": {
      "correctness": {
        "useExhaustiveDependencies": {
          "level": "error",
          "options": {
            "hooks": [
              {
                "name": "doSomething",
                "closureIndex": 2,
                "dependenciesIndex": 0
              }
            ]
          }
        }
      }
    }
  }
}

function component() {
  let thing = 5;
  // The rule will now correctly recognize `thing` as being specified
  // instead of erroring due to "missing" dependency arrays
  doSomething([thing], "blah", () => {
    console.log(thing);
  });
}

The rule documentation & diagnostic messages have also been reworked for improved clarity.

#8365 8f36051 Thanks @JacquesLeupin! - Fixed #8360: GritQL plugins defined in child configurations with extends: "//" now work correctly.
#8306 8de2774 Thanks @dibashthapa! - Fixed #8288: Fixed the issue with false positive errors

This new change will ignore attribute and only show diagnostics for JSX Expressions

For example

Valid:
```
<Something checked={isOpen && items.length} />
```
Invalid:
```
const Component = () => {
  return isOpen && items.length;
};
```
#8356 f9673fc Thanks @ematipico! - Fixed #7917, where Biome removed the styles contained in a <style lang="scss">, when experimentalFullSupportEnabled is enabled.
#8371 d71924e Thanks @ematipico! - Fixed #7343, where Biome failed to resolve extended configurations from parent directories using relative paths.
#8404 6a221f9 Thanks @fireairforce! - Fixed #7826, where a class member named async will not cause the parse error.
#8249 893e36c Thanks @cormacrelf! - Addressed #7538. Reduced the
volume of logging from the LSP server.

Use biome clean to remove large logs.

#8303 db2c65b Thanks @hirokiokada77! - Fixed #8300: noUnusedImports now detects JSDoc tags on object properties.

import type LinkOnObjectProperty from "mod";

const testLinkOnObjectProperty = {
	/**
	 * {@&#8203;link LinkOnObjectProperty}
	 */
	property: 0,
};

#8328 9cf2332 Thanks @Netail! - Corrected rule source reference. biome migrate eslint should do a bit better detecting rules in your eslint configurations.
#8403 c96dcf2 Thanks @dyc3! - Fixed #8340: noUnknownProperty will no longer flag anything in @plugin when the parser option tailwindDirectives is enabled
#8284 4976d1b Thanks @denbezrukov! - Improved the performance of the Biome Formatter by enabling the internal source maps only when needed.
#8260 a226b28 Thanks @ho991217! - Fixed biome-vscode#817: Biome now updates documents when the textDocument/didSave notification is received.
#8183 b064786 Thanks @hornta! - Fixed #8179: The useConsistentArrowReturn rule now correctly handles multiline expressions in its autofix when the style option is set to "always".

Previously, the autofix would incorrectly place a newline after the return keyword, causing unexpected behavior.

Example:
```
const foo = (l) => l.split("\n");
```
Now correctly autofixes to:
```
const foo = (l) => {
-   return
-   l.split('\n');
+   return l.split('\n');
}
```
#8382 7409cba Thanks @fireairforce! - Fixed #8338: Ignored the noUnknownTypeSelector check when the root selector is used under View Transition pseudo-elements.

Example
```
::view-transition-old(root),
::view-transition-new(root) {
  z-index: 1;
}
```
#7513 e039f3b Thanks @AsherDe! - Added the nursery rule noVueSetupPropsReactivityLoss.

This new rule disallows usages that cause the reactivity of props passed to the setup function to be lost.

Invalid code example:
```
export default {
  setup({ count }) {
    // `count` is no longer reactive here.
    return () => h("div", count);
  },
};
```

`v2.3.8`

Compare Source

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:
```
const Component = () => {
  const count = 0;
  return <div>{count && <span>Count: {count}</span>}</div>;
};
```
#8116 b537918 Thanks @Netail! - Added the nursery rule noDuplicatedSpreadProps. Disallow JSX prop spreading the same identifier multiple times.

Invalid:
```
<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:
```
const foo =
  "Line 1\n\
Line 2";
```
Valid:
```
const foo = "Line 1\nLine 2";
const bar = `Line 1
Line 2`;
```

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

-type True = unknown extends Type<
-  "many",
-  "generic",
-  "parameters",
-  "one",
-  "two",
-  "three"
->
-  ? true
-  : false;
+type True =
+  unknown extends Type<"many", "generic", "parameters", "one", "two", "three">
+    ? true
+    : false;

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

This means the following is now allowed:

// example.js
export function example() {
  return 1;
}

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

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:
```
foo == null;
foo != null;
```
Valid:
```
foo === null;
foo !== null;
```
#8219 793bb9a Thanks @dyc3! - Fixed #8190: The HTML parser will now parse Vue event handlers that contain

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 becomes conflicted, 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.

changeset-bot · 2026-01-04T06:58:27Z

⚠️ No Changeset found

Latest commit: 0232e79

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

renovate · 2026-01-04T07:34:44Z

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 2.x releases. But if you manually upgrade to 2.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

Update dependency @biomejs/biome to v2

0232e79

renovate Bot added the renovate label Jan 4, 2026

sebasptsch closed this Jan 4, 2026

renovate Bot deleted the renovate/biomejs-biome-2.x branch January 4, 2026 07:34

Navigation Menu

Uh oh!

Update dependency @biomejs/biome to v2 - #3240

Update dependency @biomejs/biome to v2#3240
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/biomejs-biome-2.x

renovate Bot commented Jan 4, 2026

Uh oh!

changeset-bot Bot commented Jan 4, 2026

Uh oh!

renovate Bot commented Jan 4, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

renovate Bot commented Jan 4, 2026

Release Notes

v2.3.11

Patch Changes

Invalid

Valid

v2.3.10

Patch Changes

Invalid

v2.3.9

Patch Changes

Invalid

Caution

Example

Examples

Valid (now allowed)

Invalid (still flagged)

v2.3.8

Patch Changes

Configuration

Uh oh!

changeset-bot Bot commented Jan 4, 2026

⚠️ No Changeset found

Uh oh!

renovate Bot commented Jan 4, 2026

Renovate Ignore Notification

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

`v2.3.11`

`v2.3.10`

`v2.3.9`

`v2.3.8`