Describe the bug

Using the @vitest/coverage-v8 package with the latest version hangs while mocking a project using nestjs. Output prints JUNIT report written to [path]/coverage/unit/junit.xml and then the process does not exit, with no coverage report being output. This does not occur as of version 1.3.0. I'm guessing that it has something to do with the changes made to decorators in #5206, as Nest makes heavy use of decorators.

Reproduction

Technically this version does resolve after hanging for ~30 seconds, but hopefully that should be enough to highlight the issue.

https://github.com/noahw3/vitest/tree/main/examples/basic

System Info

We also observed this in our CI environment, though it also reproduced locally.

  System:
    OS: macOS 14.1.2
    CPU: (10) arm64 Apple M1 Pro
    Memory: 623.30 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.15.0 - ~/.nvm/versions/node/v18.15.0/bin/node
    Yarn: 1.22.19 - /opt/homebrew/bin/yarn
    npm: 9.5.0 - ~/.nvm/versions/node/v18.15.0/bin/npm
    pnpm: 8.10.0 - /opt/homebrew/bin/pnpm
  Browsers:
    Chrome: 121.0.6167.184
    Safari: 17.1.2
  npmPackages:
    @vitest/coverage-v8: 1.3.1 => 1.3.1 
    vitest: 1.3.1 => 1.3.1

Used Package Manager

pnpm

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.