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

Biome CLI v2.2.5

2.2.5

Patch Changes

• #7597 5c3d542 Thanks @​arendjr! - Fixed #6432: useImportExtensions now works correctly with aliased paths.

• #7269 f18dac1 Thanks @​CDGardner! - Fixed #6648, where Biome's noUselessFragments contained inconsistencies with ESLint for fragments only containing text.

  Previously, Biome would report that fragments with only text were unnecessary under the noUselessFragments rule. Further analysis of ESLint's behavior towards these cases revealed that text-only fragments (<>A</a>, <React.Fragment>B</React.Fragment>, <RenamedFragment>B</RenamedFragment>) would not have noUselessFragments emitted for them.

  On the Biome side, instances such as these would emit noUselessFragments, and applying the suggested fix would turn the text content into a proper JS string.

  // Ended up as: - const t = "Text"
  const t = <>Text</>
  // Ended up as: - const e = t ? "Option A" : "Option B"
  
  const e = t ? <>Option A</> : <>Option B</>
  /* Ended up as:
  
  function someFunc() {
  
  return "Content desired to be a multi-line block of text."
  
  }
  
  */
  
  function someFunc() {
  
  return <>
  
  Content desired to be a multi-line
  
  block of text.
  
  <>
  
  }
  
  

  The proposed update was to align Biome's reaction to this rule with ESLint's; the aforementioned examples will now be supported from Biome's perspective, thus valid use of fragments.

  // These instances are now valid and won't be called out by noUselessFragments.
  const t = <>Text</>
  
  const e = t ? <>Option A</> : <>Option B</>
  function someFunc() {
  
  return <>
  
  Content desired to be a multi-line
  
  block of text.
  
  <>
  
  }
  
  

... (truncated)

• 521d149 ci: release (#7478)
• fa4fcd3 docs: fix correct graphql references (#7623)
• 2b9b9d8 chore(deps): update rust crate libc to 0.2.176 (#7612)
• 1af9931 docs: extra rule sources (#7522)
• a50ff37 chore(deps): update github-actions (#7611)
• fea905f fix(lint/useOptionalChain): fix incorrect suggestions for typeof checks on ...
• c294644 feat(biome-js-analyze): add is_meaningful_read to semantic class reads (#7543)
• 5c3d542 fix(linter): fix aliased paths in useImportExtensions (#7597)
• f18dac1 fix(lint/complexity/noUselessFragments): address inconsistencies against ESLi...
• 8653921 fix(noDuplicateProperties): false positives in @container and `@starting-st...
• Additional commits viewable in compare view

Sourced from @​biomejs/biome's releases.

Biome CLI v2.2.5

2.2.5

Patch Changes

• #7597 5c3d542 Thanks @​arendjr! - Fixed #6432: useImportExtensions now works correctly with aliased paths.

• #7269 f18dac1 Thanks @​CDGardner! - Fixed #6648, where Biome's noUselessFragments contained inconsistencies with ESLint for fragments only containing text.

  Previously, Biome would report that fragments with only text were unnecessary under the noUselessFragments rule. Further analysis of ESLint's behavior towards these cases revealed that text-only fragments (<>A</a>, <React.Fragment>B</React.Fragment>, <RenamedFragment>B</RenamedFragment>) would not have noUselessFragments emitted for them.

  On the Biome side, instances such as these would emit noUselessFragments, and applying the suggested fix would turn the text content into a proper JS string.

  // Ended up as: - const t = "Text"
  const t = <>Text</>
  // Ended up as: - const e = t ? "Option A" : "Option B"
  
  const e = t ? <>Option A</> : <>Option B</>
  /* Ended up as:
  
  function someFunc() {
  
  return "Content desired to be a multi-line block of text."
  
  }
  
  */
  
  function someFunc() {
  
  return <>
  
  Content desired to be a multi-line
  
  block of text.
  
  <>
  
  }
  
  

  The proposed update was to align Biome's reaction to this rule with ESLint's; the aforementioned examples will now be supported from Biome's perspective, thus valid use of fragments.

  // These instances are now valid and won't be called out by noUselessFragments.
  const t = <>Text</>
  
  const e = t ? <>Option A</> : <>Option B</>
  function someFunc() {
  
  return <>
  
  Content desired to be a multi-line
  
  block of text.
  
  <>
  
  }
  
  

... (truncated)

Sourced from @​biomejs/biome's changelog.

2.2.5

Patch Changes

• #7597 5c3d542 Thanks @​arendjr! - Fixed #6432: useImportExtensions now works correctly with aliased paths.

• #7269 f18dac1 Thanks @​CDGardner! - Fixed #6648, where Biome's noUselessFragments contained inconsistencies with ESLint for fragments only containing text.

  Previously, Biome would report that fragments with only text were unnecessary under the noUselessFragments rule. Further analysis of ESLint's behavior towards these cases revealed that text-only fragments (<>A</a>, <React.Fragment>B</React.Fragment>, <RenamedFragment>B</RenamedFragment>) would not have noUselessFragments emitted for them.

  On the Biome side, instances such as these would emit noUselessFragments, and applying the suggested fix would turn the text content into a proper JS string.

  // Ended up as: - const t = "Text"
  const t = <>Text</>
  // Ended up as: - const e = t ? "Option A" : "Option B"
  
  const e = t ? <>Option A</> : <>Option B</>
  /* Ended up as:
  
  function someFunc() {
  
  return "Content desired to be a multi-line block of text."
  
  }
  
  */
  
  function someFunc() {
  
  return <>
  
  Content desired to be a multi-line
  
  block of text.
  
  <>
  
  }
  
  

  The proposed update was to align Biome's reaction to this rule with ESLint's; the aforementioned examples will now be supported from Biome's perspective, thus valid use of fragments.

  // These instances are now valid and won't be called out by noUselessFragments.
  const t = <>Text</>
  
  const e = t ? <>Option A</> : <>Option B</>
  function someFunc() {
  
  return <>
  
  Content desired to be a multi-line
  
  block of text.
  
  <>
  
  }
  
  

• #7498 002cded Thanks @​siketyan! - Fixed #6893: The useExhaustiveDependencies rule now correctly adds a dependency that is captured in a shorthand object member. For example:

... (truncated)

• 521d149 ci: release (#7478)
• cadad2c feat(lint): implement noVueDuplicateKeys rule (#7542)
• 9637f93 feat: add useConsistentArrowReturn options (#7457)
• 1b61631 feat(lint): add noReactForwardRef rule (#7509)
• 74d3c56 chore: add convex to bronze sponsors (#7566)
• 3f06e19 feat(linter): implement noDeprecatedImports (#7520)
• a0039fd feat(linter): implement noUnusedExpressions (#7511)
• fd126d7 chore: fix markdown syntax in changelog
• b2da976 chore: fix changelog formatting
• 0109940 chore: repair changelog (#7477)
• Additional commits viewable in compare view

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