supercov 4.18.0 → 4.19.0

package/docs/supported-suites.md

@@ -249,6 +249,7 @@ Cloudflare's own runtime -- measure the Worker too:
 
 ```sh
 npx supercov -- cargo test
+npx supercov -- cargo nextest run
 ```
 
 The Worker crate is instrumented with the rest of the workspace, and `wrangler
@@ -259,7 +260,16 @@ the test's own arguments, process and signals. What the Worker ran is
 credited to the test that started it, exactly, as its own coverage. The
 Worker crate counts though `cargo test` never compiles it, once a test has
 run it. This needs a `wrangler` on `PATH` when the run starts; without one,
-nothing is put in front of it.
+nothing is put in front of it. A run whose tests start no Worker still compiles the crate under
+`cargo test --workspace`; its files then say they are a Rust Worker no test
+started, in `gaps` and the file view, rather than reading as code the tests
+missed.
+
+`wrangler dev --remote` runs the Worker on Cloudflare's edge, and wrangler
+opens no inspector into it there, so nothing can read what it ran. A test
+that starts it that way runs as usual; the Worker's files then say they ran
+remotely and could not be read. Start the Worker with `wrangler dev` to
+measure it.
 
 The Worker built with probes stays in the copy: its `build/` output is never
 returned to the project, and neither is the copy's configuration, which
@@ -286,8 +296,25 @@ npx supercov -- cargo test --target wasm32-wasip1
   file there as it runs.
 
 Each test is credited exactly, assertions included, as for a native test.
-Tests that run in a browser through `wasm-bindgen-test-runner`'s headless
-mode are not covered yet.
+
+`wasm-pack test` works the same way. Supercov runs wasm-pack once to learn
+the `cargo test` it would run (the runner, the browser driver), then runs
+that command test by test:
+
+```sh
+npx supercov -- wasm-pack test --node
+npx supercov -- wasm-pack test --headless --chrome
+```
+
+- In headless Chrome, Supercov stands between the runner and `chromedriver`,
+  and reads what each test's module ran from the page before the runner
+  closes it.
+- Tests run in Firefox, Safari or Edge are run and reported, but not
+  measured yet; the run says so.
+- `wasm-pack test` is measured on Linux and macOS. On Windows, run the
+  `cargo test --target wasm32-unknown-unknown` it runs.
+- Deno is not supported. `wasm-bindgen-test-runner`'s Deno mode
+  (`WASM_BINDGEN_USE_DENO=1`) does not run on Deno 2.
 
 ## Python
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "supercov",
-  "version": "4.18.0",
+  "version": "4.19.0",
   "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.18.0",
-    "@supercov/cli-darwin-x64": "4.18.0",
-    "@supercov/cli-linux-arm64-gnu": "4.18.0",
-    "@supercov/cli-linux-arm64-musl": "4.18.0",
-    "@supercov/cli-linux-x64-gnu": "4.18.0",
-    "@supercov/cli-linux-x64-musl": "4.18.0",
-    "@supercov/cli-win32-arm64": "4.18.0",
-    "@supercov/cli-win32-x64": "4.18.0"
+    "@supercov/cli-darwin-arm64": "4.19.0",
+    "@supercov/cli-darwin-x64": "4.19.0",
+    "@supercov/cli-linux-arm64-gnu": "4.19.0",
+    "@supercov/cli-linux-arm64-musl": "4.19.0",
+    "@supercov/cli-linux-x64-gnu": "4.19.0",
+    "@supercov/cli-linux-x64-musl": "4.19.0",
+    "@supercov/cli-win32-arm64": "4.19.0",
+    "@supercov/cli-win32-x64": "4.19.0"
   },
   "peerDependencies": {
     "@playwright/test": ">=1.55.0",