chore(deps): update all non-major dependencies

[renovate[bot]]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@nuxt/eslint-config (source)	0.5.4 -> 0.5.7
@types/node (source)	20.16.1 -> 20.16.11
bumpp	9.4.1 -> 9.7.1
expect-type	1.0.0 -> 1.1.0
husky	9.0.11 -> 9.1.6
playwright (source)	1.43.1 -> 1.48.0
pnpm (source)	9.8.0 -> 9.12.1
typescript (source)	5.4.5 -> 5.6.3
vitest-environment-nuxt	1.0.0 -> 1.0.1

---

Release Notes

nuxt/eslint (@​nuxt/eslint-config)

v0.5.7

Compare Source

   🚀 Features

• Update deps, remove @types/eslint  -  by @​antfu (a24f3)

    View changes on GitHub

v0.5.6

Compare Source

   🚀 Features

• module: Support customizable config.configFile, use relative path to resolve, fix #​495  -  by @​antfu in https://github.com/nuxt/eslint/issues/495 (a4ab4)

    View changes on GitHub

v0.5.5

Compare Source

   🐞 Bug Fixes

• Remove unused dependencies  -  by @​bluwy in https://github.com/nuxt/eslint/issues/493 (46d0d)

    View changes on GitHub

antfu/bumpp (bumpp)

v9.7.1

Compare Source

v9.7.0

Compare Source

v9.6.1

Compare Source

   🚀 Features

• Improve commit printing  -  by @​antfu (aaad5)

    View changes on GitHub

v9.6.0

Compare Source

   🚀 Features

• Print recent commits since last tag  -  by @​antfu (0e377)

   🐞 Bug Fixes

• The recursive option is not working in the bump.config.ts file  -  by @​gz65555 in https://github.com/antfu-collective/bumpp/issues/42 (4fda6)
• Improve printed commit messages  -  by @​antfu (2e634)

    View changes on GitHub

v9.5.2

Compare Source

   🐞 Bug Fixes

• Check file exists before update  -  by @​ryoppippi in https://github.com/antfu-collective/bumpp/issues/40 (cf526)

    View changes on GitHub

v9.5.1

Compare Source

   🚀 Features

• Read deno.jsonc for version check  -  by @​ryoppippi in https://github.com/antfu-collective/bumpp/issues/39 (6f4cb)

    View changes on GitHub

v9.5.0

Compare Source

v9.4.2

Compare Source

mmkal/expect-type (expect-type)

v1.1.0

Compare Source

What's Changed

• Add .toBeBigInt() by @​aryaemami59 in https://github.com/mmkal/expect-type/pull/123
• [ci] try artifact.ci by @​mmkal in https://github.com/mmkal/expect-type/pull/124
• bigint printtype by @​mmkal in https://github.com/mmkal/expect-type/pull/125

Full Changelog: https://github.com/mmkal/expect-type/compare/v1.0.0...v1.1.0

typicode/husky (husky)

v9.1.6

Compare Source

v9.1.5

Compare Source

v9.1.4

Compare Source

v9.1.3

Compare Source

• fix: better handle space in PATH

v9.1.2

Compare Source

v9.1.1

Compare Source

v9.1.0

Compare Source

Super saiyan ~~god~~ dog! It's over 9.0.0!

There's a bug with this release which prevents the deprecation notice to appear and requires to remove #!/usr/bin/env sh and . "$(dirname -- "$0")/_/husky.sh" (which are deprecated by the way). I'll publish a new version to fix that. Sorry about any inconvenience.

What's new

You can now run package commands directly, no need for npx or equivalents. It makes writing hooks more intuitive and is also slightly faster 🐺⚡️

### .husky/pre-commit
- npx jest
+ jest # ~0.2s faster

A new recipe has been added to the docs. Lint staged files without external dependencies (inspired by Prettier docs). Feel free to modify it.

### .husky/pre-commit
prettier $(git diff --cached --name-only --diff-filter=ACMR | sed 's| |\\ |g') --write --ignore-unknown
git update-index --again

For more advanced use cases, see lint-staged.

Fixes

• bunx husky init command
• Workaround for some hooks implementation on Windows 🤷

Deprecations

• Remove #!/usr/bin/env sh and . "$(dirname -- "$0")/_/husky.sh" from your hooks
• Move your code from ~/.huskyrc to .config/husky/init.sh

Support for these will be removed in v10, notices have been added.

Friendly reminder

If Git hooks don't fit your workflow, you can disable Husky globally. Just add export HUSKY=0 to .config/husky/init.sh.

I've seen some confusion about this on X, so just a heads-up!

Sponsoring

Husky is downloaded over 45M times per month and used by ~1.5M projects. If your company wants to sponsor, you can do so here: GitHub Sponsors.

Have a nice summer ☀️ I'm open to new opportunities/consulting so feel free to drop me a message 😉

microsoft/playwright (playwright)

v1.48.0

Compare Source

v1.47.2

Compare Source

Highlights

