Update all non-major dependencies #29

renovate · 2025-09-08T21:58:03Z

Note

Mend has cancelled the proposed renaming of the Renovate GitHub app being renamed to mend[bot].

This notice will be removed on 2025-10-07.

This PR contains the following updates:

Package	Change	Type	Update
@biomejs/biome (source)	`2.2.2` -> `2.2.5`	devDependencies	patch
@eslint/compat (source)	`1.3.2` -> `1.4.0`	dependencies	minor
@eslint/js (source)	`9.34.0` -> `9.37.0`	dependencies	minor
@stylistic/eslint-plugin (source)	`5.3.1` -> `5.4.0`	dependencies	minor
@types/node (source)	`24.3.0` -> `24.7.0`	devDependencies	minor
@typescript-eslint/parser (source)	`8.42.0` -> `8.46.0`	dependencies	minor
@vitest/eslint-plugin	`1.3.8` -> `1.3.16`	dependencies	patch
eslint-plugin-jsdoc	`54.3.1` -> `54.7.0`	dependencies	minor
eslint-plugin-n	`17.21.3` -> `17.23.1`	dependencies	minor
node (source)	`24.7.0` -> `24.9.0`	volta	minor
npm (source)	`11.6.0` -> `11.6.1`	packageManager	patch
npm (source)	`11.6.0` -> `11.6.1`	volta	patch
typescript (source)	`5.9.2` -> `5.9.3`	devDependencies	patch
typescript-eslint (source)	`8.42.0` -> `8.46.0`	dependencies	minor

Release Notes

biomejs/biome (@biomejs/biome)

`v2.2.5`

Compare Source

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
/**
 * @&#8203;deprecated
 */
export function oldUtility() {}

Valid examples

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

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

// @&#8203;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;
  @&#8203;container (min-width: 600px) {
    display: none;
  }
}

