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

[renovate]

This PR contains the following updates:

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

---

Release Notes

biomejs/biome (@​biomejs/biome)

v2.3.13

Compare Source

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:

  <div @&#8203;keydown.arrow-down="handler"></div>
  <div @&#8203;keydown.a="handler"></div>
  <div @&#8203;keydown.b="handler"></div>
  <div @&#8203;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.

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();

---

Configuration

📅 Schedule: Branch creation - "after 6am and before 6pm" (UTC), 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 these updates again.

---

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

---

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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud