fix: don't panic when coverage.reporter is a string

[sheremet-va]

Description

Fixes #6260

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

• It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
• Ideally, include a test that fails without this PR but passes with it.
• Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Tests

• Run the tests with pnpm test:ci.

Documentation

• If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

• Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.

[netlify]

✅ Deploy Preview for vitest-dev ready!

Name	Link
🔨 Latest commit	137c5d8
🔍 Latest deploy log	https://app.netlify.com/sites/vitest-dev/deploys/66ac998dfa1ce90008864821
😎 Deploy Preview	https://deploy-preview-6267--vitest-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[AriPerkkio]

Sure, this will fix the crash but htmlReporter resolving parts will cause false results. Both ['html', 'json'] and [['html', { subdir: 'tmp' }], 'json'] will pass the toArray check. Reporter resolving will then break for one of the cases:

vitest/packages/vitest/src/node/config/serializeConfig.ts

Lines 49 to 53 in 081cfe0

	const htmlReporter = coverage.reporter.find(([reporterName]) => reporterName === 'html') as [
	'html',
	{ subdir?: string },
	] | undefined
	const subdir = htmlReporter && htmlReporter[1]?.subdir

I started to do similar fix yesterday (AriPerkkio@b1ad1e5) but realized that this kind of fixes should not be needed in the first place if typings were correct. Reporter config should be normalized when configuration is resolved.

[sheremet-va]

I started to do similar fix yesterday (AriPerkkio@b1ad1e5) but realized that this kind of fixes should not be needed in the first place if typings were correct. Reporter config should be normalized when configuration is resolved.

Ok, I see, I moved resolveReporters to resolveConfig now without removing the call from coverage packages (to not accidentally break someone yet because of the usual package manager shenanigans - maybe with 2.1). I am still planning to refactor the config resolution in the future.

[AriPerkkio]

maybe with 2.1

Sounds good!