support reporter options

[hi-ogawa]

Clear and concise description of the problem

Spinned off from #5007 (comment)

To allow customizing reporter in a general manner (and also as Jest compatibility), Vitest should support reporter options.

Suggested solution

I think it's possible to support the same thing as Jest:

• https://jestjs.io/docs/configuration#reporters-arraymodulename--modulename-options
  • reporters: [ ["name", { ...option }], ... ]
• https://jestjs.io/docs/configuration#custom-reporters
  • option is passed via constructor

Currently Vitest doesn't assume anything about constructor arguments, so probably introducing this feature is not a breaking change:

vitest/packages/vitest/src/node/reporters/utils.ts

Lines 30 to 37 in cfd0611

	else if (referenceOrInstance in ReportersMap) {
	const BuiltinReporter = ReportersMap[referenceOrInstance as BuiltinReporters]
	return new BuiltinReporter()
	}
	else {
	const CustomReporter = await loadCustomReporterModule(referenceOrInstance, runner)
	return new CustomReporter()
	}

Alternative

Currently minor customization can be provided by environment variable

• feat: support config junit reporter className with env #3808

Or by using custom field in test config:

• https://github.com/AriPerkkio/vitest-sonar-reporter/tree/main?tab=readme-ov-file#silent

Additional context

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

[AriPerkkio]

@hi-ogawa did you start any work on this? I think I could work on this next. I have got some feature requests related to this on my custom reporter:

• adding ability to change reported root dir file path AriPerkkio/vitest-sonar-reporter#153
• Option to silence output AriPerkkio/vitest-sonar-reporter#62

[hi-ogawa]

@AriPerkkio No, I haven't made any code yet. Fell free to take it. Thanks!