@systemfsoftware/stryker-js-vitest-runner 1.0.0 → 2.0.1

package/CHANGELOG.md

@@ -1,5 +1,60 @@
 # @systemfsoftware/stryker-js-vitest-runner
 
+## 2.0.1
+
+### Patch Changes
+
+- Peer Effect requirement advances to 4.0.0-rc.112. No API changes.
+
+## 2.0.0
+
+### Major Changes
+
+- Three packages are renamed. `plugin-api` is now `@systemfsoftware/stryker-js`, the
+  language every plugin is written against. `mutation-run` is now
+  `@systemfsoftware/stryker-js-platform-node`, the Node host that runs a mutation
+  test. `mutation-report` is now `@systemfsoftware/stryker-js-html-reporter`.
+  Install the new names and change your imports.
+
+  Options types moved. `StrykerOptions`, `PartialStrykerOptions` and `LogLevel` are
+  imported from the `Schema` export; `Mutant`, `MutantStatus`, `Position` and
+  `Location` from the `Mutant` export. Point a config's `extends` at the language
+  package's `Schema` export.
+
+  `MutantStatus` accepts one spelling per outcome: `Killed`, `Survived`,
+  `NoCoverage`, `Timeout`, `CompileError`, `RuntimeError`, `Ignored` and `Pending`.
+  The lowercase and abbreviated forms — `killed`, `timedOut`, `noCoverage` and the
+  rest — are gone. A comparison against a removed spelling never matched the value
+  the reporter actually produced, so check any status comparison you wrote.
+
+  Statuses, plugin kinds, exit classes and AST formats are string literal unions
+  rather than enums, so read them as their string values. Member access such as
+  `ExitClass.VerdictFail` no longer resolves.
+
+  A plugin no longer receives a logger, and the logger port is gone. Plugins log
+  through Effect, and the host decides where that output goes.
+
+  The bundled base preset is gone. A config inherits from the language package's
+  `Schema` export and states the thresholds, reporters and plugins it wants; you no
+  longer silently inherit a package manager, a plugin list or a break threshold.
+
+### Minor Changes
+
+- Machine-readable mutation progress is a newline-delimited JSON file next to the HTML and JSON reports, not the console.
+
+  The console prints bounded progress prose: phase names, a count line, at most twenty surviving mutants, and a verdict. Killed mutants now advance that count. Child test runs during mutation no longer print per-test output or GitHub workflow commands.
+
+  If you parsed the console as JSON lines, read the stream file instead. A hard kill can leave that file without a closing verdict line.
+
+### Patch Changes
+
+- A mutation run writes the JSON report the `json` reporter is configured to produce.
+
+  Vitest no longer reprints its full summary for every mutant.
+
+- Updated dependencies:
+  - @systemfsoftware/effect-cell-types@5.0.0
+
 ## 1.0.0
 
 ### Major Changes

package/dist/index.d.mts

@@ -1,4 +1,3 @@
-import { PluginKind } from "@systemfsoftware/stryker-js-plugin-api/plugin";
 //#region src/index.d.ts
 /**
  * The `vitest` test runner, as the plugin the engine loads.
@@ -7,7 +6,7 @@ import { PluginKind } from "@systemfsoftware/stryker-js-plugin-api/plugin";
  * in, so the requirement is visible in the type and an engine that does not
  * provide it fails to compile.
  */
-declare const strykerPlugins: import("@systemfsoftware/stryker-js-plugin-api/plugin").PluginContribution<PluginKind.TestRunner>[];
+declare const strykerPlugins: import("@systemfsoftware/stryker-js/Plugin").PluginContribution<"TestRunner">[];
 /**
  * The `vitest` option section as a JSON Schema document, for Stryker's option
  * validation — derived from the declaration, never read from a file. It is built