chore(deps): bump the biome group with 2 updates

[dependabot]

Bumps the biome group with 2 updates: @biomejs/wasm-nodejs and @biomejs/biome.

Updates @biomejs/wasm-nodejs from 2.3.6 to 2.3.7

Release notes

Sourced from @​biomejs/wasm-nodejs's releases.

Biome CLI v2.3.7

2.3.7

Patch Changes

• #8169 7fdcec8 Thanks @​arendjr! - Fixed #7999: Correctly place await after leading comment in auto-fix action from noFloatingPromises rule.

• #8157 12d5b42 Thanks @​Conaclos! - Fixed #8148. noInvalidUseBeforeDeclaration no longer reports some valid use before declarations.

  The following code is no longer reported as invalid:

  class classA {
    C = C;
  }
  const C = 0;

• #8178 6ba4157 Thanks @​dyc3! - Fixed #8174, where the HTML parser would parse 2 directives as a single directive because it would not reject whitespace in Vue directives. This would cause the formatter to erroneously merge the 2 directives into one, resulting in broken code.

  - <Component v-else:property="123" />
  + <Component v-else :property="123" />

• #8088 0eb08e8 Thanks @​db295! - Fixed #7876: The noUnusedImports rule now ignores imports that are used by @​linkcode and @​linkplain (previously supported @​link and @​see).

  The following code will no longer be a false positive:

  import type { a } from "a"
  /**
  
  {@​linkcode a}
  */
  function func() {}

#8119 8d64655 Thanks @​ematipico! - Improved the detection of the rule noUnnecessaryConditions. Now the rule isn't triggered for variables that are mutated inside a module.

This logic deviates from the original rule, hence noUnnecessaryConditions is now marked as "inspired".

In the following example, hey starts as false, but then it's assigned to a string. The rule isn't triggered inside the if check.

let hey = false;
function test() {
hey = "string";

... (truncated)

Commits

• 8e97b89 ci: release (#8161)
• 7fc07c1 fix: revert #7684 (#8173)
• bb7a15c fix: only flag object assign in accumulators, if it is allocating a new objec...
• e9f068e fix(biome_analyze): handle suppressed categories properly for range suppressi...
• 6ba4157 fix(parse/html/vue): reject whitespace before vue directive arguments (#8178)
• 0c8349e fix(css): updating formatting of non-lowercase CSS dimension units (#8175)
• fb1458b feat(lint/html/vue): add useVueValidVText (#8158)
• 8d64655 fix(inference): improved inference for assignment types (#8119)
• 0eb08e8 fix(noUnusedImports): parse also linkcode, and not only link (#8088)
• 7fdcec8 fix: correctly place await after comment (#8169)
• Additional commits viewable in compare view

Updates @biomejs/biome from 2.3.6 to 2.3.7

Release notes

Sourced from @​biomejs/biome's releases.

Biome CLI v2.3.7

2.3.7

Patch Changes

• #8169 7fdcec8 Thanks @​arendjr! - Fixed #7999: Correctly place await after leading comment in auto-fix action from noFloatingPromises rule.

• #8157 12d5b42 Thanks @​Conaclos! - Fixed #8148. noInvalidUseBeforeDeclaration no longer reports some valid use before declarations.

  The following code is no longer reported as invalid:

  class classA {
    C = C;
  }
  const C = 0;

• #8178 6ba4157 Thanks @​dyc3! - Fixed #8174, where the HTML parser would parse 2 directives as a single directive because it would not reject whitespace in Vue directives. This would cause the formatter to erroneously merge the 2 directives into one, resulting in broken code.

  - <Component v-else:property="123" />
  + <Component v-else :property="123" />

• #8088 0eb08e8 Thanks @​db295! - Fixed #7876: The noUnusedImports rule now ignores imports that are used by @​linkcode and @​linkplain (previously supported @​link and @​see).

  The following code will no longer be a false positive:

  import type { a } from "a"
  /**
  
  {@​linkcode a}
  */
  function func() {}

#8119 8d64655 Thanks @​ematipico! - Improved the detection of the rule noUnnecessaryConditions. Now the rule isn't triggered for variables that are mutated inside a module.

This logic deviates from the original rule, hence noUnnecessaryConditions is now marked as "inspired".

In the following example, hey starts as false, but then it's assigned to a string. The rule isn't triggered inside the if check.

let hey = false;
function test() {
hey = "string";

... (truncated)

Changelog

Sourced from @​biomejs/biome's changelog.

2.3.7

Patch Changes

• #8169 7fdcec8 Thanks @​arendjr! - Fixed #7999: Correctly place await after leading comment in auto-fix action from noFloatingPromises rule.

• #8157 12d5b42 Thanks @​Conaclos! - Fixed #8148. noInvalidUseBeforeDeclaration no longer reports some valid use before declarations.

  The following code is no longer reported as invalid:

  class classA {
    C = C;
  }
  const C = 0;

• #8178 6ba4157 Thanks @​dyc3! - Fixed #8174, where the HTML parser would parse 2 directives as a single directive because it would not reject whitespace in Vue directives. This would cause the formatter to erroneously merge the 2 directives into one, resulting in broken code.

  - <Component v-else:property="123" />
  + <Component v-else :property="123" />

• #8088 0eb08e8 Thanks @​db295! - Fixed #7876: The noUnusedImports rule now ignores imports that are used by @​linkcode and @​linkplain (previously supported @​link and @​see).

  The following code will no longer be a false positive:

  import type { a } from "a"
  /**
  
  {@​linkcode a}
  */
  function func() {}

#8119 8d64655 Thanks @​ematipico! - Improved the detection of the rule noUnnecessaryConditions. Now the rule isn't triggered for variables that are mutated inside a module.

This logic deviates from the original rule, hence noUnnecessaryConditions is now marked as "inspired".

In the following example, hey starts as false, but then it's assigned to a string. The rule isn't triggered inside the if check.

let hey = false;
function test() {
hey = "string";
}

... (truncated)

Commits

• 8e97b89 ci: release (#8161)
• fb1458b feat(lint/html/vue): add useVueValidVText (#8158)
• 2dd38cf fix(schema): domains and feature kind (#8147)
• 803a44a chore: remove gold sponsor (#8135)
• 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[changeset-bot]

⚠️ No Changeset found

Latest commit: 2395af0

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR