chore(deps): update vitest monorepo to v0.32.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@vitest/coverage-c8 (source)	0.31.4 -> 0.32.0
vitest	0.31.4 -> 0.32.0

---

Release Notes

vitest-dev/vitest

v0.32.0

Compare Source

   🚨 Breaking Changes

• Throw an error, if the module cannot be resolved  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/3307 (1ad63)
  • Vitest used to fall back to the original import when it could not resolve it to the file path or the virtual module. This leads to hard-to-find module graph mismatches if you had incorrect alias or relied on relative imports to be resolved to the project root (which is usual behavior in TypeScript) because the code accidentally "worked". With this release, Vitest will now throw an error if it cannot resolve the module - there are possible edge cases that are not covered yet, so if you have any problems with this, please open a separate issue with reproduction.
• Improve globs  -  by @​nickmccurdy in https://github.com/vitest-dev/vitest/issues/3392 (19ecc)
  • Vitest now has glob patterns similar to Jest for better compatibility. It's possible that some files will be considered test files when previously they were not. For example, Vitest now considers test.js to be a test file. Also any file in __tests__ is now considered to be a test, not just files with test or spec suffix.
• Add @vitest/coverage-v8 package  -  by @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/3339 (82112)
  • Vitest now uses v8 code coverage directly for better performance. @vitest/coverage-c8 is deprecated as Vitest no longer uses c8 package for coverage output. It will not be updated anymore, and Vitest will fail in the next version if the user has c8 as their coverage provider. Please, install the new @vitest/coverage-v8 package if you previously used @vitest/coverage-c8.
• mocker: Don't restore mock to the original if the module is automocked  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/3518 (c1004)
  • spy.mockRestore on auto-mocked named exports will no longer restore their implementation to the actual function. This behavior better matches what Jest does.

   🚀 Features

• Support ssr optimizer  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/3490 (89842)
• Image type add apng  -  by @​btea in https://github.com/vitest-dev/vitest/issues/3498 (a53c2)
• expect: Support expect.soft  -  by @​Dunqing in https://github.com/vitest-dev/vitest/issues/3507 (7c687)
• runner: Support using function/class as describe/test name  -  by @​fenghan34 in https://github.com/vitest-dev/vitest/issues/3497 (15253)

   🐞 Bug Fixes

• The cli option is passed to coverage.exclude  -  by @​btea in https://github.com/vitest-dev/vitest/issues/3506 (c37cd)
• optimizer: Always respect optimizeDeps even if include/exclude is overridden  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/3488 (eb285)
• runner: Ensure Vitest is deduped  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/3489 (2deb7)
• ui: Don't cache coverage assets  -  by @​userquin in https://github.com/vitest-dev/vitest/issues/3508 (952b5)
• vite-node: Circular import stuck  -  by @​Dunqing in https://github.com/vitest-dev/vitest/issues/3480 (50f07)
• watch: Junit reporter fails to re-generate report  -  by @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/3496 (5b73c)

    View changes on GitHub

---

Configuration

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

🚦 Automerge: Enabled.

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

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

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

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate]

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.

---

• Branch has one or more failed status checks

[changeset-bot]

⚠️ No Changeset found

Latest commit: fa11db9

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

💥 An error occurred when fetching the changed packages and changesets in this PR

Some errors occurred when validating the changesets config:
The package or glob expression "@react-docgen-internal/benchmark" is specified in the `ignore` option but it is not found in the project. You may have misspelled the package name or provided an invalid glob expression. Note that glob expressions must be defined according to https://www.npmjs.com/package/micromatch.

[netlify]

✅ Deploy Preview for react-docgen ready!

Name	Link
🔨 Latest commit	fa11db9
🔍 Latest deploy log	https://app.netlify.com/sites/react-docgen/deploys/64807ec917ce5e0008c0716f
😎 Deploy Preview	https://deploy-preview-803--react-docgen.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[renovate]

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.