Skip to content

fix: declare the stryker vitest-runner plugin explicitly #552

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
HugoRCD merged 1 commit into from
Aug 10, 2026
Merged

fix: declare the stryker vitest-runner plugin explicitly #552

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions packages/evlog/stryker.config.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,8 @@
"$schema": "./node_modules/@stryker-mutator/core/schema/stryker-schema.json",
"_": "Mutation testing for evlog core. Slow (~minutes) — do not run in default CI; see .github/workflows/mutation.yml for the weekly cron.",
"_mutate_scope": "Only core modules listed in `mutate` are mutated (logger, pipeline, redact, error, catalog, audit, utils, shared/{routes,headers,middleware}). Framework integrations (express, hono, fastify, ...) and adapters (axiom, posthog, ...) are intentionally excluded — Stryker would re-boot each framework's runtime per mutant which is prohibitively expensive, and those modules are already covered by integration tests in test/frameworks/ and test/adapters/.",
"_plugins": "Explicit because the default @stryker-mutator/* discovery globs relative to core's own install dir, which under pnpm's isolated layout never contains the runner.",
"plugins": ["@stryker-mutator/vitest-runner"],
"packageManager": "pnpm",
"testRunner": "vitest",
"vitest": {
Expand Down
Loading