biomejs/biome @biomejs/biome@2.2.5 on GitHub

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:
```
useEffect(() => {
  console.log({ firstId, secondId });
}, []);
```
is now correctly fixed to:
```
useEffect(() => {
  console.log({ firstId, secondId });
}, [firstId, secondId]);
```
#7509 1b61631 Thanks @siketyan! - Added a new lint rule noReactForwardRef, which detects usages of forwardRef that is no longer needed and deprecated in React 19.
For example:
```
export const Component = forwardRef(function Component(props, ref) {
  return <div ref={ref} />;
});
```
will be fixed to:
```
export const Component = function Component({ ref, ...props }) {
  return <div ref={ref} />;
};
```
Note that the rule provides an unsafe fix, which may break the code. Don't forget to review the code after applying the fix.

#7520 3f06e19 Thanks @arendjr! - Added new nursery rule noDeprecatedImports to flag imports of deprecated symbols.

Invalid example

// foo.js
import { oldUtility } from "./utils.js";

// utils.js
/**
 * @deprecated
 */
export function oldUtility() {}

Valid examples

// foo.js
import { newUtility, oldUtility } from "./utils.js";

// utils.js
export function newUtility() {}

// @deprecated (this is not a JSDoc comment)
export function oldUtility() {}

#7457 9637f93 Thanks @kedevked! - Added style and requireForObjectLiteral options to the lint rule useConsistentArrowReturn.
This rule enforces a consistent return style for arrow functions. It can be configured with the following options:
- style: (default: asNeeded)
  - always: enforces that arrow functions always have a block body.
  - never: enforces that arrow functions never have a block body, when possible.
  - asNeeded: enforces that arrow functions have a block body only when necessary (e.g. for object literals).
style: "always"

Invalid:
```
const f = () => 1;
```
Valid:
```
const f = () => {
  return 1;
};
```
style: "never"

Invalid:
```
const f = () => {
  return 1;
};
```
Valid:
```
const f = () => 1;
```
style: "asNeeded"

Invalid:
```
const f = () => {
  return 1;
};
```
Valid:
```
const f = () => 1;
```
style: "asNeeded" and requireForObjectLiteral: true

Valid:
```
const f = () => {
  return { a: 1 };
};
```

#7510 527cec2 Thanks @rriski! - Implements #7339. GritQL patterns can now use native Biome AST nodes using their PascalCase names, in addition to the existing TreeSitter-compatible snake_case names.

engine biome(1.0)
language js(typescript,jsx)

or {
  // TreeSitter-compatible pattern
  if_statement(),

  // Native Biome AST node pattern
  JsIfStatement()
} as $stmt where {
  register_diagnostic(
    span=$stmt,
    message="Found an if statement"
  )
}

#7574 47907e7 Thanks @kedevked! - Fixed 7574. The diagnostic message for the rule useSolidForComponent now correctly emphasizes <For /> and provides a working hyperlink to the Solid documentation.
#7497 bd70f40 Thanks @siketyan! - Fixed #7320: The useConsistentCurlyBraces rule now correctly detects a string literal including " inside a JSX attribute value.
#7522 1af9931 Thanks @Netail! - Added extra references to external rules to improve migration for the following rules: noUselessFragments & noNestedComponentDefinitions
#7597 5c3d542 Thanks @arendjr! - Fixed an issue where package.json manifests would not be correctly discovered
when evaluating files in the same directory.
#7565 38d2098 Thanks @siketyan! - The resolver can now correctly resolve .ts, .tsx, .d.ts, .js files by .js extension if exists, based on the file extension substitution in TypeScript.
For example, the linter can now detect the floating promise in the following situation, if you have enabled the noFloatingPromises rule.
foo.ts
```
export async function doSomething(): Promise<void> {}
```
bar.ts
```
import { doSomething } from "./foo.js"; // doesn't exist actually, but it is resolved to `foo.ts`

doSomething(); // floating promise!
```

#7542 cadad2c Thanks @mdevils! - Added the rule noVueDuplicateKeys, which prevents duplicate keys in Vue component definitions.

