build(deps-dev): bump @biomejs/biome from 1.9.4 to 2.3.15 in /website

[dependabot]

Bumps @biomejs/biome from 1.9.4 to 2.3.15.

Release notes

Sourced from @​biomejs/biome's releases.

Biome CLI v2.3.15

2.3.15

Patch Changes

• #9019 043b67c Thanks @​dyc3! - Added the lint rule noNestedPromises. This rule detects nested .then() or .catch() calls that could be refactored into flat promise chains.

  // Invalid: nested promise that can be flattened
  doThing().then(function () {
    return doOtherThing().then(console.log);
  });
  // Valid: flat promise chain
  doThing()
  .then(() => doOtherThing())
  .then(console.log);

  The rule intelligently allows nesting when the inner callback references variables from the outer scope, as these cases cannot be safely flattened.

• #9029 6ebf6c6 Thanks @​ff1451! - Added the nursery rule noUselessReturn. The rule reports redundant return; statements that don't affect the function's control flow.

  // Invalid: return at end of function is redundant
  function foo() {
    doSomething();
    return;
  }

• #9017 8bac2da Thanks @​mdevils! - Reverted a behavior change in useExhaustiveDependencies that was accidentally included as part of the #8802 fix. The change made method calls on objects (e.g., props.data.forEach(...)) report only the object (props.data) as a missing dependency instead of the full member expression. This behavior change will be reconsidered separately.

• #9005 c8dbbbe Thanks @​corvid-agent! - Fixed #8790: The noAssignInExpressions rule no longer reports a false positive when an assignment is used as the expression body of an arrow function (e.g., const f = b => a += b).

• #8519 ccdc602 Thanks @​ruidosujeira! - Fixed #8518, where globally excluded files in a monorepo were still being processed when using "extends": "//".

  When a package-level configuration extends the root configuration with "extends": "//", glob patterns (such as those in files.includes) are now correctly resolved relative to the project root directory, instead of the current workspace directory.

• #9033 0628e0a Thanks @​mdevils! - Fixed #8967. useExhaustiveDependencies no longer reports false positives for variables destructured from a rest pattern.

• #9023 8ef9d1d Thanks @​siketyan! - Fixed #9020: When javascript.jsxRuntime is set to reactClassic, noUnusedImports and useImportType rules now allow importing the React identifier from a package other than react. This aligns the behavior with tsc (--jsx=react), which also allows importing React from any package.

• #8646 16fd71d Thanks @​siketyan! - Fixed #8605: Text expressions in some template languages ({{ expr }} or { expr }) at the top level of an HTML document no longer causes panicking.

• #8930 51c158e Thanks @​ANKANJAGTAP! - Fixed #8917 useExhaustiveDependencies now correctly detects JSX component identifiers as hook dependencies.

• #9009 7d229c7 Thanks @​Netail! - Fixed typo in noPositiveTabindex's quick fix text.

... (truncated)

Changelog

Sourced from @​biomejs/biome's changelog.

2.3.15

Patch Changes

• #9019 043b67c Thanks @​dyc3! - Added the lint rule noNestedPromises. This rule detects nested .then() or .catch() calls that could be refactored into flat promise chains.

  // Invalid: nested promise that can be flattened
  doThing().then(function () {
    return doOtherThing().then(console.log);
  });
  // Valid: flat promise chain
  doThing()
  .then(() => doOtherThing())
  .then(console.log);

  The rule intelligently allows nesting when the inner callback references variables from the outer scope, as these cases cannot be safely flattened.

• #9029 6ebf6c6 Thanks @​ff1451! - Added the nursery rule noUselessReturn. The rule reports redundant return; statements that don't affect the function's control flow.

  // Invalid: return at end of function is redundant
  function foo() {
    doSomething();
    return;
  }

• #9017 8bac2da Thanks @​mdevils! - Reverted a behavior change in useExhaustiveDependencies that was accidentally included as part of the #8802 fix. The change made method calls on objects (e.g., props.data.forEach(...)) report only the object (props.data) as a missing dependency instead of the full member expression. This behavior change will be reconsidered separately.

• #9005 c8dbbbe Thanks @​corvid-agent! - Fixed #8790: The noAssignInExpressions rule no longer reports a false positive when an assignment is used as the expression body of an arrow function (e.g., const f = b => a += b).

• #8519 ccdc602 Thanks @​ruidosujeira! - Fixed #8518, where globally excluded files in a monorepo were still being processed when using "extends": "//".

  When a package-level configuration extends the root configuration with "extends": "//", glob patterns (such as those in files.includes) are now correctly resolved relative to the project root directory, instead of the current workspace directory.

• #9033 0628e0a Thanks @​mdevils! - Fixed #8967. useExhaustiveDependencies no longer reports false positives for variables destructured from a rest pattern.

• #9023 8ef9d1d Thanks @​siketyan! - Fixed #9020: When javascript.jsxRuntime is set to reactClassic, noUnusedImports and useImportType rules now allow importing the React identifier from a package other than react. This aligns the behavior with tsc (--jsx=react), which also allows importing React from any package.

• #8646 16fd71d Thanks @​siketyan! - Fixed #8605: Text expressions in some template languages ({{ expr }} or { expr }) at the top level of an HTML document no longer causes panicking.

• #8930 51c158e Thanks @​ANKANJAGTAP! - Fixed #8917 useExhaustiveDependencies now correctly detects JSX component identifiers as hook dependencies.

• #9009 7d229c7 Thanks @​Netail! - Fixed typo in noPositiveTabindex's quick fix text.

• #8758 8c789f1 Thanks @​Pranav2612000! - Updated the useJsxKeyInIterable rule to not run inside Map constructors

... (truncated)

Commits

• df21006 ci: release (#8973)
• 6ebf6c6 feat(lint): add nursery rule noUselessReturn (#9029)
• 043b67c feat(lint/js): add noNestedPromises (#9019)
• 26d8367 docs: correct default value for useEditorconfig schema setting (#9025)
• 3a38d5c ci: release (#8888)
• 4561751 feat(linter): add rule noRedundantDefaultExport (#8931)
• ccaeac4 feat(biome_js_analyze): implement useGlobalThis (#8928)
• d876a38 feat(lint): implement useConsistentMethodSignatures from `typescript-eslint...
• 9a18daa feat(analyze/js/vue): add noVueArrowFuncInWatch (#8602)
• 3531687 feat(lint/css): add noDeprecatedMediaType (#8861)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), 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 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)

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.