https://github.com/microsoft/playwright/pull/32699- [REGRESSION]: fix(codegen): use content_frame property in python/.NEThttps://github.com/microsoft/playwright/issues/327066- [REGRESSION]: page.pause() does not pause test timeout after 1.4https://github.com/microsoft/playwright/pull/3266161 - fix(trace-viewer): time delta between local and remote actions

Browser Versions

• Chromium 129.0.6668.29
• Mozilla Firefox 130.0
• WebKit 18.0

This version was also tested against the following stable channels:

• Google Chrome 128
• Microsoft Edge 128

v1.47.1

Compare Source

v1.47.0

Compare Source

v1.46.1

Compare Source

v1.46.0

Compare Source

v1.45.3

Compare Source

v1.45.2

Compare Source

v1.45.1

Compare Source

v1.45.0

Compare Source

v1.44.1

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/30779 - [REGRESSION]: When using video: 'on' with VSCode extension the browser got closed https://github.com/microsoft/playwright/issues/30755 - [REGRESSION]: Electron launch with spaces inside executablePath didn't workhttps://github.com/microsoft/playwright/issues/307700 - [REGRESSION]: Mask elements outside of viewport when creating fullscreen screenshots didn't worhttps://github.com/microsoft/playwright/issues/3085858 - [REGRESSION]: ipv6 got shown instead of localhost in show-trace/show-report

Browser Versions

• Chromium 125.0.6422.14
• Mozilla Firefox 125.0.1
• WebKit 17.4

This version was also tested against the following stable channels:

• Google Chrome 124
• Microsoft Edge 124

v1.44.0

Compare Source

New APIs

Accessibility assertions

• expect(locator).toHaveAccessibleName() checks if the element has the specified accessible name:

  const locator = page.getByRole('button');
  await expect(locator).toHaveAccessibleName('Submit');
  

• expect(locator).toHaveAccessibleDescription() checks if the element has the specified accessible description:

  const locator = page.getByRole('button');
  await expect(locator).toHaveAccessibleDescription('Upload a photo');
  

• expect(locator).toHaveRole() checks if the element has the specified ARIA role:

  const locator = page.getByTestId('save-button');
  await expect(locator).toHaveRole('button');
  

Locator handler

• After executing the handler added with page.addLocatorHandler(), Playwright will now wait until the overlay that triggered the handler is not visible anymore. You can opt-out of this behavior with the new noWaitAfter option.
• You can use new times option in page.addLocatorHandler() to specify maximum number of times the handler should be run.
• The handler in page.addLocatorHandler() now accepts the locator as argument.
• New page.removeLocatorHandler() method for removing previously added locator handlers.

const locator = page.getByText('This interstitial covers the button');
await page.addLocatorHandler(locator, async overlay => {
  await overlay.locator('#close').click();
}, { times: 3, noWaitAfter: true });
// Run your tests that can be interrupted by the overlay.
// ...
await page.removeLocatorHandler(locator);

Miscellaneous options

• multipart option in apiRequestContext.fetch() now accepts FormData and supports repeating fields with the same name.

  const formData = new FormData();
  formData.append('file', new File(['let x = 2024;'], 'f1.js', { type: 'text/javascript' }));
  formData.append('file', new File(['hello'], 'f2.txt', { type: 'text/plain' }));
  context.request.post('https://example.com/uploadFiles', {
    multipart: formData
  });
  

• expect(callback).toPass({ intervals }) can now be configured by expect.toPass.inervals option globally in testConfig.expect or per project in testProject.expect.

• expect(page).toHaveURL(url) now supports ignoreCase option.

• testProject.ignoreSnapshots allows to configure per project whether to skip screenshot expectations.

Reporter API

• New method suite.entries() returns child test suites and test cases in their declaration order. suite.type and testCase.type can be used to tell apart test cases and suites in the list.
• Blob reporter now allows overriding report file path with a single option outputFile. The same option can also be specified as PLAYWRIGHT_BLOB_OUTPUT_FILE environment variable that might be more convenient on CI/CD.
• JUnit reporter now supports includeProjectInTestName option.

Command line

• --last-failed CLI option for running only tests that failed in the previous run.

  First run all tests:

  $ npx playwright test
  
  Running 103 tests using 5 workers
  ...
  2 failed
    [chromium] › my-test.spec.ts:8:5 › two ─────────────────────────────────────────────────────────
    [chromium] › my-test.spec.ts:13:5 › three ──────────────────────────────────────────────────────
  101 passed (30.0s)
  

  Now fix the failing tests and run Playwright again with --last-failed option:

  $ npx playwright test --last-failed
  
  Running 2 tests using 2 workers
    2 passed (1.2s)
  

Browser Versions

• Chromium 125.0.6422.14
• Mozilla Firefox 125.0.1
• WebKit 17.4

This version was also tested against the following stable channels:

• Google Chrome 124
• Microsoft Edge 124

pnpm/pnpm (pnpm)

v9.12.1: pnpm 9.12.1

Compare Source

Patch Changes

• pnpm update --latest should not update the automatically installed peer dependencies #​6657.
• pnpm publish should be able to publish from a local tarball #​7950.
• The pnpx command should work correctly on Windows, when pnpm is installed via the standalone installation script #​8608.
• Prevent EBUSY errors caused by creating symlinks in parallel dlx processes #​8604.
• Fix maximum call stack size exceeded error related to circular workspace dependencies #​8599.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v9.12.0: pnpm 9.12

