chore(deps)(deps-dev): bump @biomejs/biome from 1.9.4 to 2.0.2

[dependabot]

Bumps @biomejs/biome from 1.9.4 to 2.0.2.

Release notes

Sourced from @​biomejs/biome's releases.

@​biomejs/biome@​2.0.1

Patch Changes

• #6425 00e97ad Thanks @​siketyan! - Fixed #6391: the rule noUselessFragments no longer reports a fragment that contains whitespaces which aren't trimmed by the runtime.

• #6417 dd88565 Thanks @​ematipico! - Fixed #6360: The following pseudo classes and elements are no longer reported by noUnknownPseudoClass or noUnknownPseudoElement rules.

  • :open
  • ::details-content
  • ::prefix
  • ::search-text
  • ::suffix

• #6417 dd88565 Thanks @​ematipico! - Fixed #6357, where the boolean values weren't correctly merged when using the extends functionality. Now Biome correctly merges the values.

• #6417 dd88565 Thanks @​ematipico! - Fixed #6341: Fixed an issue where Biome would throw an error for the language tags nb and nn.

• #6385 94142dd Thanks @​siketyan! - Fixed #6377: The rule noSelfCompare now correctly compares two function calls with different arguments.

• #6417 dd88565 Thanks @​ematipico! - Fixed #6278: useExhaustiveDependencies no longer adds duplicated dependencies into the list.

• #6417 dd88565 Thanks @​ematipico! - Fix #6396, where vi.useFakeTimers() and vi.useRealTimers() incorrectly triggered React Hooks-related rules

• #6417 dd88565 Thanks @​ematipico! - Fixed a bug where Biome didn't correctly discover nested configuration files when using the lint command and the linter is disabled in the root configuration.

• #6422 594ec50 Thanks @​ematipico! - Removed the experimental rename feature from Biome LSP, which caused some issues inside existing editors such as Zed.

• #6388 c6942d2 Thanks @​siketyan! - Fixed #6375: the formatter no longer inserts an extra empty line before a semicolon when it has leading comments.

Biome CLI v2.0.0

Major Changes

• Biome now resolves globs and paths from the configuration. Before, paths and globs were resolved from the working directory.

• Biome now raises a warning diagnostic for suppression comments that have <explanation> as reason.

  <explanation> is provided as a placeholder when applying the suppression code fix from LSP editors.

• Removed the --config-path argument from the biome lsp-proxy and biome start commands.

  The option was overriding the configuration path for all workspaces opened in the Biome daemon, which led to a configuration mismatch problem when multiple projects are opened in some editors or IDEs.

  If you are using one of our official plugins for IDEs or editors, it is recommended to update it to the latest version of the plugin, or you will get unexpected behavior.

  If you are a developer of a plugin, please update your plugin to use the workspace/configuration response instead of using the --config-path argument. Biome's LSP will resolve a configuration in the workspace automatically, so it is recommended to keep it empty unless you are using a custom configuration path.

• Downgraded some code fixes to unsafe which were previously safe.

  The following rules have now a unsafe fix:

... (truncated)

Changelog

Sourced from @​biomejs/biome's changelog.

2.0.2

Patch Changes

• #6436 ec7c63d Thanks @​ematipico! - Fixed an issue where binaries weren't copied anymore inside the @biomejs/cli-* packages.

2.0.1

Patch Changes

• #6425 00e97ad Thanks @​siketyan! - Fixed #6391: the rule noUselessFragments no longer reports a fragment that contains whitespaces which aren't trimmed by the runtime.

• #6417 dd88565 Thanks @​ematipico! - Fixed #6360: The following pseudo classes and elements are no longer reported by noUnknownPseudoClass or noUnknownPseudoElement rules.

  • :open
  • ::details-content
  • ::prefix
  • ::search-text
  • ::suffix

• #6417 dd88565 Thanks @​ematipico! - Fixed #6357, where the boolean values weren't correctly merged when using the extends functionality. Now Biome correctly merges the values.

• #6417 dd88565 Thanks @​ematipico! - Fixed #6341: Fixed an issue where Biome would throw an error for the language tags nb and nn.

• #6385 94142dd Thanks @​siketyan! - Fixed #6377: The rule noSelfCompare now correctly compares two function calls with different arguments.

• #6417 dd88565 Thanks @​ematipico! - Fixed #6278: useExhaustiveDependencies no longer adds duplicated dependencies into the list.

• #6417 dd88565 Thanks @​ematipico! - Fix #6396, where vi.useFakeTimers() and vi.useRealTimers() incorrectly triggered React Hooks-related rules

• #6417 dd88565 Thanks @​ematipico! - Fixed a bug where Biome didn't correctly discover nested configuration files when using the lint command and the linter is disabled in the root configuration.

• #6422 594ec50 Thanks @​ematipico! - Removed the experimental rename feature from Biome LSP, which caused some issues inside existing editors such as Zed.

• #6388 c6942d2 Thanks @​siketyan! - Fixed #6375: the formatter no longer inserts an extra empty line before a semicolon when it has leading comments.

2.0.0

Major Changes

• Biome now resolves globs and paths from the configuration. Before, paths and globs were resolved from the working directory.

• Biome now raises a warning diagnostic for suppression comments that have <explanation> as reason.

  <explanation> is provided as a placeholder when applying the suppression code fix from LSP editors.

• Removed the --config-path argument from the biome lsp-proxy and biome start commands.

  The option was overriding the configuration path for all workspaces opened in the Biome daemon, which led to a configuration mismatch problem when multiple projects are opened in some editors or IDEs.

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Summary by Sourcery

Chores:

• Bump @biomejs/biome dev dependency from v1.9.4 to v2.0.2

[sourcery-ai]

Reviewer's Guide

This PR updates the devDependency for @biomejs/biome from 1.9.4 to 2.0.2 by bumping the version in package.json—and regenerating the lock file—bringing in the latest bug fixes and CLI improvements from Biome v2.

File-Level Changes

Change	Details	Files
Bump @biomejs/biome to 2.0.2	Update version string in devDependencies Regenerate lock file to pin the new version	package.json package-lock.json

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.