chore(deps): update @biomejs packages

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@biomejs/cli-darwin-arm64 (source)	1.8.1 -> 1.8.2
@biomejs/cli-darwin-x64 (source)	1.8.1 -> 1.8.2
@biomejs/cli-linux-arm64 (source)	1.8.1 -> 1.8.2
@biomejs/cli-linux-arm64-musl (source)	1.8.1 -> 1.8.2
@biomejs/cli-linux-x64 (source)	1.8.1 -> 1.8.2
@biomejs/cli-linux-x64-musl (source)	1.8.1 -> 1.8.2
@biomejs/cli-win32-arm64 (source)	1.8.1 -> 1.8.2
@biomejs/cli-win32-x64 (source)	1.8.1 -> 1.8.2
@biomejs/wasm-bundler (source)	^1.8.1 -> ^1.8.2
@biomejs/wasm-nodejs (source)	^1.8.1 -> ^1.8.2
@biomejs/wasm-web (source)	^1.8.1 -> ^1.8.2
@types/bun (source)	1.1.4 -> 1.1.5
@types/node (source)	20.14.3 -> 20.14.8
typescript (source)	5.4.5 -> 5.5.2

---

Release Notes

biomejs/biome (@​biomejs/cli-darwin-arm64)

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

Microsoft/TypeScript (typescript)

v5.5.2

Compare Source

---

Configuration

📅 Schedule: Branch creation - "before 9am on monday" in timezone Europe/Gibraltar, 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

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

---

This PR has been generated by Mend Renovate. View repository job log here.