chore(deps): update dependency vitest to ^0.32.2

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
vitest	^0.31.4 -> ^0.32.2

---

Release Notes

vitest-dev/vitest

v0.32.2

Compare Source

   🐞 Bug Fixes

• browser: Don't fail on importing diff-sequences  -  by @​sheremet-va (00b0e)

    View changes on GitHub

v0.32.1

Compare Source

   🚀 Features

• Export registerConsoleShortcuts from vitest/node  -  by @​deot in https://github.com/vitest-dev/vitest/issues/3563 (bc49b)
• expect: Support expect.unreachable  -  by @​fenghan34 and @​sheremet-va in https://github.com/vitest-dev/vitest/issues/3556 (8e385)
• runner: describe/test name support anonymous function  -  by @​btea in https://github.com/vitest-dev/vitest/issues/3562 (3d436)

   🐞 Bug Fixes

• Avoid call stack recursion with large error (fix: #​3060)  -  by @​nathanmmiller and @​sheremet-va in https://github.com/vitest-dev/vitest/issues/3078 and https://github.com/vitest-dev/vitest/issues/3060 (02196)
• Automatically remove define related configuration  -  by @​btea in https://github.com/vitest-dev/vitest/issues/3552 (368b8)
• Import performance from perf_hooks  -  by @​Max10240 and wangbaolong.wbl in https://github.com/vitest-dev/vitest/issues/3578 and https://github.com/vitest-dev/vitest/issues/3579 (24ec8)
• Revert concordance diff, use jest's diff output  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/3582 (9c7ea)
• Typo in config suggestion  -  by @​Krisell in https://github.com/vitest-dev/vitest/issues/3583 (68985)
• browser:
  • Change optimized deps to use vitest  -  by @​userquin in https://github.com/vitest-dev/vitest/issues/3580 (b4ac8)
  • Access vi_inject only if it was injected  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/3587 (d9e14)
• mocker:
  • Respect namespace import when hoisting vi.mock  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/3547 (158c4)
• ui:
  • Navigate to dashboard when re-running tests from coverage page  -  by @​userquin in https://github.com/vitest-dev/vitest/issues/3529 (bc283)
• vite-node:
  • Correctly resolve virtual modules  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/3544 (0cbb0)
  • Fix errors caused by commonjs export circular references  -  by @​rxliuli in https://github.com/vitest-dev/vitest/issues/3570 (b097c)

    View changes on GitHub

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 this update 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.