Compare Source

Minor Changes

• Fix peer dependency resolution dead lock #​8570. This change might change some of the keys in the snapshots field inside pnpm-lock.yaml but it should happen very rarely.

• pnpm outdated command supports now a --sort-by=name option for sorting outdated dependencies by package name #​8523.

• Added the ability for overrides to remove dependencies by specifying "-" as the field value #​8572. For example, to remove lodash from the dependencies, use this configuration in package.json:

  {
    "pnpm": {
      "overrides": {
        "lodash": "-"
      }
    }
  }
  

Patch Changes

• Fixed an issue where pnpm list --json pkg showed "private": false for a private package #​8519.
• Packages with libc that differ from pnpm.supportedArchitectures.libc are not downloaded #​7362.
• Prevent ENOENT errors caused by running store prune in parallel #​8586.
• Add issues alias to pnpm bugs #​8596.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v9.11.0

Compare Source

v9.10.0: pnpm 9.10

Compare Source

Minor Changes

• Support for a new CLI flag, --exclude-peers, added to the list and why commands. When --exclude-peers is used, peer dependencies are not printed in the results, but dependencies of peer dependencies are still scanned #​8506.

• Added a new setting to package.json at pnpm.auditConfig.ignoreGhsas for ignoring vulnerabilities by their GHSA code #​6838.

  For instance:

  {
    "pnpm": {
      "auditConfig": {
        "ignoreGhsas": [
          "GHSA-42xw-2xvc-qx8m",
          "GHSA-4w2v-q235-vp99",
          "GHSA-cph5-m8f7-6c5x",
          "GHSA-vh95-rmgr-6w4m"
        ]
      }
    }
  }
  

Patch Changes

• Throw an exception if pnpm switches to the same version of itself.
• Reduce memory usage during peer dependencies resolution.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v9.9.0

Compare Source

microsoft/TypeScript (typescript)

v5.6.3

Compare Source

v5.6.2

Compare Source

v5.5.4: TypeScript 5.5.4

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

• fixed issues query for TypeScript v5.5.4 (Stable).
• fixed issues query for TypeScript v5.5.3 (Stable).
• fixed issues query for TypeScript v5.5.2 (Stable).
• fixed issues query for TypeScript v5.5.1 (RC).
• fixed issues query for TypeScript v5.5.0 (Beta).

Downloads are available on:

• npm
• NuGet package (soon!)

v5.5.3: TypeScript 5.5.3

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

• fixed issues query for TypeScript v5.5.3 (Stable).
• fixed issues query for TypeScript v5.5.2 (Stable).
• fixed issues query for TypeScript v5.5.1 (RC).
• fixed issues query for TypeScript v5.5.0 (Beta).

Downloads are available on:

• npm
• NuGet package

v5.5.2: TypeScript 5.5

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

• fixed issues query for TypeScript v5.5.2 (Stable).
• fixed issues query for TypeScript v5.5.1 (RC).
• fixed issues query for TypeScript v5.5.0 (Beta).

Downloads are available on:

• npm

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - "before 4am on Monday" (UTC).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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[bot]]

[!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.

---

🪧 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 resolve resolve all the CodeRabbit review comments.
• @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.

[socket-security[bot]]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@nuxt/[email protected]	Transitive: environment, filesystem, unsafe	+148	25.1 MB	antfu
npm/@nuxt/[email protected]	Transitive: environment, filesystem, network, shell, unsafe	+74	6.17 MB	danielroe
npm/@nuxt/[email protected]	Transitive: environment	+16	10.5 MB	danielroe
npm/@nuxt/[email protected]	Transitive: environment	+11	2.09 MB	danielroe
npm/@nuxt/[email protected]	Transitive: environment, eval, filesystem, network, shell, unsafe	+298	34.8 MB	danielroe
npm/@types/[email protected]	None	0	2.21 MB	types
npm/@vitest/[email protected]	Transitive: environment, filesystem, shell	+56	10.2 MB	vitestbot
npm/[email protected]	environment, filesystem, unsafe Transitive: network, shell	+77	7.19 MB	antfu
npm/[email protected]	environment Transitive: eval, filesystem, shell, unsafe	+79	9.79 MB	eslintbot
npm/[email protected]	None	0	110 kB	mmkale
npm/[email protected]	environment, filesystem, shell	0	4.03 kB	typicode
npm/[email protected]	Transitive: environment, eval, filesystem, network, shell, unsafe	+991	158 MB	danielroe
npm/[email protected]	None	+1	10.8 MB	dgozman, dgozman-ms, pavelfeldman, ...1 more

🚮 Removed packages: npm/@nuxt/[email protected], npm/@nuxt/[email protected], npm/@nuxt/[email protected], npm/@nuxt/[email protected], npm/@nuxt/[email protected], npm/@types/[email protected], npm/@vitest/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected]

View full report↗︎

[renovate[bot]]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.