chore(deps-dev): bump vitest from 0.31.4 to 0.32.2

[dependabot[bot]]

Bumps vitest from 0.31.4 to 0.32.2.

Release notes

Sourced from vitest's releases.

v0.32.2

   🐞 Bug Fixes

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

    View changes on GitHub

v0.32.1

   🚀 Features

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

   🐞 Bug Fixes

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

    View changes on GitHub

v0.32.0

   🚨 Breaking Changes

• Throw an error, if the module cannot be resolved  -  by @​sheremet-va in vitest-dev/vitest#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 vitest-dev/vitest#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 vitest-dev/vitest#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 vitest-dev/vitest#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 vitest-dev/vitest#3490 (89842)
• Image type add apng  -  by @​btea in vitest-dev/vitest#3498 (a53c2)

... (truncated)

Commits

• 1e8760a chore: release v0.32.2
• 02bed36 chore: release v0.32.1
• 8e385bb feat(expect): support expect.unreachable (#3556)
• 689855b fix: typo in config suggestion (#3583)
• 9c7ea38 fix: revert concordance diff, use jest's diff output (#3582)
• 24ec85a fix: import performance from perf_hooks (fix #3578) (#3579)
• 368b825 fix: automatically remove define related configuration (#3552)
• 02196f9 fix: avoid call stack recursion with large error (fix: #3060) (#3078)
• bc49bac feat: export registerConsoleShortcuts from vitest/node (#3563)
• 158c4bb fix(mocker): respect namespace import when hoisting vi.mock (#3547)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[changeset-bot[bot]]

⚠️ No Changeset found

Latest commit: 4b817932633805c69a661c487e59a6ea68298941

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.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

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

[dependabot[bot]]

Looks like vitest is up-to-date now, so this is no longer needed.