Description

• Closes support reporter options #5042
• Tested custom reporter with options: feat: add support for rewriting <file path="..."> attributes AriPerkkio/vitest-sonar-reporter#154

There are now multiple different ways how to define reporters in configuration. This is similar shape as coverage.reporters has.

// A single reporter by name
{ reporters: "junit" },

// Inline reporter
{ reporters: { onFinished() { method(); } } },

// A single reporter with options - new option style 
{ reporters: [["junit", { classname: "some-junit-thing", outputFile: "report.xml" }]] },

// Multiple reporters - can combine any of the above
{ 
  reporters: [
    "verbose",
    ["json"],
    ["junit", { classname: "some-junit-thing" } ],
    { onFinished() { method(); } },
    "vitest-github-actions-reporter", // Third party reporter by package name
    "/path/to/local/reporter.js", // Local reporter by path
    ["vitest-sonar-reporter", { silent: true }], // Third party reporter by with options
  ]
},

• junit reporter's process.env.VITEST_JUNIT_CLASSNAME and process.env.VITEST_JUNIT_SUITE_NAME can now be passed via reporter options: ["junit", { classname: "..." suiteName: "..." }]. In 2.0.0 we should drop support for the environment variables.
• test.outputFile can now be passed as reporter option, e.g. ["json", { outputFile: "report.json" }]. I think in 2.0.0 we should drop support for test.outputFile completely.

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:.