@systemfsoftware/stryker-test-contribution@v3.0.3: chore(release): version packages (#69)

3.0.3

Patch Changes

• Effect moves to 4.0.0-rc.116 (with @effect/platform-node, @effect/platform-node-shared, @effect/vitest and @effect/opentelemetry on the same release), the @systemfsoftware/* toolchain pins move to their current releases, and vitest 5 with oxc-parser 0.150 come along. Both worker bundles (stryker-js-typescript-checker, stryker-js-vitest-runner) now inline their whole runtime rather than resolving effect, @effect/* and the sibling packages from the host's tree, so a worker runs on its own copy of the effect that built it; the project's typescript and vitest remain the only imports beside Node builtins. The filter-level arbitrary.candidate generators that the thresholds schemas carried are gone: v4 no longer reads them, so thresholds still reject a low above high and the property tests generate the pair from the schema again. Log calls inside Effect.catch* handlers moved to Effect.tapError/Effect.tapCause at the same level and message. @systemfsoftware/stryker-ignorer-interface re-exports the 0.150 AST, where FormalParameterRest.decorators is now Array<Decorator>.

@systemfsoftware/stryker-test-contribution@v3.0.2: chore(release): version packages (#51)

3.0.2

Patch Changes

• Updated dependencies:
  • @systemfsoftware/stryker-js-plugin-interface@7.0.0

@systemfsoftware/stryker-js@v9.0.0: chore(release): version packages (#62)

9.0.0

Major Changes

• The incremental file now carries incrementalVersion (the Stryker package version). Stryker writes it on every incremental run and discards an incremental file it cannot parse or whose incrementalVersion differs from the running version, falling back to a full mutation testing run instead of failing. IncrementalReportSchema requires incrementalVersion, and decodeIncrementalReport and IncrementalReportError are no longer exported.

@systemfsoftware/stryker-js@v8.0.0: chore(release): version packages (#51)

8.0.0

Major Changes

• The checker request carries a plain data record, not the instrumenter's Mutant class. CheckerRequest.mutants and CheckerService.check/group now speak CheckerMutantWire - id, fileName, mutatorName, replacement, and location. A mutant that cannot be described to a checker is skipped instead of reaching it.

  With OTEL_ENABLED=true the CLI now exports its OpenTelemetry metrics to OTEL_EXPORTER_OTLP_ENDPOINT, and OTEL_METRIC_EXPORT_INTERVAL sets the export interval in milliseconds. Checker timings, mutant counts, and worker crashes now reach a metrics backend.

  ConfigEnv and resolveExtends are no longer exported. Import ConfigEnv from the config entry point of the package, and read merged options with loadConfigCell or readConfig from the package root - either performs the extends walk, validation and merge in order.

@systemfsoftware/stryker-js@v10.0.1: chore(release): version packages (#69)

10.0.1

Patch Changes

• Effect moves to 4.0.0-rc.116 (with @effect/platform-node, @effect/platform-node-shared, @effect/vitest and @effect/opentelemetry on the same release), the @systemfsoftware/* toolchain pins move to their current releases, and vitest 5 with oxc-parser 0.150 come along. Both worker bundles (stryker-js-typescript-checker, stryker-js-vitest-runner) now inline their whole runtime rather than resolving effect, @effect/* and the sibling packages from the host's tree, so a worker runs on its own copy of the effect that built it; the project's typescript and vitest remain the only imports beside Node builtins. The filter-level arbitrary.candidate generators that the thresholds schemas carried are gone: v4 no longer reads them, so thresholds still reject a low above high and the property tests generate the pair from the schema again. Log calls inside Effect.catch* handlers moved to Effect.tapError/Effect.tapCause at the same level and message. @systemfsoftware/stryker-ignorer-interface re-exports the 0.150 AST, where FormalParameterRest.decorators is now Array<Decorator>.

@systemfsoftware/stryker-js@v10.0.0: chore(release): version packages (#64)

10.0.0

Major Changes

• The machine-mode event stream now tags every event document with _tag (previously kind), matching the RunEvent schema tags. The wire line schema RunEventWireLine is exported, so consumers can decode machine-mode stdout lines with the same schema the CLI encodes them with. The event stream's composition surface is now public: makeRunEventStream, RunEventStream, RunEventDrain, RunEventDrainLive, and ResolvedModeInput.

  Consumers parsing machine-mode stdout must read the _tag field instead of kind.

Patch Changes

• A checker that fails now fails mutation testing with that checker's cause, instead of crashing with an empty error. The TypeScript checker type-checks each mutant, so compile errors appear in the report. Verdict counts are non-negative integers; Metrics is a class you can build from mutant statuses; a threshold low may not exceed high.

@systemfsoftware/stryker-js-vitest-runner@v7.0.1: chore(release): version packages (#69)

7.0.1

Patch Changes

• Effect moves to 4.0.0-rc.116 (with @effect/platform-node, @effect/platform-node-shared, @effect/vitest and @effect/opentelemetry on the same release), the @systemfsoftware/* toolchain pins move to their current releases, and vitest 5 with oxc-parser 0.150 come along. Both worker bundles (stryker-js-typescript-checker, stryker-js-vitest-runner) now inline their whole runtime rather than resolving effect, @effect/* and the sibling packages from the host's tree, so a worker runs on its own copy of the effect that built it; the project's typescript and vitest remain the only imports beside Node builtins. The filter-level arbitrary.candidate generators that the thresholds schemas carried are gone: v4 no longer reads them, so thresholds still reject a low above high and the property tests generate the pair from the schema again. Log calls inside Effect.catch* handlers moved to Effect.tapError/Effect.tapCause at the same level and message. @systemfsoftware/stryker-ignorer-interface re-exports the 0.150 AST, where FormalParameterRest.decorators is now Array<Decorator>.

@systemfsoftware/stryker-js-typescript-checker@v7.0.4: chore(release): version packages (#69)

7.0.4

Patch Changes

• Effect moves to 4.0.0-rc.116 (with @effect/platform-node, @effect/platform-node-shared, @effect/vitest and @effect/opentelemetry on the same release), the @systemfsoftware/* toolchain pins move to their current releases, and vitest 5 with oxc-parser 0.150 come along. Both worker bundles (stryker-js-typescript-checker, stryker-js-vitest-runner) now inline their whole runtime rather than resolving effect, @effect/* and the sibling packages from the host's tree, so a worker runs on its own copy of the effect that built it; the project's typescript and vitest remain the only imports beside Node builtins. The filter-level arbitrary.candidate generators that the thresholds schemas carried are gone: v4 no longer reads them, so thresholds still reject a low above high and the property tests generate the pair from the schema again. Log calls inside Effect.catch* handlers moved to Effect.tapError/Effect.tapCause at the same level and message. @systemfsoftware/stryker-ignorer-interface re-exports the 0.150 AST, where FormalParameterRest.decorators is now Array<Decorator>.

@systemfsoftware/stryker-js-typescript-checker@v7.0.3: chore(release): version packages (#64)

7.0.3

Patch Changes

• A checker that fails now fails mutation testing with that checker's cause, instead of crashing with an empty error. The TypeScript checker type-checks each mutant, so compile errors appear in the report. Verdict counts are non-negative integers; Metrics is a class you can build from mutant statuses; a threshold low may not exceed high.

@systemfsoftware/stryker-js-typescript-checker@v7.0.2: chore(release): version packages (#51)

7.0.2

Patch Changes

• The checker request carries a plain data record, not the instrumenter's Mutant class. CheckerRequest.mutants and CheckerService.check/group now speak CheckerMutantWire - id, fileName, mutatorName, replacement, and location. A mutant that cannot be described to a checker is skipped instead of reaching it.

  With OTEL_ENABLED=true the CLI now exports its OpenTelemetry metrics to OTEL_EXPORTER_OTLP_ENDPOINT, and OTEL_METRIC_EXPORT_INTERVAL sets the export interval in milliseconds. Checker timings, mutant counts, and worker crashes now reach a metrics backend.

  ConfigEnv and resolveExtends are no longer exported. Import ConfigEnv from the config entry point of the package, and read merged options with loadConfigCell or readConfig from the package root - either performs the extends walk, validation and merge in order.

• Updated dependencies:

  • @systemfsoftware/stryker-js-plugin-interface@7.0.0