supercov 0.0.29 → 0.0.30
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/docs/workspace-isolation.md +12 -1
- package/package.json +7 -7
|
@@ -32,7 +32,9 @@ synced back to the project after the run, so `supercov -- npm test -- -u`
|
|
|
32
32
|
updates snapshots in the repository exactly as `npm test -- -u` would. Two
|
|
33
33
|
exceptions are reported instead of applied: changes the command makes to
|
|
34
34
|
instrumented source files (the instrumented copies must never overwrite your
|
|
35
|
-
sources) and deletions (never propagated automatically).
|
|
35
|
+
sources) and deletions (never propagated automatically). Changes inside any
|
|
36
|
+
`node_modules` directory are neither applied nor reported: dependency trees are
|
|
37
|
+
not command outputs.
|
|
36
38
|
|
|
37
39
|
## Files Supercov creates
|
|
38
40
|
|
|
@@ -88,6 +90,15 @@ When a suite launches a container or VM from a mounted workspace, Supercov uses
|
|
|
88
90
|
the isolated workspace as the source presented to that environment. The runtime
|
|
89
91
|
must be able to cross the launch boundary and return evidence.
|
|
90
92
|
|
|
93
|
+
Dependencies stay out of the instrumented copy. The root `node_modules` is
|
|
94
|
+
linked entry by entry to the project's own, so an environment that mounts the
|
|
95
|
+
workspace must bring its own root dependencies (the supported launchers do).
|
|
96
|
+
Nested `node_modules` inside packages and extensions are materialised as real
|
|
97
|
+
directories: cloned copy-on-write where the filesystem allows it (APFS), and
|
|
98
|
+
hard-linked file by file elsewhere on Unix, so they resolve inside the mount
|
|
99
|
+
either way. Only when neither is possible, such as a dependency tree on another
|
|
100
|
+
volume, are they linked entry by entry like the root.
|
|
101
|
+
|
|
91
102
|
If a remote executor hides the launch or mount boundary, Supercov reports the
|
|
92
103
|
limitation instead of claiming unseen code was measured. See
|
|
93
104
|
[Supported suites](supported-suites.md) for the current boundary.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "supercov",
|
|
3
|
-
"version": "0.0.
|
|
3
|
+
"version": "0.0.30",
|
|
4
4
|
"description": "Zero-edit, runner-aware coverage completeness for JavaScript test suites",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"repository": {
|
|
@@ -68,12 +68,12 @@
|
|
|
68
68
|
"prepublishOnly": "npm run release:check"
|
|
69
69
|
},
|
|
70
70
|
"optionalDependencies": {
|
|
71
|
-
"@supercov/cli-darwin-arm64": "0.0.
|
|
72
|
-
"@supercov/cli-darwin-x64": "0.0.
|
|
73
|
-
"@supercov/cli-linux-arm64-gnu": "0.0.
|
|
74
|
-
"@supercov/cli-linux-arm64-musl": "0.0.
|
|
75
|
-
"@supercov/cli-linux-x64-gnu": "0.0.
|
|
76
|
-
"@supercov/cli-linux-x64-musl": "0.0.
|
|
71
|
+
"@supercov/cli-darwin-arm64": "0.0.30",
|
|
72
|
+
"@supercov/cli-darwin-x64": "0.0.30",
|
|
73
|
+
"@supercov/cli-linux-arm64-gnu": "0.0.30",
|
|
74
|
+
"@supercov/cli-linux-arm64-musl": "0.0.30",
|
|
75
|
+
"@supercov/cli-linux-x64-gnu": "0.0.30",
|
|
76
|
+
"@supercov/cli-linux-x64-musl": "0.0.30"
|
|
77
77
|
},
|
|
78
78
|
"peerDependencies": {
|
|
79
79
|
"@playwright/test": ">=1.55.0",
|