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

[dependabot]

Bumps @biomejs/biome from 1.9.4 to 2.3.4.

Release notes

Sourced from @​biomejs/biome's releases.

Biome CLI v2.3.4

2.3.4

Patch Changes

• #7989 4855c4a Thanks @​alissonlauffer! - Fixed a regression in Astro frontmatter parsing where comments inside quoted strings were incorrectly detected as actual comments. This caused the parser to prematurely terminate frontmatter parsing when encountering strings like const test = "//";. For example, the following Astro frontmatter now parses correctly:

  ---
  const test = "// not a real comment";
  ---

• #7968 0b28f5f Thanks @​denbezrukov! - Refactored formatter to use strict Token element for better performance. The new Token variant is optimized for static, ASCII-only text (keywords, operators, punctuation) with the following constraints:

  • ASCII only (no Unicode characters)
  • No newlines (\n, \r)
  • No tab characters (\t)

  This enables faster printing and fitting logic by using bulk string operations (push_str, len()) instead of character-by-character iteration with Unicode width calculations.

• #7941 19b8280 Thanks @​Conaclos! - Fixed #7943. Rules' options are now properly merged with the inherited options from a shared configuration.

  This means that you can now override a specific option from a rule without resetting the other options to their default.

  Given the following shared configuration:

  {
    "linter": {
      "rules": {
        "style": {
          "useNamingConvention": {
            "level": "on",
            "options": {
              "strictCase": false,
              "conventions": [
                {
                  "selector": { "kind": "variable", "scope": "global" },
                  "formats": ["CONSTANT_CASE"]
                }
              ]
            }
          }
        }
      }
    }
  }

... (truncated)

Changelog

Sourced from @​biomejs/biome's changelog.

2.3.4

Patch Changes

• #7989 4855c4a Thanks @​alissonlauffer! - Fixed a regression in Astro frontmatter parsing where comments inside quoted strings were incorrectly detected as actual comments. This caused the parser to prematurely terminate frontmatter parsing when encountering strings like const test = "//";. For example, the following Astro frontmatter now parses correctly:

  ---
  const test = "// not a real comment";
  ---

• #7968 0b28f5f Thanks @​denbezrukov! - Refactored formatter to use strict Token element for better performance. The new Token variant is optimized for static, ASCII-only text (keywords, operators, punctuation) with the following constraints:

  • ASCII only (no Unicode characters)
  • No newlines (\n, \r)
  • No tab characters (\t)

  This enables faster printing and fitting logic by using bulk string operations (push_str, len()) instead of character-by-character iteration with Unicode width calculations.

• #7941 19b8280 Thanks @​Conaclos! - Fixed #7943. Rules' options are now properly merged with the inherited options from a shared configuration.

  This means that you can now override a specific option from a rule without resetting the other options to their default.

  Given the following shared configuration:

  {
    "linter": {
      "rules": {
        "style": {
          "useNamingConvention": {
            "level": "on",
            "options": {
              "strictCase": false,
              "conventions": [
                {
                  "selector": { "kind": "variable", "scope": "global" },
                  "formats": ["CONSTANT_CASE"]
                }
              ]
            }
          }
        }
      }
    }
  }

  And the user configuration that extends this shared configuration:

... (truncated)

Commits

• e8b6753 ci: release (#7965)
• ec24456 chore: add graphite as bronze sponsor (#7974)
• 19b8280 fix(config): implement Merge for rules' options (#7941)
• c9e20c3 feat(lint): implement noContinue (#7856)
• fd282fc ci: release (#7916)
• 198a371 chore: update Rust to v1.91.0 (#7947)
• 2509b91 feat(lint): implement no-unknown-property from eslint react (#7774)
• 69cecec feat(lint): new rule: no parameters only used in recursion (#7926)
• 6d95a67 ci: release (#7887)
• c600618 feat(lint): implement noIncrementDecrement (#7859)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by ematipico, a new releaser for @​biomejs/biome since your current version.

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 CodeRabbit

• Chores
  • Updated development tooling to improve code quality and performance.

[coderabbitai]

Walkthrough

Updated the Biome linter dev dependency in package.json from version 1.9.4 to 2.3.4, moving from a minor version to a new feature release.

Changes

Cohort / File(s)	Summary
Dependency update package.json	Updated @biomejs/biome devDependency from ^1.9.4 to ^2.3.4

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Verify that the version bump is intentional and aligns with project requirements
• Check Biome release notes for v2.x to identify potential breaking changes or new configuration requirements
• Ensure existing CI/CD pipelines and linting configurations remain compatible with the new version

Pre-merge checks and finishing touches

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically describes the main change: bumping the @biomejs/biome dev dependency from version 1.9.4 to 2.3.4, which matches the changeset perfectly.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch dependabot/npm_and_yarn/biomejs/biome-2.3.4

---

📜 Recent review details

Configuration used: Repository: lokalise/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Pro

Disabled knowledge base sources:

• Jira integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 84bdba8 and 595cfed.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (1)

• package.json (1 hunks)

🔇 Additional comments (1)

package.json (1)

29-29: Biome 2.3.4 is compatible; address the unused suppression warning.

Verification confirms that the upgrade to Biome 2.3.4 is compatible with the project. The linting scripts execute successfully, and the noDefaultExport rule exists in Biome 2.x with category lint/style/noDefaultExport. The configuration merging breaking change mentioned in the PR objectives does not cause fatal errors.

However, linting reports an "unused" suppression warning at vite.config.ts:5. The suppression comment syntax is correct for Biome 2.x, but Biome flagged it as having no effect. Investigate whether:

• The rule is disabled or excluded in your biome.json configuration
• The rule detection or suppression matching behavior changed in v2.3.4

Run npm run lint to verify the current state and consider updating the biome configuration if the suppression is no longer needed or requires adjustment.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}