diff --git a/.changeset/changelogs/@systemfsoftware!stryker-js-html-reporter@5.0.1.md b/.changeset/changelogs/@systemfsoftware!stryker-js-html-reporter@5.0.1.md deleted file mode 100644 index 1124b8b3..00000000 --- a/.changeset/changelogs/@systemfsoftware!stryker-js-html-reporter@5.0.1.md +++ /dev/null @@ -1,7 +0,0 @@ -## 5.0.1 - -### Patch Changes - -- The packages now build on the latest `@systemfsoftware/effect-cell-types` 10.2 cell kinds, with no change to their published behavior. - - - `@systemfsoftware/stryker-test-contribution` exports its evaluator as `Judge`, `TestContribution`, and `TestContributionEvaluator`, and now depends on `effect` directly. diff --git a/.changeset/changelogs/@systemfsoftware!stryker-js-html-reporter@5.0.2.md b/.changeset/changelogs/@systemfsoftware!stryker-js-html-reporter@5.0.2.md new file mode 100644 index 00000000..a4a9d74f --- /dev/null +++ b/.changeset/changelogs/@systemfsoftware!stryker-js-html-reporter@5.0.2.md @@ -0,0 +1,6 @@ +## 5.0.2 + +### Patch Changes + +- Updated dependencies: + - @systemfsoftware/stryker-js-plugin-interface@9.0.0 diff --git a/.changeset/changelogs/@systemfsoftware!stryker-js-instrumenter@9.0.1.md b/.changeset/changelogs/@systemfsoftware!stryker-js-instrumenter@9.0.1.md deleted file mode 100644 index d57d355f..00000000 --- a/.changeset/changelogs/@systemfsoftware!stryker-js-instrumenter@9.0.1.md +++ /dev/null @@ -1,7 +0,0 @@ -## 9.0.1 - -### Patch Changes - -- The packages now build on the latest `@systemfsoftware/effect-cell-types` 10.2 cell kinds, with no change to their published behavior. - - - `@systemfsoftware/stryker-test-contribution` exports its evaluator as `Judge`, `TestContribution`, and `TestContributionEvaluator`, and now depends on `effect` directly. diff --git a/.changeset/changelogs/@systemfsoftware!stryker-js-plugin-interface@9.0.0.md b/.changeset/changelogs/@systemfsoftware!stryker-js-plugin-interface@9.0.0.md new file mode 100644 index 00000000..fdef6697 --- /dev/null +++ b/.changeset/changelogs/@systemfsoftware!stryker-js-plugin-interface@9.0.0.md @@ -0,0 +1,18 @@ +## 9.0.0 + +### Major Changes + +- `Report.Metrics#mutationScore` and `Report.Metrics#mutationScoreBasedOnCoveredCode` now return a `Report.MutationScore` instead of a number: `Scored` with a `percentage` between 0 and 100, or `Unscored` when no tested mutant counts toward the score. Previously an empty run produced `NaN`, which compared false against every threshold. + + Code that read the score as a number must match on it: + + ```ts + // before + const failing = metrics.mutationScore < 80 + + // after + const failing = Report.MutationScore.match(metrics.mutationScore, { + Scored: ({ percentage }) => percentage < 80, + Unscored: () => false, + }) + ``` diff --git a/.changeset/changelogs/@systemfsoftware!stryker-js-plugin-runtime@6.0.1.md b/.changeset/changelogs/@systemfsoftware!stryker-js-plugin-runtime@6.0.1.md deleted file mode 100644 index 781bf468..00000000 --- a/.changeset/changelogs/@systemfsoftware!stryker-js-plugin-runtime@6.0.1.md +++ /dev/null @@ -1,7 +0,0 @@ -## 6.0.1 - -### Patch Changes - -- The packages now build on the latest `@systemfsoftware/effect-cell-types` 10.2 cell kinds, with no change to their published behavior. - - - `@systemfsoftware/stryker-test-contribution` exports its evaluator as `Judge`, `TestContribution`, and `TestContributionEvaluator`, and now depends on `effect` directly. diff --git a/.changeset/changelogs/@systemfsoftware!stryker-js-plugin-runtime@6.0.2.md b/.changeset/changelogs/@systemfsoftware!stryker-js-plugin-runtime@6.0.2.md new file mode 100644 index 00000000..7fb31654 --- /dev/null +++ b/.changeset/changelogs/@systemfsoftware!stryker-js-plugin-runtime@6.0.2.md @@ -0,0 +1,6 @@ +## 6.0.2 + +### Patch Changes + +- Updated dependencies: + - @systemfsoftware/stryker-js-plugin-interface@9.0.0 diff --git a/.changeset/changelogs/@systemfsoftware!stryker-js-typescript-checker@7.1.1.md b/.changeset/changelogs/@systemfsoftware!stryker-js-typescript-checker@7.1.1.md deleted file mode 100644 index dd84edf8..00000000 --- a/.changeset/changelogs/@systemfsoftware!stryker-js-typescript-checker@7.1.1.md +++ /dev/null @@ -1,7 +0,0 @@ -## 7.1.1 - -### Patch Changes - -- The packages now build on the latest `@systemfsoftware/effect-cell-types` 10.2 cell kinds, with no change to their published behavior. - - - `@systemfsoftware/stryker-test-contribution` exports its evaluator as `Judge`, `TestContribution`, and `TestContributionEvaluator`, and now depends on `effect` directly. diff --git a/.changeset/changelogs/@systemfsoftware!stryker-js-typescript-checker@7.1.2.md b/.changeset/changelogs/@systemfsoftware!stryker-js-typescript-checker@7.1.2.md new file mode 100644 index 00000000..535600d6 --- /dev/null +++ b/.changeset/changelogs/@systemfsoftware!stryker-js-typescript-checker@7.1.2.md @@ -0,0 +1,10 @@ +## 7.1.2 + +### Patch Changes + +- Mutants are now type-checked incrementally. Checking a mutant costs its own file and the files that import it — through a relative path, a path alias, or a re-export — instead of a full type check of every project the checker opens, so a run whose mutants all live in one file finishes instead of staying at zero completed mutants until the run is killed. + + A mutation that breaks a file which imports the mutated file is still a `CompileError` rather than being handed to the test runner. + +- Updated dependencies: + - @systemfsoftware/stryker-js-plugin-interface@9.0.0 diff --git a/.changeset/changelogs/@systemfsoftware!stryker-js-vitest-runner@7.2.1.md b/.changeset/changelogs/@systemfsoftware!stryker-js-vitest-runner@7.2.1.md deleted file mode 100644 index 8eb3cadc..00000000 --- a/.changeset/changelogs/@systemfsoftware!stryker-js-vitest-runner@7.2.1.md +++ /dev/null @@ -1,7 +0,0 @@ -## 7.2.1 - -### Patch Changes - -- The packages now build on the latest `@systemfsoftware/effect-cell-types` 10.2 cell kinds, with no change to their published behavior. - - - `@systemfsoftware/stryker-test-contribution` exports its evaluator as `Judge`, `TestContribution`, and `TestContributionEvaluator`, and now depends on `effect` directly. diff --git a/.changeset/changelogs/@systemfsoftware!stryker-js-vitest-runner@7.3.0.md b/.changeset/changelogs/@systemfsoftware!stryker-js-vitest-runner@7.3.0.md new file mode 100644 index 00000000..bdd23efb --- /dev/null +++ b/.changeset/changelogs/@systemfsoftware!stryker-js-vitest-runner@7.3.0.md @@ -0,0 +1,19 @@ +## 7.3.0 + +### Minor Changes + +- The test runner accepts a new `pool` option. When it is `threads`, a Vitest config that enables browser mode for any project is refused at startup with a message naming `testRunner: 'vitest'`. + +### Patch Changes + +- A run whose selected files produce no mutants, for example because no loaded framework claims them, now runs every test in the dry run and finishes with an empty report. With `testRunner: 'vm'` or `'vitest'` it used to fail with "No tests were executed", because the dry run only looked for tests related to those files. The dry run now relates tests only to the files that carry mutants. + +- A failed dry run now names every failing test. The runner used to apply the bail setting to the dry run as well, so Vitest stopped at the first failure and the error listed only that test. Mutant runs still stop at the first failing test unless `disableBail` is set. + +- A test file that fails as a whole — a suite that registers no tests, a file that throws while loading, or a `beforeAll`/`afterAll` hook that fails — is now reported as a failing test carrying the file's own message. A mutant that breaks a file this way is reported as Killed instead of Surviving, and a dry run that loads such a file fails naming it. + + Skipped tests that never start are now reported as skipped rather than dropped from the run's results. + + A mutant run whose related files match no test file no longer stops with a test-runner crash; the run continues with no test able to kill the mutant. + +- Mutation runs with `testRunner: 'vm'` finish in about half the time, with the same verdicts. The engine checks mutant groups on every checker process at once, stops the checkers as soon as checking ends, hands their share of `concurrency` to the test runners, and shares a Node compile cache with every worker it starts. The Vitest runner starts the next isolated worker thread while the current test file runs, so each file still gets a fresh thread but no longer waits for one to boot. On a 319-mutant TypeScript project with the TypeScript checker, a run went from 24.9 s to 12.6 s. diff --git a/.changeset/changelogs/@systemfsoftware!stryker-js@12.0.0.md b/.changeset/changelogs/@systemfsoftware!stryker-js@12.0.0.md deleted file mode 100644 index cf6fe1fe..00000000 --- a/.changeset/changelogs/@systemfsoftware!stryker-js@12.0.0.md +++ /dev/null @@ -1,20 +0,0 @@ -## 12.0.0 - -### Major Changes - -- Restore `defineConfig` and `mergeConfig` on `@systemfsoftware/stryker-js/config`. `defineConfig` accepts an options object, a promise of one, or a `(env: ConfigEnv) => …` factory, as in 10.1.1, and `mergeConfig(defaults, overrides)` composes presets again. `StrykerConfig` is again the partial-options type, so `const config: StrykerConfig = defineConfig({ … })` typechecks. Config files written against the 10.1.1 `./config` surface load and typecheck without edits. - - This removes the 11.0.0 `StrykerConfig` class value. If you adopted it: - - - Replace `StrykerConfig.define(…)` with `defineConfig(…)` and `StrykerConfig.merge(…)` with `mergeConfig(…)`, imported from `@systemfsoftware/stryker-js/config`. - - Replace `StrykerConfig.createDefaultOptions()` and `StrykerConfig.defaultOptions` with `Configuration.createDefaultOptions()` and `Configuration.defaultOptions` from the package entry point. - -### Patch Changes - -- A failed dry run now says which tests broke and why. The refusal names every failing test with its failure message in the error output and in the log at the default level, instead of reporting only how many failed. - -- Installing `@systemfsoftware/stryker-js` on its own now works. `effect` was declared an optional peer even though Stryker imports it at runtime. Package managers never install optional peers, so a project without `effect` failed with `Failed to read config` before the run started. `effect` is now a required peer: pnpm and npm install it automatically, and a project that already uses Effect shares its own copy with Stryker. - -- The packages now build on the latest `@systemfsoftware/effect-cell-types` 10.2 cell kinds, with no change to their published behavior. - - - `@systemfsoftware/stryker-test-contribution` exports its evaluator as `Judge`, `TestContribution`, and `TestContributionEvaluator`, and now depends on `effect` directly. diff --git a/.changeset/changelogs/@systemfsoftware!stryker-js@12.1.0.md b/.changeset/changelogs/@systemfsoftware!stryker-js@12.1.0.md new file mode 100644 index 00000000..9cdfda82 --- /dev/null +++ b/.changeset/changelogs/@systemfsoftware!stryker-js@12.1.0.md @@ -0,0 +1,29 @@ +## 12.1.0 + +### Minor Changes + +- A piped `stdout` now gets human output, exactly like a terminal. Machine consumers ask for the NDJSON event stream explicitly, with `--json` or `STRYKER_MODE=machine`; `--format text` names the human format, and passing it together with `--json` is a usage error (exit 2). Under `--json`, `stdout` carries wire records and nothing else, while progress status lines and log output stay on `stderr`. + + Every run also writes those wire records to `reports/mutation-stream.jsonl` in human mode too, so a job that shows a readable log still produces the artifact `stryker merge-reports` rebuilds a shard's report from. + + If a script or CI step read NDJSON from a piped run without requesting it, pass `--json` (or set `STRYKER_MODE=machine`) there. + + Custom `RunEventDrain` implementations must accept a required `toStdout` argument in `drainFramed`; pass-throughs can ignore it. + +### Patch Changes + +- A run whose selected files produce no mutants, for example because no loaded framework claims them, now runs every test in the dry run and finishes with an empty report. With `testRunner: 'vm'` or `'vitest'` it used to fail with "No tests were executed", because the dry run only looked for tests related to those files. The dry run now relates tests only to the files that carry mutants. + +- A run whose `mutate` patterns match no file now finishes successfully instead of stopping with an instrument error. It performs the dry run, writes a mutation report with no files, and passes regardless of `thresholds.break`, the same as upstream StrykerJS. A sharded run whose shard receives no file no longer fails. + + `stryker merge-reports` shows `n/a` for a package whose report has no tested mutant, instead of a score of `0.00`. + + Errors reported for the prepare, dry-run, and mutation-testing stages now carry their reason as the error message, so a printed cause no longer shows up as a bare error name. + +- `stryker merge-reports` now rebuilds a package's partial report from the mutants recorded in its stream part when the run ended before writing its final report. Earlier versions recognized none of the recorded mutants and reported the package as having no report. + +- Mutation runs with `testRunner: 'vm'` finish in about half the time, with the same verdicts. The engine checks mutant groups on every checker process at once, stops the checkers as soon as checking ends, hands their share of `concurrency` to the test runners, and shares a Node compile cache with every worker it starts. The Vitest runner starts the next isolated worker thread while the current test file runs, so each file still gets a fresh thread but no longer waits for one to boot. On a 319-mutant TypeScript project with the TypeScript checker, a run went from 24.9 s to 12.6 s. + +- `testRunner: 'vm'` runs Vitest itself on Vitest's isolated `threads` pool instead of an in-process reimplementation, and stays the default `testRunner`. It reports the same test ids, outcomes and per-mutant verdicts as `testRunner: 'vitest'`, so a project whose Vitest config enables browser mode is refused at startup with a message naming `testRunner: 'vitest'`. + + Stryker no longer discovers test files for `vm`: Vitest selects them from your config, as it does for `testRunner: 'vitest'`. A run that loads no test files fails the dry run naming `testFiles`. diff --git a/.changeset/changelogs/@systemfsoftware!stryker-test-contribution@4.1.0.md b/.changeset/changelogs/@systemfsoftware!stryker-test-contribution@4.1.0.md deleted file mode 100644 index 16b80227..00000000 --- a/.changeset/changelogs/@systemfsoftware!stryker-test-contribution@4.1.0.md +++ /dev/null @@ -1,7 +0,0 @@ -## 4.1.0 - -### Minor Changes - -- The packages now build on the latest `@systemfsoftware/effect-cell-types` 10.2 cell kinds, with no change to their published behavior. - - - `@systemfsoftware/stryker-test-contribution` exports its evaluator as `Judge`, `TestContribution`, and `TestContributionEvaluator`, and now depends on `effect` directly. diff --git a/.changeset/changelogs/@systemfsoftware!stryker-test-contribution@4.1.1.md b/.changeset/changelogs/@systemfsoftware!stryker-test-contribution@4.1.1.md new file mode 100644 index 00000000..7a042232 --- /dev/null +++ b/.changeset/changelogs/@systemfsoftware!stryker-test-contribution@4.1.1.md @@ -0,0 +1,6 @@ +## 4.1.1 + +### Patch Changes + +- Updated dependencies: + - @systemfsoftware/stryker-js-plugin-interface@9.0.0 diff --git a/.changeset/changelogs/@systemfsoftware!stryker-vm-harness@3.0.1.md b/.changeset/changelogs/@systemfsoftware!stryker-vm-harness@3.0.1.md deleted file mode 100644 index 8aa4ef99..00000000 --- a/.changeset/changelogs/@systemfsoftware!stryker-vm-harness@3.0.1.md +++ /dev/null @@ -1,15 +0,0 @@ -## 3.0.1 - -### Patch Changes - -- The packages now build on the latest `@systemfsoftware/effect-cell-types` 10.2 cell kinds, with no change to their published behavior. - - - `@systemfsoftware/stryker-test-contribution` exports its evaluator as `Judge`, `TestContribution`, and `TestContributionEvaluator`, and now depends on `effect` directly. - -- The vm runner now honours Vitest's `passWithNoTests`. A test file that registers no tests no longer fails the dry run when its Vitest project sets `passWithNoTests: true`, and still fails with `No test suite found in file ` when the option is false or unset. The option applies per project, as in Vitest: a root-level `test.passWithNoTests` covers every project, and one project in `test.projects` can opt in while another does not. - -- Projects that install `@systemfsoftware/stryker-js` and `vitest`, but not the vm runner package directly, now complete a `testRunner: 'vm'` dry run under pnpm's default isolated `node_modules` layout, instead of failing with a `Cannot find module` error for the vm runner's own package. The project's own `vitest` is still the one that runs your tests. - -- The vm runner no longer rewrites `import.meta.vitest` text that is not an expression. A string, template literal, comment or regex literal that mentions `import.meta.vitest` now reaches your code unchanged, so suites whose fixtures contain it, such as lint-rule tests, pass on the vm runner as they do under Vitest. In-source `if (import.meta.vitest)` tests still register and run, and `import.meta.vitest` inside a template `${…}` substitution still evaluates to the Vitest API. - -- The vm runner now gives the Vitest API to every module a suite loads that imports `vitest`, not only to files inside the project directory. A Vitest `setupFiles` entry, helper module or workspace package outside the project used to receive a runner-less `vitest` and stop the whole run with "Vitest failed to find the runner"; its `beforeEach` and `it` calls now register against the current test file, as they do under Vitest. Dependencies under `node_modules` stay shared across test files, and `@effect/vitest` and `@systemfsoftware/effect-gherkin-spec` behave as before. diff --git a/.changeset/dry-run-failure-names-tests.md b/.changeset/dry-run-failure-names-tests.md deleted file mode 100644 index 0c71a293..00000000 --- a/.changeset/dry-run-failure-names-tests.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -'@systemfsoftware/stryker-js': patch ---- - -A failed dry run now says which tests broke and why. The refusal names every failing test with its failure message in the error output and in the log at the default level, instead of reporting only how many failed. diff --git a/.changeset/ledger.yaml b/.changeset/ledger.yaml index 70354855..90a83b21 100644 --- a/.changeset/ledger.yaml +++ b/.changeset/ledger.yaml @@ -194,6 +194,10 @@ - plugin-interface-codecs - stryker-js-plugin-interface-bare-package-specifiers - vm-runner-default-zero-config +"@systemfsoftware/stryker-js-plugin-interface@9.0.0": + dir: packages/stryker-js-plugin-interface + intents: + - mutation-score-union "@systemfsoftware/stryker-js-plugin-runtime@5.0.0": dir: packages/stryker-js-plugin-runtime intents: @@ -262,6 +266,10 @@ dir: packages/stryker-js-typescript-checker intents: - systemfsoftware-latest-packages +"@systemfsoftware/stryker-js-typescript-checker@7.1.2": + dir: packages/stryker-js-typescript-checker + intents: + - typescript-checker-checks-affected-files "@systemfsoftware/stryker-js-vitest-runner@5.0.0": dir: packages/stryker-js-vitest-runner intents: @@ -303,6 +311,14 @@ dir: packages/stryker-js-vitest-runner intents: - systemfsoftware-latest-packages +"@systemfsoftware/stryker-js-vitest-runner@7.3.0": + dir: packages/stryker-js-vitest-runner + intents: + - dry-run-without-mutants + - vitest-runner-dry-run-reports-every-failure + - vitest-runner-file-failures + - vitest-runner-pool-option + - vm-runner-mutation-wall-time "@systemfsoftware/stryker-js@10.0.0": dir: packages/stryker-js intents: @@ -356,6 +372,15 @@ - restore-config-authoring-helpers - stryker-js-effect-required-peer - systemfsoftware-latest-packages +"@systemfsoftware/stryker-js@12.1.0": + dir: packages/stryker-js + intents: + - dry-run-without-mutants + - empty-mutate-set-dry-run + - merge-reports-rebuilds-streamed-mutants + - piped-stdout-stays-human + - vm-runner-mutation-wall-time + - vm-runner-runs-vitest "@systemfsoftware/stryker-js@5.0.0": dir: packages/stryker-js intents: diff --git a/.changeset/restore-config-authoring-helpers.md b/.changeset/restore-config-authoring-helpers.md deleted file mode 100644 index 08388605..00000000 --- a/.changeset/restore-config-authoring-helpers.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -'@systemfsoftware/stryker-js': major ---- - -Restore `defineConfig` and `mergeConfig` on `@systemfsoftware/stryker-js/config`. `defineConfig` accepts an options object, a promise of one, or a `(env: ConfigEnv) => …` factory, as in 10.1.1, and `mergeConfig(defaults, overrides)` composes presets again. `StrykerConfig` is again the partial-options type, so `const config: StrykerConfig = defineConfig({ … })` typechecks. Config files written against the 10.1.1 `./config` surface load and typecheck without edits. - -This removes the 11.0.0 `StrykerConfig` class value. If you adopted it: - -- Replace `StrykerConfig.define(…)` with `defineConfig(…)` and `StrykerConfig.merge(…)` with `mergeConfig(…)`, imported from `@systemfsoftware/stryker-js/config`. -- Replace `StrykerConfig.createDefaultOptions()` and `StrykerConfig.defaultOptions` with `Configuration.createDefaultOptions()` and `Configuration.defaultOptions` from the package entry point. diff --git a/.changeset/stryker-js-effect-required-peer.md b/.changeset/stryker-js-effect-required-peer.md deleted file mode 100644 index f3d04a0e..00000000 --- a/.changeset/stryker-js-effect-required-peer.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"@systemfsoftware/stryker-js": patch ---- - -Installing `@systemfsoftware/stryker-js` on its own now works. `effect` was declared an optional peer even though Stryker imports it at runtime. Package managers never install optional peers, so a project without `effect` failed with `Failed to read config` before the run started. `effect` is now a required peer: pnpm and npm install it automatically, and a project that already uses Effect shares its own copy with Stryker. diff --git a/.changeset/systemfsoftware-latest-packages.md b/.changeset/systemfsoftware-latest-packages.md deleted file mode 100644 index ad14427c..00000000 --- a/.changeset/systemfsoftware-latest-packages.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -"@systemfsoftware/stryker-js": patch -"@systemfsoftware/stryker-js-html-reporter": patch -"@systemfsoftware/stryker-js-instrumenter": patch -"@systemfsoftware/stryker-js-plugin-runtime": patch -"@systemfsoftware/stryker-js-typescript-checker": patch -"@systemfsoftware/stryker-js-vitest-runner": patch -"@systemfsoftware/stryker-test-contribution": minor ---- - -The packages now build on the latest `@systemfsoftware/effect-cell-types` 10.2 cell kinds, with no change to their published behavior. - -- `@systemfsoftware/stryker-test-contribution` exports its evaluator as `Judge`, `TestContribution`, and `TestContributionEvaluator`, and now depends on `effect` directly. diff --git a/packages/stryker-js-html-reporter/package.json b/packages/stryker-js-html-reporter/package.json index b6717d34..006f4bf5 100644 --- a/packages/stryker-js-html-reporter/package.json +++ b/packages/stryker-js-html-reporter/package.json @@ -1,6 +1,6 @@ { "name": "@systemfsoftware/stryker-js-html-reporter", - "version": "5.0.1", + "version": "5.0.2", "repository": { "type": "git", "url": "git+https://github.com/systemfsoftware/stryker-js-effect.git", diff --git a/packages/stryker-js-plugin-interface/package.json b/packages/stryker-js-plugin-interface/package.json index 75aa2dba..ad8bfe5a 100644 --- a/packages/stryker-js-plugin-interface/package.json +++ b/packages/stryker-js-plugin-interface/package.json @@ -1,6 +1,6 @@ { "name": "@systemfsoftware/stryker-js-plugin-interface", - "version": "8.0.0", + "version": "9.0.0", "repository": { "type": "git", "url": "git+https://github.com/systemfsoftware/stryker-js-effect.git", diff --git a/packages/stryker-js-plugin-runtime/package.json b/packages/stryker-js-plugin-runtime/package.json index 7017d999..bbf491cb 100644 --- a/packages/stryker-js-plugin-runtime/package.json +++ b/packages/stryker-js-plugin-runtime/package.json @@ -1,6 +1,6 @@ { "name": "@systemfsoftware/stryker-js-plugin-runtime", - "version": "6.0.1", + "version": "6.0.2", "repository": { "type": "git", "url": "git+https://github.com/systemfsoftware/stryker-js-effect.git", diff --git a/packages/stryker-js-typescript-checker/package.json b/packages/stryker-js-typescript-checker/package.json index 13240eaa..144897be 100644 --- a/packages/stryker-js-typescript-checker/package.json +++ b/packages/stryker-js-typescript-checker/package.json @@ -1,6 +1,6 @@ { "name": "@systemfsoftware/stryker-js-typescript-checker", - "version": "7.1.1", + "version": "7.1.2", "repository": { "type": "git", "url": "git+https://github.com/systemfsoftware/stryker-js-effect.git", diff --git a/packages/stryker-js-vitest-runner/package.json b/packages/stryker-js-vitest-runner/package.json index 25339564..dea70148 100644 --- a/packages/stryker-js-vitest-runner/package.json +++ b/packages/stryker-js-vitest-runner/package.json @@ -1,6 +1,6 @@ { "name": "@systemfsoftware/stryker-js-vitest-runner", - "version": "7.2.1", + "version": "7.3.0", "repository": { "type": "git", "url": "git+https://github.com/systemfsoftware/stryker-js-effect.git", diff --git a/packages/stryker-js/package.json b/packages/stryker-js/package.json index c9a85baa..41339795 100644 --- a/packages/stryker-js/package.json +++ b/packages/stryker-js/package.json @@ -1,6 +1,6 @@ { "name": "@systemfsoftware/stryker-js", - "version": "12.0.0", + "version": "12.1.0", "repository": { "type": "git", "url": "git+https://github.com/systemfsoftware/stryker-js-effect.git", diff --git a/packages/stryker-test-contribution/package.json b/packages/stryker-test-contribution/package.json index 751f0d26..8610262e 100644 --- a/packages/stryker-test-contribution/package.json +++ b/packages/stryker-test-contribution/package.json @@ -1,7 +1,7 @@ { "name": "@systemfsoftware/stryker-test-contribution", "license": "Apache-2.0", - "version": "4.1.0", + "version": "4.1.1", "author": "Ryan Lee ", "repository": { "type": "git",