@systemfsoftware/stryker-js 10.2.0 → 12.0.0

package/CHANGELOG.md

@@ -1,5 +1,32 @@
 # @systemfsoftware/stryker-js
 
+## 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.
+
+## 11.0.0
+
+### Patch Changes
+
+- A mutation run no longer stalls forever when a checker or test-runner worker stops answering its connection. Previously a request that was in flight when the worker's connection dropped kept waiting on the dead connection, freezing progress until the CI timeout killed the run. Such a request now fails with a typed connection error when its connection drops, and the worker is restarted per the existing crash policy. Only requests already sent on the dropped connection fail: the client still reconnects on its own, and requests made while it reconnects, including the first request to a worker that is still booting, wait for the connection instead of failing.
+
 ## 10.2.0
 
 ### Minor Changes

package/README.md

@@ -2,7 +2,7 @@
 
 The modern mutation testing framework for JavaScript and TypeScript.
 A ground-up, breaking-change fork of `@stryker-mutator/core` built with Effect 4:
-provides the `stryker` executable, in-memory V8 and isolated Vitest runners,
+provides the `stryker` executable, in-process `vm` and isolated Vitest runners,
 and the typed `./config` authoring surface.
 
 ## Install
@@ -30,8 +30,8 @@ export default defineConfig({
   testRunner: 'vitest',
   checkers: ['typescript'],
   plugins: [
-    import.meta.resolve('@systemfsoftware/stryker-js-vitest-runner'),
-    import.meta.resolve('@systemfsoftware/stryker-js-typescript-checker'),
+    '@systemfsoftware/stryker-js-vitest-runner',
+    '@systemfsoftware/stryker-js-typescript-checker',
   ],
   mutate: [
     'src/**/*.ts',
@@ -54,6 +54,11 @@ pnpm exec stryker run
 
 ## Zero-Plugin Built-in Runners
 
+The `vm` runner is the default: with no `testRunner` and no `testFiles`
+configured, it discovers `*.test` / `*.spec` files itself and runs them. It loads
+your suites through your project's `vitest`, so `vitest` must be installed.
+Set `testFiles` explicitly, or pick one of the runners below, to take control.
+
 ### 1. Shell Command Runner (`testRunner: 'command'`)
 
 Execute any test suite without extra plugins:
@@ -70,9 +75,9 @@ export default defineConfig({
 })
 ```
 
-### 2. In-Memory V8 VM Runner (`testRunner: 'vm'`)
+### 2. In-Process `vm` Runner (`testRunner: 'vm'`)
 
-Run pure unit tests directly inside Node's native V8 VM with zero process spawning overhead:
+Runs Vitest suites in-process, in one worker thread per test runner, loading each test file as native ESM through Node's module hooks. No child process and no bundler step. Each file gets its own module state by default; your `vitest.config.*` (environment, setup files, globals, projects) is picked up through your project's `vitest` install. Vitest browser-mode suites are refused with an error naming `testRunner: 'vitest'`; pick the `vitest` runner for those.
 
 ```ts
 import { defineConfig } from '@systemfsoftware/stryker-js/config'
@@ -86,10 +91,10 @@ export default defineConfig({
 
 ## Configuration API (`@systemfsoftware/stryker-js/config`)
 
-The `./config` subpath exports lightweight, inert TypeScript configuration helpers:
+The `./config` subpath exports the typed configuration authoring surface, including the `StrykerConfig` type naming the partial options a config file writes: a config annotated `const config: StrykerConfig = defineConfig({ ... })` typechecks and loads.
 
 ```ts
-import { defineConfig, mergeConfig } from '@systemfsoftware/stryker-js/config'
+import { defineConfig, type StrykerConfig } from '@systemfsoftware/stryker-js/config'
 ```
 
 ### `defineConfig(options | configFactory)`
@@ -99,7 +104,7 @@ Identity function providing strict autocompletion and type checking without runt
 ```ts
 export default defineConfig(({ isCi, command }) => ({
   testRunner: 'vitest',
-  plugins: [import.meta.resolve('@systemfsoftware/stryker-js-vitest-runner')],
+  plugins: ['@systemfsoftware/stryker-js-vitest-runner'],
   mutate: ['src/**/*.ts', '!src/**/*.test.ts'],
   concurrency: isCi ? 2 : 4,
 }))
@@ -147,12 +152,15 @@ pnpm exec stryker merge-reports --output reports/mutation/mutation.json "reports
 
 ```ts
 import { NodeRuntime } from '@effect/platform-node'
-import { strykerCell } from '@systemfsoftware/stryker-js'
-
-NodeRuntime.runMain(strykerCell({
-  mutate: ['src/**/*.ts'],
-  testRunner: 'command',
-}))
+import { Engine } from '@systemfsoftware/stryker-js'
+import * as Effect from 'effect/Effect'
+
+NodeRuntime.runMain(
+  Engine.strykerCell({
+    mutate: ['src/**/*.ts'],
+    testRunner: 'command',
+  }).pipe(Effect.provide(Engine.nodePlatformLayer)),
+)
 ```
 
 ### Vanilla Promise Interface (`./promises`)
@@ -172,11 +180,11 @@ console.log(`Mutation score: ${verdict.score}%`)
 
 ## Published Subpaths
 
-| Subpath      | Description                                                        |
-| ------------ | ------------------------------------------------------------------ |
-| `.`          | Main entry point: `strykerCell`, runtime layers, and error schemas |
-| `./config`   | `defineConfig`, `mergeConfig`, and `StrykerConfig` typing          |
-| `./promises` | `run()` wrapper returning standard JavaScript promises             |
+| Subpath      | Description                                                               |
+| ------------ | ------------------------------------------------------------------------- |
+| `.`          | Main entry point: `strykerCell`, runtime layers, and error schemas        |
+| `./config`   | Config authoring surface (`defineConfig`, `mergeConfig`, `StrykerConfig`) |
+| `./promises` | `run()` wrapper returning standard JavaScript promises                    |
 
 ## License