[popover]:popover-open {
  opacity: 1;
  @&#8203;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);
```

`v2.2.4`

Compare Source

Patch Changes

#7453 aa8cea3 Thanks @arendjr! - Fixed #7242: Aliases specified in
package.json's imports section now support having multiple targets as part of an array.
#7454 ac17183 Thanks @arendjr! - Greatly improved performance of
noImportCycles by eliminating allocations.

In one repository, the total runtime of Biome with only noImportCycles enabled went from ~23s down to ~4s.
#7447 7139aad Thanks @rriski! - Fixes #7446. The GritQL
$... spread metavariable now correctly matches members in object literals, aligning its behavior with arrays and function calls.
#6710 98cf9af Thanks @arendjr! - Fixed #4723: Type inference now recognises
index signatures and their accesses when they are being indexed as a string.

Example

type BagOfPromises = {
  // This is an index signature definition. It declares that instances of type
  // `BagOfPromises` can be indexed using arbitrary strings.
  [property: string]: Promise<void>;
};

let bag: BagOfPromises = {};
// Because `bag.iAmAPromise` is equivalent to `bag["iAmAPromise"]`, this is
// considered an access to the string index, and a Promise is expected.
bag.iAmAPromise;

#7415 d042f18 Thanks @qraqras! - Fixed #7212, now the useOptionalChain rule recognizes optional chaining using
typeof (e.g., typeof foo !== 'undefined' && foo.bar).
#7419 576baf4 Thanks @Conaclos! - Fixed #7323. noUnusedPrivateClassMembers no longer reports as unused TypeScript
private members if the rule encounters a computed access on this.

In the following example, member as previously reported as unused. It is no longer reported.
```
class TsBioo {
  private member: number;

  set_with_name(name: string, value: number) {
    this[name] = value;
  }
}
```
351bccd Thanks @ematipico! - Added the new nursery lint rule
noJsxLiterals, which disallows the use of string literals inside JSX.

The rule catches these cases:
```
<>
  <div>test</div> {/* test is invalid */}
  <>test</>
  <div>
    {/* this string is invalid */}
    asdjfl test foo
  </div>
</>
```
#7406 b906112 Thanks @mdevils! - Fixed an issue (#6393) where the useHookAtTopLevel rule reported excessive diagnostics for nested hook calls.

The rule now reports only the offending top-level call site, not sub-hooks of composite hooks.
```
// Before: reported twice (useFoo and useBar).
function useFoo() {
  return useBar();
}
function Component() {
  if (cond) useFoo();
}
// After: reported once at the call to useFoo().
```
#7461 ea585a9 Thanks @arendjr! - Improved performance of
noPrivateImports by eliminating allocations.

In one repository, the total runtime of Biome with only noPrivateImports enabled went from ~3.2s down to ~1.4s.
351bccd Thanks @ematipico! - Fixed #7411. The Biome Language Server had a regression where opening an editor with a file already open wouldn't load the project settings correctly.
#7142 53ff5ae Thanks @Netail! - Added the new nursery rule noDuplicateDependencies, which verifies that no dependencies are duplicated between the
bundledDependencies, bundleDependencies, dependencies, devDependencies, overrides,
optionalDependencies, and peerDependencies sections.

For example, the following snippets will trigger the rule:
```
{
  "dependencies": {
    "foo": ""
  },
  "devDependencies": {
    "foo": ""
  }
}
```
```
{
  "dependencies": {
    "foo": ""
  },
  "optionalDependencies": {
    "foo": ""
  }
}
```
```
{
  "dependencies": {
    "foo": ""
  },
  "peerDependencies": {
    "foo": ""
  }
}
```
351bccd Thanks @ematipico! - Fixed #3824. Now the option CLI
--color is correctly applied to logging too.

`v2.2.3`

Compare Source

Patch Changes

#7353 4d2b719 Thanks @JeetuSuthar! - Fixed #7340: The linter now allows the navigation property for view-transition in CSS.

Previously, the linter incorrectly flagged navigation: auto as an unknown property. This fix adds navigation to the list of known CSS properties, following the CSS View Transitions spec.
#7275 560de1b Thanks @arendjr! - Fixed #7268: Files that are explicitly passed as CLI arguments are now correctly ignored if they reside in an ignored folder.
#7358 963a246 Thanks @ematipico! - Fixed #7085, now the rule noDescendingSpecificity correctly calculates the specificity of selectors when they are included inside a media query.
#7387 923674d Thanks @qraqras! - Fixed #7381, now the useOptionalChain rule recognizes optional chaining using Yoda expressions (e.g., undefined !== foo && foo.bar).
#7316 f9636d5 Thanks @Conaclos! - Fixed #7289. The rule useImportType now inlines import type into import { type } when the style option is set to inlineType.

Example:
```
import type { T } from "mod";
// becomes
import { type T } from "mod";
```
#7350 bb4d407 Thanks @siketyan! - Fixed #7261: two characters ・ (KATAKANA MIDDLE DOT, U+30FB) and ･ (HALFWIDTH KATAKANA MIDDLE DOT, U+FF65) are no longer considered as valid characters in identifiers. Property keys containing these character(s) are now preserved as string literals.
#7377 811f47b Thanks @ematipico! - Fixed a bug where the Biome Language Server didn't correctly compute the diagnostics of a monorepo setting, caused by an incorrect handling of the project status.
#7245 fad34b9 Thanks @kedevked! - Added the new lint rule useConsistentArrowReturn.

This rule enforces a consistent return style for arrow functions.

Invalid

const f = () => {
  return 1;
};

This rule is a port of ESLint's arrow-body-style rule.

#7370 e8032dd Thanks @fireairforce! - Support dynamic import defer and import source. The syntax looks like:

import.source("foo");
import.source("x", { with: { attr: "val" } });
import.defer("foo");
import.defer("x", { with: { attr: "val" } });

#7369 b1f8cbd Thanks @siketyan! - Range suppressions are now supported for Grit plugins.

For JavaScript, you can suppress a plugin as follows:

// biome-ignore-start lint/plugin/preferObjectSpread: reason
Object.assign({ foo: "bar" }, baz);
// biome-ignore-end lint/plugin/preferObjectSpread: reason

For CSS, you can suppress a plugin as follows:

body {
  /* biome-ignore-start lint/plugin/useLowercaseColors: reason */
  color: #fff;
  /* biome-ignore-end lint/plugin/useLowercaseColors: reason */
}

#7384 099507e Thanks @ematipico! - Reduced the severity of certain diagnostics emitted when Biome deserializes the configuration files.
Now these diagnostics are emitted as Information severity, which means that they won't interfere when running commands with --error-on-warnings
#7302 2af2380 Thanks @unvalley! - Fixed #7301: useReadonlyClassProperties now correctly skips JavaScript files.
#7288 94d85f8 Thanks @ThiefMaster! - Fixed #7286. Files are now formatted with JSX behavior when javascript.parser.jsxEverywhere is explicitly set.

Previously, this flag was only used for parsing, but not for formatting, which resulted in incorrect formatting of conditional expressions when JSX syntax is used in .js files.
#7311 62154b9 Thanks @qraqras! - Added the new nursery rule noUselessCatchBinding. This rule disallows unnecessary catch bindings.
```
try {
    // Do something
- } catch (unused) {}
+ } catch {}
```

#7349 45c1dfe Thanks @ematipico! - Fixed #4298. Biome now correctly formats CSS declarations when it contains one single value:

.bar {
-  --123456789012345678901234567890: var(--1234567890123456789012345678901234567);
+  --123456789012345678901234567890: var(
+    --1234567890123456789012345678901234567
+  );
}

#7295 7638e84 Thanks @ematipico! - Fixed #7130. Removed the emission of a false-positive diagnostic. Biome no longer emits the following diagnostic:

lib/main.ts:1:5 suppressions/unused ━━━━━━━━━━━━━━━━━━━━━━━━━

  ⚠ Suppression comment has no effect because the tool is not enabled.

  > 1 │ /** biome-ignore-all assist/source/organizeImports: For the lib root file, we don't want to organize exports */
      │     ^^^^^^^^^^^^^^^^

#7377 811f47b Thanks @ematipico! - Fixed #7371 where the Biome Language Server didn't correctly recompute the diagnostics when updating a nested configuration file.
#7348 ac27fc5 Thanks @ematipico! - Fixed #7079. Now the rule useSemanticElements doesn't trigger components and custom elements.
#7389 ab06a7e Thanks @Conaclos! - Fixed #7344. useNamingConvention no longer reports interfaces defined in global declarations.

Interfaces declared in global declarations augment existing interfaces.
Thus, they must be ignored.

In the following example, useNamingConvention reported HTMLElement.
It is now ignored.
```
export {};
declare global {
  interface HTMLElement {
    foo(): void;
  }
}
```
#7315 4a2bd2f Thanks @vladimir-ivanov! - Fixed #7310: useReadonlyClassProperties correctly handles nested assignments, avoiding false positives when a class property is assigned within another assignment expression.

Example of code that previously triggered a false positive but is now correctly ignored:
```
class test {
  private thing: number = 0; // incorrectly flagged