This rule prevents the use of duplicate keys across different Vue component options such as props, data, computed, methods, and setup. Even if keys don't conflict in the script tag, they may cause issues in the template since Vue allows direct access to these keys.

Invalid examples

<script>
export default {
  props: ["foo"],
  data() {
    return {
      foo: "bar",
    };
  },
};
</script>

<script>
export default {
  data() {
    return {
      message: "hello",
    };
  },
  methods: {
    message() {
      console.log("duplicate key");
    },
  },
};
</script>

<script>
export default {
  computed: {
    count() {
      return this.value * 2;
    },
  },
  methods: {
    count() {
      this.value++;
    },
  },
};
</script>

Valid examples

<script>
export default {
  props: ["foo"],
  data() {
    return {
      bar: "baz",
    };
  },
  methods: {
    handleClick() {
      console.log("unique key");
    },
  },
};
</script>

<script>
export default {
  computed: {
    displayMessage() {
      return this.message.toUpperCase();
    },
  },
  methods: {
    clearMessage() {
      this.message = "";
    },
  },
};
</script>

#7546 a683acc Thanks @siketyan! - Internal data for Unicode strings have been updated to Unicode 17.0.
#7497 bd70f40 Thanks @siketyan! - Fixed #7256: The useConsistentCurlyBraces rule now correctly ignores a string literal with braces that contains only whitespaces. Previously, literals that contains single whitespace were only allowed.
#7565 38d2098 Thanks @siketyan! - The useImportExtensions rule now correctly detects imports with an invalid extension. For example, importing .ts file with .js extension is flagged by default. If you are using TypeScript with neither the allowImportingTsExtensions option nor the rewriteRelativeImportExtensions option, it's recommended to turn on the forceJsExtensions option of the rule.
#7581 8653921 Thanks @lucasweng! - Fixed #7470: solved a false positive for noDuplicateProperties. Previously, declarations in @container and @starting-style at-rules were incorrectly flagged as duplicates of identical declarations at the root selector.
For example, the linter no longer flags the display declaration in @container or the opacity declaration in @starting-style.
```
a {
  display: block;
  @container (min-width: 600px) {
    display: none;
  }
}

[popover]:popover-open {
  opacity: 1;
  @starting-style {
    opacity: 0;
  }
}
```
#7529 fea905f Thanks @qraqras! - Fixed #7517: the useOptionalChain rule no longer suggests changes for typeof checks on global objects.
```
// ok
typeof window !== "undefined" && window.location;
```
#7476 c015765 Thanks @ematipico! - Fixed a bug where the suppression action for noPositiveTabindex didn't place the suppression comment in the correct position.
#7511 a0039fd Thanks @arendjr! - Added nursery rule noUnusedExpressions to flag expressions used as a statement that is neither an assignment nor a function call.
Invalid examples
```
f; // intended to call `f()` instead
```
```
function foo() {
  0; // intended to `return 0` instead
}
```
Valid examples
```
f();
```
```
function foo() {
  return 0;
}
```
#7564 40e515f Thanks @turbocrime! - Fixed #6617: improved useIterableCallbackReturn to correctly handle arrow functions with a single-expression void body.
Now the following code doesn't trigger the rule anymore:
```
[].forEach(() => void null);
```

What's Changed

