Coverage report doesn't report correct paths

[wight554]

Describe the bug

I've got the following preact project structure

src/
  app.tsx
server/
test/
  src/
    app.tsx.test
  server/

For some reason test report always strips src from src folder tests, test report structure:

----------|---------|----------|---------|---------|-------------------
File      | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s 
----------|---------|----------|---------|---------|-------------------
All files                              |   90.53 |      100 |   87.23 |   90.53 |                   
 project                         |     100 |      100 |     100 |     100 |                   
  app.tsx                              |     100 |      100 |     100 |     100 |                                  
 project/server                  |     100 |      100 |     100 |     100 |                   
  constants.ts                         |     100 |      100 |     100 |     100 |                   
----------|---------|----------|---------|---------|-------------------

I've tried manually running c8 with config from https://github.com/vitest-dev/vitest/blob/main/packages/vitest/src/integrations/coverage.ts - it worked fine, src was under src, not in root folder

I've also tried debugging the code in reportCoverage, it's somehow related with source maps, url has correct mapping, while map has stripped src, probably issue inctx.vitenode.fetchCache.entries(), but that's just assumption

Reproduction

https://github.com/wight554/blog-template

System Info

System:
    OS: macOS 12.2
    CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
    Memory: 1.26 GB / 32.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 16.13.2 - ~/.nvm/versions/node/v16.13.2/bin/node
    npm: 8.1.2 - ~/.nvm/versions/node/v16.13.2/bin/npm
    Watchman: 2021.10.04.00 - /usr/local/bin/watchman
  Browsers:
    Chrome: 98.0.4758.80
    Edge: 97.0.1072.76
    Safari: 15.3
  npmPackages:
    vite: ^2.7.2 => 2.7.13 
    vitest: ^0.2.7 => 0.2.7

Used Package Manager

npm

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.