  public incrementThing(): void {
    const temp = { x: 0 };
    temp.x = this.thing++;
  }
}
```

eslint/rewrite (@eslint/compat)

`v1.4.0`

Compare Source

Features

Add config types in @eslint/core (#237) (7b6dd37)

Dependencies

The following workspace dependencies were updated
- dependencies
  - @eslint/core bumped from ^0.15.2 to ^0.16.0

eslint/eslint (@eslint/js)

`v9.37.0`

Compare Source

`v9.36.0`

Compare Source

Features

47afcf6 feat: correct preserve-caught-error edge cases (#20109) (Francesco Trotta)

Bug Fixes

75b74d8 fix: add missing rule option types (#20127) (ntnyq)
1c0d850 fix: update eslint-all.js to use Object.freeze for rules object (#20116) (루밀LuMir)
7d61b7f fix: add missing scope types to Scope.type (#20110) (Pixel998)
7a670c3 fix: correct rule option typings in rules.d.ts (#20084) (Pixel998)

Documentation

b73ab12 docs: update examples to use defineConfig (#20131) (sethamus)
31d9392 docs: fix typos (#20118) (Pixel998)
c7f861b docs: Update README (GitHub Actions Bot)
6b0c08b docs: Update README (GitHub Actions Bot)
91f97c5 docs: Update README (GitHub Actions Bot)

Chores

12411e8 chore: upgrade @eslint/js@9.36.0 (#20139) (Milos Djermanovic)
488cba6 chore: package.json update for @eslint/js release (Jenkins)
bac82a2 ci: simplify renovate configuration (#19907) (唯然)
c00bb37 ci: bump actions/labeler from 5 to 6 (#20090) (dependabot[bot])
fee751d refactor: use defaultOptions in rules (#20121) (Pixel998)
1ace67d chore: update example to use defineConfig (#20111) (루밀LuMir)
4821963 test: add missing loc information to error objects in rule tests (#20112) (루밀LuMir)
b42c42e chore: disallow use of deprecated type property in core rule tests (#20094) (Milos Djermanovic)
7bb498d test: remove deprecated type property from core rule tests (#20093) (Pixel998)
e10cf2a ci: bump actions/setup-node from 4 to 5 (#20089) (dependabot[bot])
5cb0ce4 refactor: use meta.defaultOptions in preserve-caught-error (#20080) (Pixel998)
f9f7cb5 chore: package.json update for eslint-config-eslint release (Jenkins)
81764b2 chore: update eslint peer dependency in eslint-config-eslint (#20079) (Milos Djermanovic)

`v9.35.0`

Compare Source

eslint-stylistic/eslint-stylistic (@stylistic/eslint-plugin)

`v5.4.0`

Compare Source

Features

generator-star-spacing: introduce shorthand to override property function shorthands (#980) (62d7a17)
introduce experimental mechanism (#894) (87f09ee)
object-curly-spacing: introduce overrides (#898) (2a422b7)

Bug Fixes

correctly display the deprecation warning (#967) (094aa48)
multiline-comment-style: correctly handle ignored comments (#969) (cad56b2)
quote-props: only check ES3 reserved words for keywords option (#964) (bc4810f)
update deps (#983) (86596f9)

Documentation

indent: introduce assignmentOperator (#974) (8a096a8)
max-len: clarify that ignorePattern needs to be a string (#981) (d38b703)

Build Related

deps: bump actions/setup-node from 4 to 5 (#976) (2983f00)

typescript-eslint/typescript-eslint (@typescript-eslint/parser)