supercov 4.17.0 → 4.17.2

package/docs/assertions.md

@@ -133,6 +133,11 @@ never asked; the statement view (`assertions <file>:<line>`) says how many were,
 and names the test files none of whose tests were asked, which is where to look
 before writing a test that may already exist.
 
+A statement at a module's top level in JavaScript, TypeScript or Python runs
+once, when the first test loads the module, and is recorded for that test
+alone. Every test that runs the module's functions relies on it too, so those
+tests count as running it, after the one that loaded it.
+
 An asserted statement is a judgment too: some test was judged to fail if it
 changed, and the pass stops at the first that is. How strong that answer was
 says how far to trust it. Checked by applying each change and running the

package/docs/cli.md

@@ -471,7 +471,7 @@ one as a public artifact.
 | `--title <text>` | Restrict to tests whose name contains this text |
 | `--test-file <path>` | Restrict to tests in this file, or in this directory |
 | `--metric all \| lines \| statements \| functions \| branches \| mcdc` | Choose a metric for `files`, `gaps`, `diff`, or `minimize` |
-| `--limit N`, `--offset N` | Page through a collection |
+| `--limit N`, `--offset N` | Page through a collection; `--limit 0` lists every entry |
 | `--json` | Return the machine-readable form |
 
 Collection output includes a copyable command for the next page.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "supercov",
-  "version": "4.17.0",
+  "version": "4.17.2",
   "description": "Coverage, security and code quality for coding agents",
   "keywords": [
     "coverage",
@@ -119,14 +119,14 @@
     "test:windows-tls": "node scripts/windows-tls-test.mjs"
   },
   "optionalDependencies": {
-    "@supercov/cli-darwin-arm64": "4.17.0",
-    "@supercov/cli-darwin-x64": "4.17.0",
-    "@supercov/cli-linux-arm64-gnu": "4.17.0",
-    "@supercov/cli-linux-arm64-musl": "4.17.0",
-    "@supercov/cli-linux-x64-gnu": "4.17.0",
-    "@supercov/cli-linux-x64-musl": "4.17.0",
-    "@supercov/cli-win32-arm64": "4.17.0",
-    "@supercov/cli-win32-x64": "4.17.0"
+    "@supercov/cli-darwin-arm64": "4.17.2",
+    "@supercov/cli-darwin-x64": "4.17.2",
+    "@supercov/cli-linux-arm64-gnu": "4.17.2",
+    "@supercov/cli-linux-arm64-musl": "4.17.2",
+    "@supercov/cli-linux-x64-gnu": "4.17.2",
+    "@supercov/cli-linux-x64-musl": "4.17.2",
+    "@supercov/cli-win32-arm64": "4.17.2",
+    "@supercov/cli-win32-x64": "4.17.2"
   },
   "peerDependencies": {
     "@playwright/test": ">=1.55.0",

package/runtime/javascript/jest.config.mjs

@@ -4,6 +4,7 @@
 // Jest accepts, or the "jest" key of package.json -- and adds the adapter
 // (jest.cjs) and the reporter (jestReporter.mjs). Nothing of the user's is
 // replaced: their setup files and reporters keep running.
+import { realpathSync } from "node:fs";
 import { createRequire } from "node:module";
 import { dirname, resolve } from "node:path";
 import { fileURLToPath } from "node:url";
@@ -11,12 +12,38 @@ import { fileURLToPath } from "node:url";
 const here = (name) => fileURLToPath(new URL(`./${name}`, import.meta.url));
 const asList = (value) => (value === undefined ? [] : Array.isArray(value) ? value : [value]);
 
+// The jest-config of the Jest that is running, so version and resolution
+// match Jest's. npm may leave it only under jest-cli or @jest/core
+// (node_modules/jest-cli/node_modules/jest-config), where the project root
+// does not see it: from the root, then from the running Jest's own packages.
+function jestConfig() {
+    const fromRoot = createRequire(resolve(process.cwd(), "package.json"));
+    const bases = [fromRoot];
+    try {
+        bases.push(createRequire(realpathSync(process.argv[1])));
+    } catch {}
+    for (const base of [...bases]) {
+        for (const owner of ["jest-cli/package.json", "@jest/core/package.json", "jest/package.json"]) {
+            try {
+                bases.push(createRequire(base.resolve(owner)));
+            } catch {}
+        }
+    }
+    let first;
+    for (const base of bases) {
+        try {
+            return base("jest-config");
+        } catch (error) {
+            first ??= error;
+        }
+    }
+    throw first;
+}
+
 export default async function supercovJestConfig() {
     let config = { rootDir: process.cwd() };
     try {
-        // The project's own jest-config, so version and resolution match Jest's.
-        const projectRequire = createRequire(resolve(process.cwd(), "package.json"));
-        const { readInitialOptions } = projectRequire("jest-config");
+        const { readInitialOptions } = jestConfig();
         const original = process.env["SUPERCOV_ORIGINAL_JEST_CONFIG"] || undefined;
         const read = await readInitialOptions(original, { skipMultipleConfigError: true });
         config = read.config ?? config;