Bump @vitest/ui from 0.27.1 to 0.32.0

[dependabot]

Bumps @vitest/ui from 0.27.1 to 0.32.0.

Release notes

Sourced from @​vitest/ui's releases.

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)
• expect: Support expect.soft  -  by @​Dunqing in vitest-dev/vitest#3507 (7c687)
• runner: Support using function/class as describe/test name  -  by @​fenghan34 in vitest-dev/vitest#3497 (15253)

   🐞 Bug Fixes

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

    View changes on GitHub

v0.31.4

   🚀 Features

• Enable experimentalOptimizer  -  by @​sheremet-va in vitest-dev/vitest#3413 (5a894)

   🐞 Bug Fixes

• vite-node: Deps.inline doesn't work  -  by @​sheremet-va in vitest-dev/vitest#3485 (be930)

    View changes on GitHub

v0.31.3

   🚀 Features

• Support VITE_NODE_DEPS_MODULE_DIRECTORIES from .npmrc  -  by @​AriPerkkio in vitest-dev/vitest#3471 (393bf)

   🐞 Bug Fixes

• logger: Print unhandled errors before summary  -  by @​sheremet-va in vitest-dev/vitest#3474 (4c9a7)
• runner: Suite options do not propagate to nested suites (fix: #3467)  -  by @​xsjcTony in vitest-dev/vitest#3473 and vitest-dev/vitest#3467 (9fb9d)

... (truncated)

Commits

• 8d3cf9d chore: release v0.32.0
• 952b5be fix(ui): don't cache coverage assets (#3508)
• ab3e085 chore: release v0.31.4
• 29a37cd chore: release v0.31.3
• d65f287 chore: release v0.31.2
• 306b233 fix(vite-node): don't externalize "dist" by default (#3446)
• 39432e8 chore(deps): update dependency @​faker-js/faker to v8 (#3375)
• cd5d58b fix: prevent birpc timeouts when Math.random mock is not restored (#3460)
• 6433224 chore: release v0.31.1
• 6501d2e fix(browser): keep default export when rewriting exports (#3389)
• 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)