chore: add spanish readme translation by @Terraciano in #7465
feat(yaml_parser): parse block scalars by @l0ngvh in #7417
docs: improve noDuplicateDependencies by @Netail in #7471
chore: repair changelog by @ematipico in #7477
fix(noPositiveTabindex): suppression action by @ematipico in #7476
fix(lint/useConsistentCurlyBraces): adjust condition to allow removing the braces by @siketyan in #7497
fix(lint/useExhaustiveDependencies): correctly fix the dependency list from a shorthand object member by @siketyan in #7498
chore(deps): update rust:1.89.0-bullseye docker digest to 8f72d97 by @renovate[bot] in #7506
chore(deps): update rust:1.89.0-bookworm docker digest to 948f9b0 by @renovate[bot] in #7505
chore(deps): update github-actions by @renovate[bot] in #7503
chore(deps): update docker/dockerfile:1 docker digest to dabfc09 by @renovate[bot] in #7502
chore(deps): update dependency @changesets/cli to v2.29.7 by @renovate[bot] in #7507
chore(deps): update dependency dprint to v0.50.2 by @renovate[bot] in #7508
feat(biome-js-analyze): class member references service by @vladimir-ivanov in #7428
feat(grit): allow matching native Biome AST nodes by @rriski in #7510
feat(linter): implement noUnusedExpressions by @arendjr in #7511
feat(linter): implement noDeprecatedImports by @arendjr in #7520
chore: expose preferred indentation by @arendjr in #7540
chore: update Unicode table for Unicode 17 by @siketyan in #7546
ci: don't run the autofix workflow on an autofix commit by @siketyan in #7550
test: fix failing watcher tests on macOS by @siketyan in #7549
chore(deps): update github-actions by @renovate[bot] in #7554
chore(deps): update rust crate anyhow to 1.0.100 by @renovate[bot] in #7555
chore(deps): update rust crate serde_json to 1.0.145 by @renovate[bot] in #7558
chore(deps): update rust crate tracing-subscriber to 0.3.20 by @renovate[bot] in #7560
chore(deps): update rust crate url to 2.5.7 by @renovate[bot] in #7561
chore(deps): update rust crate serde to 1.0.226 by @renovate[bot] in #7557
chore(deps): update dependency @types/node to v22.18.6 by @renovate[bot] in #7563
chore: add convex to bronze sponsors by @ematipico in #7566
feat(resolver): resolve extension alias by @siketyan in #7565
feat(lint): add noReactForwardRef rule by @siketyan in #7509
perf: don't allocate when pushing or retrieving globals by @arendjr in #7569
feat: add useConsistentArrowReturn options by @kedevked in #7457
fix: set correct string for diagnostic by @kedevked in #7574
feat(lint): implement noVueDuplicateKeys rule by @mdevils in #7542
chore: add edition 2024 to rustfmt.toml by @turbocrime in #7591
fix(lint/suspicious/useIterableCallbackReturn): single-expression void arrow function by @turbocrime in #7564
fix(noDuplicateProperties): false positives in @container and @starting-style at-rules by @lucasweng in #7581
fix(lint/complexity/noUselessFragments): address inconsistencies against ESLint behavior with fragments only containing text. by @CDGardner in #7269
fix(linter): fix aliased paths in useImportExtensions by @arendjr in #7597
feat(biome-js-analyze): add is_meaningful_read to semantic class reads by @vladimir-ivanov in #7543
fix(lint/useOptionalChain): fix incorrect suggestions for typeof checks on global objects by @qraqras in #7529
chore(deps): update github-actions by @renovate[bot] in #7611
docs: extra rule sources by @Netail in #7522
chore(deps): update rust crate libc to 0.2.176 by @renovate[bot] in #7612
docs: fix correct graphql references by @Netail in #7623
ci: release by @github-actions[bot] in #7478

New Contributors

@Terraciano made their first contribution in #7465
@turbocrime made their first contribution in #7591
@CDGardner made their first contribution in #7269

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.2.4...@biomejs/biome@2.2.5

biomejs/biome @biomejs/biome@2.2.5
Biome CLI v2.2.5

on GitHub

2.2.5

Patch Changes

Invalid example

Valid examples

`style: "always"`

`style: "never"`

`style: "asNeeded"`

`style: "asNeeded"` and `requireForObjectLiteral: true`

Invalid examples

Valid examples

Invalid examples

Valid examples

What's Changed

New Contributors

biomejs/biome @biomejs/biome@2.2.5 Biome CLI v2.2.5 on GitHub

2.2.5

Patch Changes

Invalid example

Valid examples

style: "always"

style: "never"

style: "asNeeded"

style: "asNeeded" and requireForObjectLiteral: true

Invalid examples

Valid examples

Invalid examples

Valid examples

What's Changed

New Contributors

biomejs/biome @biomejs/biome@2.2.5
Biome CLI v2.2.5

on GitHub

`style: "always"`

`style: "never"`

`style: "asNeeded"`

`style: "asNeeded"` and `requireForObjectLiteral: true`