chore(deps): update dependency @biomejs/biome to v1.8.3 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@biomejs/biome (source)	1.8.0 -> 1.8.3

---

Release Notes

biomejs/biome (@​biomejs/biome)

v1.8.3

Compare Source

CLI

Bug fixes

• Fix #​3104 by suppressing node warnings when using biome migrate. Contributed by @​SuperchupuDev

• Force colors to be off when using the GitHub reporter to properly create annotations in GitHub actions (#​3148). Contributed by @​Sec-ant

Parser

Bug fixes

• Implement CSS unicode range. Contributed by @​denbezrukov

Formatter

Bug fixes

• Fix #​3184 CSS formatter converts custom identifiers to lowercase. Contributed by @​denbezrukov
• Fix #​3256 constant crashes when editing css files #​3256. Contributed by @​denbezrukov

Linter

New features

• Add nursery/useDeprecatedReason rule. Contributed by @​vohoanglong0107.
• Add nursery/noExportedImports. Contributed by @​Conaclos

Bug fixes

• useConsistentArrayType and useShorthandArrayType now ignore Array in the extends and implements clauses. Fix #​3247. Contributed by @​Conaclos
• Fixes #​3066 by taking into account the dependencies declared in the package.json. Contributed by @​ematipico
• The code action of the useArrowFunction rule now preserves a trailing comma when there is only a single type parameter in the arrow function and JSX is enabled. Fixes #​3292. Contributed by @​Sec-ant

Enhancements

• Enhance tailwind sorting lint rule #​1274 with variant support.

  Every preconfigured variant is assigned a weight that concurs on establishing the output sorting order.
  Since nesting variants on the same utility class is possible, the resulting weight is the Bitwise XOR of all the variants weight for that class.
  Dynamic variants (e.g. has-[.custom-class], group-[:checked]) are also supported and they take the weight of their base variant name the custom value attached (e.g. has-[.custom-class] takes has weight).
  Arbitrary variants (e.g. [&nth-child(2)]) don't have a weight assigned and they are placed after every known variant.
  Classes with the same amount of arbitrary variants follow lexicographical order. The class that has the highest number of nested arbitrary variants is placed last.
  Screen variants (e.g. sm:, max-md:, min-lg:) are not supported yet.

  Contributed by @​lutaok

v1.8.2

Compare Source

CLI

Bug fixes

• Fix #​3201 by correctly injecting the source code of the file when printing the diagnostics. Contributed by @​ematipico
• Fix #​3179 where comma separators are not correctly removed after running biome migrate and thus choke the parser. Contributed by @​Sec-ant
• Fix #​3232 by correctly using the colors set by the user. Contributed by @​ematipico

Enhancement

• Reword the reporter message No fixes needed to No fixes applied.

  The former message is misleading when there're still errors or warnings in the files that should be taken care of manually. For example:

  Checked 2 files in <TIME>. No fixes needed.
  Found 2 errors.
  

  The new message suits better in these cases.

  Contributed by @​Sec-ant

Configuration

Bug fixes

• Don't conceal previous overrides (#​3176).

  Previously, each override inherited the unset configuration of the base configuration.
  This means that setting a configuration in an override can be concealed by a subsequent override that inherits of the value from the base configuration.

  For example, in the next example, noDebugger was disabled for the index.js file.

  {
    "linter": {
      "rules": {
        "suspicious": { "noDebugger": "off" }
      }
    },
    "overrides": [
      {
        "include": ["index.js"],
        "linter": {
          "rules": {
            "suspicious": { "noDebugger": "warn" }
          }
        }
      }, {
        "include": ["index.js"],
        "linter": {
          "rules": {
            "suspicious": { "noDoubleEquals": "off" }
          }
        }
      }
    ]
  }

  The rule is now correctly enabled for the index.js file.

  Contributed by @​Conaclos

Formatter

Bug fixes

• Fix #​3103 by correctly resolving CSS formatter options. Contributed by @​ah-yu
• Fix #​3192 don't add an extra whitespace within :has. Contributed by @​denbezrukov

JavaScript APIs

Bug fixes

• Fix a regression introduced by the release of v1.8.0

Linter

New features

• Add nursery/useValidAutocomplete. Contributed by @​unvalley

Bug fixes

• Add nursery/noShorthandPropertyOverrides. #​2958 Contributed by @​neokidev

• Fix [#​3084] false positive by correctly recognize parenthesized return statement. Contributed by @​unvalley

• useImportExtensions now suggests a correct fix for import '.' and import './.'. Contributed by @​minht11

• Fix useDateNow false positive when new Date object has arguments new Date(0).getTime(). Contributed by @​minht11.

• The noUnmatchableAnbSelector rule is now able to catch unmatchable an+b selectors like 0n+0 or -0n+0. Contributed by @​Sec-ant.

• The useHookAtTopLevel rule now recognizes properties named as hooks like foo.useFoo(). Contributed by @​ksnyder9801

• Fix #​3092, prevent warning for Custom properties (--*). Contributed by @​chansuke

• Fix a false positive in the useLiteralKeys rule. (#​3160)

  This rule now ignores the following kind of computed member name:

  const a = {
    [`line1
    line2`]: true,
  };

  Contributed by @​Sec-ant

• The noUnknownProperty rule now ignores the composes property often used in css modules. #​3000 Contributed by @​chansuke

• Fix false positives of the useExhaustiveDependencies rule.

  The component itself is considered stable when it is used recursively inside a hook closure defined inside of it:

  import { useMemo } from "react";
  
  function MyRecursiveComponent() {
    // MyRecursiveComponent is stable, we don't need to add it to the dependencies list.
    const children = useMemo(() => <MyRecursiveComponent />, []);
    return <div>{children}</div>;
  }

  Also, export default function and export default class are considered stable now because they can only appear at the top level of a module.

  Contributed by @​Sec-ant

• Fix missing withDefaults macro in vue files for globals variables. Contributed by @​Shyam-Chen

Parser

Bug fixes

• Fix CSS modules settings mapping. Contributed by @​denbezrukov

v1.8.1

Compare Source

Analyzer

CLI

Bug fixes

• Fix #​3069, prevent overwriting paths when using --staged or --changed options. Contributed by @​unvalley
• Fix a case where the file link inside a diagnostic wasn't correctly displayed inside a terminal run by VSCode. Contributed by @​uncenter

Configuration

Bug fixes

• Fix #​3067, by assigning the correct default value to indentWidth. Contributed by @​ematipico

Editors

Formatter

Bug fixes

• Fix the bug where whitespace after the & character in CSS nesting was incorrectly trimmed, ensuring proper targeting of child classes #​3061. Contributed by @​denbezrukov
• Fix #​3068 where the CSS formatter was inadvertently converting variable declarations and function calls to lowercase. Contributed by @​denbezrukov
• Fix the formatting of CSS grid layout properties. Contributed by @​denbezrukov

JavaScript APIs

Linter

Bug fixes

• The noEmptyBlock css lint rule now treats empty blocks containing comments as valid ones. Contributed by @​Sec-ant

• useLiteralKeys no longer reports quoted member names (#​3085).

  Previously useLiteralKeys reported quoted member names that can be unquoted.
  For example, the rule suggested the following fix:

  - const x = { "prop": 0 };
  + const x = { prop: 0 };

  This conflicted with the option quoteProperties of our formatter.

  The rule now ignores quoted member names.

  Contributed by @​Conaclos

• noEmptyInterface now ignores empty interfaces in ambient modules (#​3110). Contributed by @​Conaclos

• noUnusedVariables and noUnusedFunctionParameters no longer report the parameters of a constructor type (#​3135).

  Previously, arg was reported as unused in a constructor type like:

  export type Classlike = new (arg: unknown) => string;

  Contributed by @​Conaclos

• noStringCaseMismatch now ignores escape sequences (#​3134).

  The following code is no longer reported by the rule:

  s.toUpperCase() === "\u001b";

  Contributed by @​Conaclos

Parser

New features

• Implemented CSS Unknown At-Rule parsing, allowing the parser to gracefully handle unsupported or unrecognized CSS at-rules. Contributed by @​denbezrukov

Bug fixes

• Fix #​3055 CSS: Layout using named grid lines is now correctly parsed. Contributed by @​denbezrukov
• Fix #​3091. Allows the parser to handle nested style rules and at-rules properly, enhancing the parser's compatibility with the CSS Nesting Module. Contributed by @​denbezrukov

---

Configuration

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

🚦 Automerge: Enabled.

♻ 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]

⚠️ No Changeset found

Latest commit: a5775d4

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