@systemfsoftware/stryker-js-typescript-checker 4.0.0 → 5.0.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,96 @@
1
1
  # @systemfsoftware/stryker-js-typescript-checker
2
2
 
3
+ ## 5.0.1
4
+
5
+ ### Patch Changes
6
+
7
+ - Re-released against @systemfsoftware/stryker-js without the removed --llms manifest. The Run stream no longer carries a manifest terminal event, and the RunEvent / RunTerminalEvent unions no longer include the manifest arm, so any exhaustive consumer of those types must drop that case.
8
+
9
+ - Rebuilds against updated workspace dependencies, including the new
10
+ `@systemfsoftware/stryker-js` reporter protocol major.
11
+
12
+ - Updated dependencies:
13
+ - @systemfsoftware/stryker-js@3.0.0
14
+
15
+ ## 5.0.0
16
+
17
+ ### Major Changes
18
+
19
+ - The packages are renamed. `plugin-api` is now `@systemfsoftware/stryker-js`, the
20
+ language every plugin is written against. `mutation-run` is split: the run
21
+ itself is `@systemfsoftware/stryker-js-engine`
22
+ (host-neutral, no Node on its manifest) and the Node process entries are
23
+ `@systemfsoftware/stryker-js-cli`, which owns the worker files and the runtime
24
+ gate. `mutation-report` is now `@systemfsoftware/stryker-js-html-reporter`.
25
+ `@systemfsoftware/stryker-js-platform-node` is never published — do not install
26
+ it. Install the new names and change your imports.
27
+
28
+ Options types moved. `StrykerOptions`, `PartialStrykerOptions` and `LogLevel` are
29
+ imported from the `Schema` export; `Mutant`, `MutantStatus`, `Position` and
30
+ `Location` from the `Mutant` export. Point a config's `extends` at the language
31
+ package's `Schema` export.
32
+
33
+ `MutantStatus` accepts one spelling per outcome: `Killed`, `Survived`,
34
+ `NoCoverage`, `Timeout`, `CompileError`, `RuntimeError`, `Ignored` and `Pending`.
35
+ The lowercase and abbreviated forms — `killed`, `timedOut`, `noCoverage` and the
36
+ rest — are gone. A comparison against a removed spelling never matched the value
37
+ the reporter actually produced, so check any status comparison you wrote.
38
+
39
+ Statuses, plugin kinds, exit classes and AST formats are string literal unions
40
+ rather than enums, so read them as their string values. Member access such as
41
+ `ExitClass.VerdictFail` no longer resolves.
42
+
43
+ A plugin no longer receives a logger, and the logger port is gone. Plugins log
44
+ through Effect, and the host decides where that output goes.
45
+
46
+ The bundled base preset is gone. A config inherits from the language package's
47
+ `Schema` export and states the thresholds, reporters and plugins it wants; you no
48
+ longer silently inherit a package manager, a plugin list or a break threshold.
49
+
50
+ ### Minor Changes
51
+
52
+ - cut over to effect v4 (4.0.0-rc.108): public surface derives from effect types; peers flip effect ^3→^4
53
+
54
+ ### Patch Changes
55
+
56
+ - New version is published through npm trusted publishing, so it carries a provenance attestation you can verify.
57
+
58
+ - Peer Effect requirement advances to 4.0.0-rc.112. No API changes.
59
+
60
+ - An oversized message between the runner and a worker now fails the run with a
61
+ reason instead of exhausting memory. Each side of the connection reads frames
62
+ up to 16 MiB, which leaves headroom over the largest legitimate payload — a dry
63
+ run carrying per-test coverage — and a frame past the limit fails the calls
64
+ waiting on it rather than growing until the process dies.
65
+
66
+ - Each of these packages now has a README, so its registry page says what the package is, how
67
+ to install it, and what to import or register — previously the page was blank. The lint
68
+ plugins show the configuration line that enables what they recommend.
69
+
70
+ `@systemfsoftware/stryker-js-html-reporter` also carries its licence text
71
+
72
+ - The shared helpers package is gone. Nothing installs it any more, and the
73
+ handful of helpers worth sharing now live in the plugin contract next to the
74
+ types they serve:
75
+
76
+ - `strykerReportBugUrl`, `normalizeFileName`, `propertyPath`, `errorToString`
77
+ and `isErrnoException` from `@systemfsoftware/stryker-js/core`
78
+ - `noopLogger` from `@systemfsoftware/stryker-js/logging`
79
+ - `testFilesProvided` from `@systemfsoftware/stryker-js/test-runner`
80
+
81
+ If you imported any of those, change the specifier. Everything else it exported
82
+ had no consumer and is removed: use `Predicate.isNotNullish` from Effect in place
83
+ of `notEmpty`, and `RegExp.escape` in place of `escapeRegExp`.
84
+
85
+ - These packages no longer install dependencies they never imported, so installing them pulls less into your tree.
86
+
87
+ `tslib` is gone from all six. The mutation runner additionally stops installing `lodash.groupby`, `semver` and `source-map`, and the command line interface stops installing `@effect/platform-node-shared`. Nothing exported changes.
88
+
89
+ - Published packages no longer carry build artifacts left over from earlier builds. One package was shipping about a megabyte of bundled test-runner internals this way.
90
+
91
+ - Updated dependencies:
92
+ - @systemfsoftware/stryker-js@2.0.0
93
+
3
94
  ## 4.0.0
4
95
 
5
96
  ### Major Changes
package/dist/index.d.mts CHANGED
@@ -1,5 +1,5 @@
1
1
  //#region src/index.d.ts
2
- declare const strykerPlugins: import("@systemfsoftware/stryker-js/Plugin").PluginContribution<"Checker">[];
2
+ declare const strykerPlugins: import("@systemfsoftware/stryker-js/Plugin").PluginLayerContribution<"Checker">[];
3
3
  declare const strykerValidationSchema: Record<string, unknown>;
4
4
  //#endregion
5
5
  export { strykerPlugins, strykerValidationSchema };