npm / @stryker-mutator/vitest-runner
@stryker-mutator/vitest-runner
What changed in @stryker-mutator/vitest-runner 9 to 10, from its official release notes, upgrade guides and advisories. Sources checked 2026-10-25.
2 breaking2 new APIs and options3 tooling6 fixes and other
See which of these apply to your code, ranked, in your agent:
npx @unstale/cli init@stryker-mutator/vitest-runner 103 changes
Breaking changes 1
Node.js 20 is no longer supported; Node.js 22 or higher is required.
New APIs and options 1
Configure the Vitest pool used to run tests; defaults to threads. The vmForks pool is unsupported by Vitest versions below 1.0.0.
Fixes and other changes 1
Fixes noisy warnings about Vitest options and setup files.
@stryker-mutator/vitest-runner 910 changes
Breaking changes 1
The Vitest runner now supports Vitest v2 or higher.
New APIs and options 1
Adds an option to limit which tests are executed.
Tooling 3
The Vitest runner now supports Vitest fixtures created with test.extend.
Adds support for Vitest 4.
The Vitest runner now supports Vitest 3 browser mode.
Fixes and other changes 5
Fixes mutant hitcount and coverage in the Vitest runner for Vitest 4.1.
Fixes the dual instance problem with Vitest plugins.
Fixes the EBUSY warning on Windows when concurrency is 2 or greater.
Detects suite-level failures when a test is skipped, so those failures are not missed.
The Vitest runner ensures that test failure screenshots are not produced.