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

package/CHANGELOG.md

@@ -1,5 +1,59 @@
 # @systemfsoftware/stryker-js-vitest-runner
 
+## 1.0.0
+
+### Major Changes
+
+- effect is now a required peer dependency. Install it alongside these packages. They previously bundled their own copy, which meant two Effect instances in one process and services that could not find each other across the boundary.
+
+### Minor Changes
+
+- The Vitest runner accepts `setupFilePath`, naming the setup file it copies into
+  the sandbox. It defaults to the file shipped beside the runner's own module,
+  which is the right answer for an installed package; supply it only when you are
+  running the runner from sources rather than from an install.
+
+### Patch Changes
+
+- The shared helpers package is gone. Nothing installs it any more, and the
+  handful of helpers worth sharing now live in the plugin contract next to the
+  types they serve:
+
+  - `strykerReportBugUrl`, `normalizeFileName`, `propertyPath`, `errorToString`
+    and `isErrnoException` from `@systemfsoftware/stryker-js-plugin-api/core`
+  - `noopLogger` from `@systemfsoftware/stryker-js-plugin-api/logging`
+  - `testFilesProvided` from `@systemfsoftware/stryker-js-plugin-api/test-runner`
+
+  If you imported any of those, change the specifier. Everything else it exported
+  had no consumer and is removed: use `Predicate.isNotNullish` from Effect in place
+  of `notEmpty`, and `RegExp.escape` in place of `escapeRegExp`.
+
+- These packages no longer install dependencies they never imported, so installing them pulls less into your tree.
+
+  `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.
+
+- 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.
+
+- Updated dependencies:
+  - @systemfsoftware/stryker-js-plugin-api@3.0.0
+
+## 0.1.4
+
+### Patch Changes
+
+- Plugins are discovered under this scope by default. The `plugins` option now
+  defaults to a glob over this scope instead of the original project's, so a
+  configuration that relied on the previous default while installing plugins from
+  the original project must now list those plugins explicitly. Discovery also no
+  longer fails when no matching scope directory is installed: it loads nothing and
+  warns.
+
+  The report's dependency section names the packages of this scope, and the
+  report's home link points at this project.
+
+- Updated dependencies:
+  - @systemfsoftware/stryker-js-util@0.2.0
+
 ## 0.1.3
 
 ### Patch Changes

package/dist/index.d.mts

@@ -1,52 +1,19 @@
-import { Injector, PluginKind, SandboxPluginContext } from "@systemfsoftware/stryker-js-plugin-api/plugin";
-import { INSTRUMENTER_CONSTANTS, StrykerOptions } from "@systemfsoftware/stryker-js-plugin-api/core";
-import { DryRunOptions, DryRunResult, MutantRunOptions, MutantRunResult, TestRunner, TestRunnerCapabilities } from "@systemfsoftware/stryker-js-plugin-api/test-runner";
-import { createVitest } from "vitest/node";
-import { Logger } from "@systemfsoftware/stryker-js-plugin-api/logging";
-//#region src/vitest-wrapper.d.ts
-interface ResolvedVitest {
-  createVitest: typeof createVitest;
-  version: string;
-}
-type VitestResolver = (dir: string) => Promise<ResolvedVitest>;
-//#endregion
-//#region src/vitest-test-runner.d.ts
-type StrykerNamespace = '__stryker__' | '__stryker2__';
-declare class VitestTestRunner implements TestRunner {
-  private readonly log;
-  private globalNamespace;
-  private readonly sandboxDirectory;
-  private readonly resolveVitestFor;
-  static inject: readonly ["options", "logger", 'globalNamespace', "sandboxDirectory"];
-  private ctx?;
-  private readonly options;
-  private localSetupFile?;
-  constructor(options: StrykerOptions, log: Logger, globalNamespace: StrykerNamespace, sandboxDirectory: string, resolveVitestFor?: VitestResolver);
-  capabilities(): TestRunnerCapabilities;
-  init(): Promise<void>;
-  dryRun(options: DryRunOptions): Promise<DryRunResult>;
-  mutantRun(options: MutantRunOptions): Promise<MutantRunResult>;
-  private run;
-  private setEnv;
-  private requireCtx;
-  private resetContext;
-  private readHitCount;
-  private readMutantCoverage;
-  dispose(): Promise<void>;
-}
-declare function createVitestTestRunnerFactory(namespace?: typeof INSTRUMENTER_CONSTANTS.NAMESPACE | '__stryker2__'): {
-  (injector: Injector<SandboxPluginContext>): VitestTestRunner;
-  inject: ['$injector'];
-};
-//#endregion
+import { PluginKind } from "@systemfsoftware/stryker-js-plugin-api/plugin";
 //#region src/index.d.ts
-declare const strykerPlugins: import("@systemfsoftware/stryker-js-plugin-api/plugin").FactoryPlugin<PluginKind.TestRunner, ["$injector"]>[];
+/**
+ * The `vitest` test runner, as the plugin the engine loads.
+ *
+ * The declared layer asks for the run's resolved options and the sandbox it runs
+ * 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>[];
 /**
  * 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
+ * validation — derived from the declaration, never read from a file. It is built
  * here, at the entry that contributes it, because a document is a *use* of a
  * schema and the schema module exports only declarations.
  */
 declare const strykerValidationSchema: Record<string, unknown>;
 //#endregion
-export { VitestTestRunner, createVitestTestRunnerFactory, strykerPlugins, strykerValidationSchema };
+export { strykerPlugins, strykerValidationSchema };