fix: reporter to log version before provider initalizations

[AriPerkkio]

Initialize reporters before coverage and browser providers. This assures that version number banner is printed before unhandled errors are thrown. Version number banner in this context is RUN v0.29.8 /xyz/vitest-example-project text.

There were few reports where users thought they were using the latest [email protected] but based on stack traces they were using older versions. We've seen similar reports couple of months ago.

• This is 0.29.1 0.29.8 seems to have broken C8 unit test coverage reporting #3118 (comment)
• This is 0.26.3 0.29.8 seems to have broken C8 unit test coverage reporting #3118 (comment)
• This is 0.29.7 [email protected] can not genetate the coverage report #3125 (comment)

Checking the version from stack traces can be done by comparing the filename hashes on earlier releases. This is slow. Let's add the version number to be printed before error is thrown.

Before (by manually adding the error in the code):

$ pnpm run test --coverage

> vitest run "--coverage"

TypeError: coverageModule.getProvider is not a function
    at getCoverageProvider (file:///xyz/vitest/packages/vitest/dist/chunk-integrations-coverage.d93ee824.js:26:27)
    at async Vitest.initCoverageProvider (file:///xyz/vitest/packages/vitest/dist/chunk-node-pkg.63daf436.js:13090:29)
    at async Vitest.start (file:///xyz/vitest/packages/vitest/dist/chunk-node-pkg.63daf436.js:13195:7)
    at async startVitest (file:///xyz/vitest/packages/vitest/dist/chunk-node-pkg.63daf436.js:20352:5)
    at async start (file:///xyz/vitest/packages/vitest/dist/cli.js:105:17)
    at async CAC.run (file:///xyz/vitest/packages/vitest/dist/cli.js:78:3)
 ELIFECYCLE  Test failed. See above for more details.

After:

$ pnpm run test --coverage

> vitest run "--coverage"


 RUN  v0.29.8 /xyz/vitest-example-project


⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Unhandled Error ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
TypeError: coverageModule.getProvider is not a function
 ❯ getCoverageProvider ../vitest/packages/vitest/dist/chunk-integrations-coverage.d93ee824.js:26:27
 ❯ Vitest.initCoverageProvider ../vitest/packages/vitest/dist/chunk-node-pkg.007a6962.js:13090:29
 ❯ Vitest.start ../vitest/packages/vitest/dist/chunk-node-pkg.007a6962.js:13195:5
 ❯ startVitest ../vitest/packages/vitest/dist/chunk-node-pkg.007a6962.js:20347:5
 ❯ start ../vitest/packages/vitest/dist/cli.js:105:17
 ❯ CAC.run ../vitest/packages/vitest/dist/cli.js:78:3




 ELIFECYCLE  Test failed. See above for more details.

[sheremet-va]

This is a breaking change because custom reporters don't have access to the coverage reporter in onInit anymore.

[AriPerkkio]

Oh right, I missed that one completely. Another option is to add a version number logging here:

vitest/packages/vitest/src/node/cli-api.ts

Lines 95 to 103 in 5b85635

	try {
	await ctx.start(cliFilters)
	}
	catch (e) {
	process.exitCode = 1
	await ctx.logger.printError(e, true, 'Unhandled Error')
	ctx.logger.error('\n\n')
	return ctx
	}

But then it could be printed twice if the error occurs after reporter("onInit") is called.

I'm not sure if custom test reporters should ever call the ctx.coverageProvider though. They'll still have access to ctx.config.coverage to make decisions based on coverage options. So intentional breaking change here doesn't sound bad either.