build(deps): update dependency @biomejs/biome to v1.8.2

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@biomejs/biome (source)	1.8.1 -> 1.8.2

---

Release Notes

biomejs/biome (@​biomejs/biome)

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

---

Configuration

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

🚦 Automerge: Enabled.

♻ 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 has been generated by Mend Renovate. View repository job log here.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
distrohop	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 20, 2024 0:15am

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.