chore(deps): update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@eslint/js (source)	9.22.0 -> 9.23.0
@types/chrome (source)	^0.0.309 -> ^0.0.313
@types/node (source)	22.13.10 -> 22.13.14
@vitest/coverage-v8 (source)	3.0.8 -> 3.0.9
eslint (source)	9.22.0 -> 9.23.0
pnpm (source)	10.6.3+sha512.bb45e34d50a9a76e858a95837301bfb6bd6d35aea2c5d52094fa497a467c43f5c440103ce2511e9e0a2f89c3d6071baac3358fc68ac6fb75e2ceb3d2736065e6 -> 10.7.0
typescript-eslint (source)	8.26.1 -> 8.28.0
vitest (source)	3.0.8 -> 3.0.9

---

Release Notes

eslint/eslint (@​eslint/js)

v9.23.0

Compare Source

vitest-dev/vitest (@​vitest/coverage-v8)

v3.0.9

Compare Source

eslint/eslint (eslint)

v9.23.0

Compare Source

pnpm/pnpm (pnpm)

v10.7.0

Compare Source

Minor Changes

• pnpm config get and list also show settings set in pnpm-workspace.yaml files #​9316.

• It should be possible to use env variables in pnpm-workspace.yaml setting names and value.

• Add an ability to patch dependencies by version ranges. Exact versions override version ranges, which in turn override name-only patches. Version range * is the same as name-only, except that patch application failure will not be ignored.

  For example:

  patchedDependencies:
    foo: patches/foo-1.patch
    foo@^2.0.0: patches/foo-2.patch
    [email protected]: patches/foo-3.patch

  The above configuration would apply patches/foo-3.patch to [email protected], patches/foo-2.patch to all foo versions which satisfy ^2.0.0 except 2.1.0, and patches/foo-1.patch to the remaining foo versions.

  [!WARNING]
  The version ranges should not overlap. If you want to specialize a sub range, make sure to exclude it from the other keys. For example:

  # pnpm-workspace.yaml
  patchedDependencies:
    # the specialized sub range
    '[email protected]': patches/foo.2.2.0-2.8.0.patch
    # the more general patch, excluding the sub range above
    'foo@>=2.0.0 <2.2.0 || >2.8.0': 'patches/foo.gte2.patch

  In most cases, however, it's sufficient to just define an exact version to override the range.

• pnpm config set --location=project saves the setting to a pnpm-workspace.yaml file if no .npmrc file is present in the directory #​9316.

• Rename pnpm.allowNonAppliedPatches to pnpm.allowUnusedPatches. The old name is still supported but it would print a deprecation warning message.

• Add pnpm.ignorePatchFailures to manage whether pnpm would ignore patch application failures.

  If ignorePatchFailures is not set, pnpm would throw an error when patches with exact versions or version ranges fail to apply, and it would ignore failures from name-only patches.

  If ignorePatchFailures is explicitly set to false, pnpm would throw an error when any type of patch fails to apply.

  If ignorePatchFailures is explicitly set to true, pnpm would print a warning when any type of patch fails to apply.

Patch Changes

• Remove dependency paths from audit output to prevent out-of-memory errors #​9280.

v10.6.5

Compare Source

v10.6.4: pnpm 10.6.4

Compare Source

Patch Changes

• Fix pnpm dlx with --allow-build flag #​9263.
• Invalid Node.js version in use-node-version should not cause pnpm itself to break #​9276.
• The max amount of workers running for linking packages from the store has been reduced to 4 to achieve optimal results #​9286. The workers are performing many file system operations, so increasing the number of CPUs doesn't help performance after some point.

Platinum Sponsors

Gold Sponsors

typescript-eslint/typescript-eslint (typescript-eslint)

v8.28.0

Compare Source

This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v8.27.0

Compare Source

This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

vitest-dev/vitest (vitest)

v3.0.9

Compare Source

   🐞 Bug Fixes

• Typings of ctx.skip() as never  -  by @​sirlancelot in https://github.com/vitest-dev/vitest/issues/7608 (09f35)
• Cleanup vitest in public resolveConfig API  -  by @​hi-ogawa in https://github.com/vitest-dev/vitest/issues/7623 (db14a)
• Fix toHaveBeenCalledWith(asymmetricMatcher) with undefined arguments  -  by @​hi-ogawa in https://github.com/vitest-dev/vitest/issues/7624 (0fb21)
• Race condition in RPC filesystem cache.  -  by @​dts in https://github.com/vitest-dev/vitest/issues/7531 (b7f55)
• Fix getState().testPath during collection with no isolation  -  by @​hi-ogawa in https://github.com/vitest-dev/vitest/issues/7640 (3fb3f)
• Support custom toString method in %s format  -  by @​pengooseDev in https://github.com/vitest-dev/vitest/issues/7637 (46d93)
• browser:
  • Fail playwright timeouts earlier than a test timeout  -  by @​sheremet-va and @​hi-ogawa in https://github.com/vitest-dev/vitest/issues/7565 (5eb4c)
  • Remove @​testing-library/dom from dependencies #​7555)"  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/7628 and https://github.com/vitest-dev/vitest/issues/7555 (94b27)
• coverage:
  • Browser mode + coverage.all  -  by @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/7597 (422ba)
• runner:
  • Show stacktrace on hook timeout error  -  by @​hi-ogawa in https://github.com/vitest-dev/vitest/issues/7502 (268a1)
• vite-node:
  • Fix source map of inlined node_modules  -  by @​hi-ogawa in https://github.com/vitest-dev/vitest/issues/7557 (34aa3)
  • Fix missing buildStart  -  by @​hi-ogawa in https://github.com/vitest-dev/vitest/issues/7652 (29f5a)
• web-worker:
  • Ensure removeEventListener is bound to worker  -  by @​joelgallant in https://github.com/vitest-dev/vitest/issues/7631 (ff42b)

    View changes on GitHub

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

📢 Thoughts on this report? Let us know!