0.29.8 seems to have broken C8 unit test coverage reporting

[USA-RedDragon]

Describe the bug

After upgrading to vitest 0.29.8, my workflows utilizing C8 as a coverage provide have started erroring with

$ vitest run --coverage

vite:istanbul> Sourcemaps was automatically enabled for code coverage to be accurate.
 To hide this message set build.sourcemap to true, 'inline' or 'hidden'.
TypeError: coverageModule.getProvider is not a function
    at getCoverageProvider (file:///home/user/project/node_modules/vitest/dist/chunk-integrations-coverage.e0a6acd2.js:26:27)
    at async Vitest.initCoverageProvider (file:///home/user/project/node_modules/vitest/dist/chunk-node-pkg.4e9b4238.js:11669:29)
    at async Vitest.start (file:///home/user/project/node_modules/vitest/dist/chunk-node-pkg.4e9b4238.js:11753:7)
    at async startVitest (file:///home/user/project/node_modules/vitest/dist/chunk-node-pkg.4e9b4238.js:19004:5)
    at async start (file:///home/user/project/node_modules/vitest/dist/cli.js:104:17)
    at async CAC.run (file:///home/user/project/node_modules/vitest/dist/cli.js:77:3)

I noticed this change was added, and it seems related: #3040

Reproduction

https://github.com/USA-RedDragon/vite-bug-repro-c8-coverage is pulled and stripped from a bigger project which had been previously set up with coverage via this guide: https://vitest.dev/guide/coverage.html

To reproduce with that repo:

npm ci # the package-lock.json is present and appropriate
npm run test:unit # equivalent to npx vitest run --coverage

System Info

Binaries:
  Node: 16.14.0 - ~/.nvm/versions/node/v16.14.0/bin/node
  Yarn: 1.22.19 - ~/.nvm/versions/node/v16.14.0/bin/yarn
  npm: 8.3.1 - ~/.nvm/versions/node/v16.14.0/bin/npm
Browsers:
  Chromium: 111.0.5563.146
  Firefox: 111.0.1
npmPackages:
  @vitejs/plugin-vue: ^4.1.0 => 4.1.0
  @vitest/coverage-c8: ^0.29.8 => 0.29.8
  @vitest/ui: ^0.29.8 => 0.29.8
  vite: ^4.2.1 => 4.2.1

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.

[TiagoDiass]

I am facing the same problem here.
Just installed @vitest/coverage-c8 in order to get coverage of my files but when I run vitest run --coverage it throws the same error as described in the issue.

[AriPerkkio]

After upgrading to vitest 0.29.8

The reproduction case is not using vitest@0.29.8. Try updating your vitest to latest version. https://github.com/USA-RedDragon/vite-bug-repro-c8-coverage/blob/main/package-lock.json#L3803-L3804

[dteoh]

I also reported this issue in the local-pkg repo: antfu/local-pkg#7

[USA-RedDragon]

@AriPerkkio was right. Since I didn't have vitest explicitly in my package.json, only @vitest/coverage-c8 and @vitest/ui one of my dependencies was resolving vitest 0.29.1. After explicitly installing vitest at 0.29.8, it started working.