Recordsnpm@vitest/spyfailure issue
Failure signature
PROJECT_TEST exit 1 ×2
FAIL src/main/sources/runtime/electronPageWiring.test.ts > production source runtime wiring > backs a context with an ElectronSourcePage and loads the initial …
Evidence quality: complete · test-runner-diagnostic · First recorded: 2026-09-13 · Last seen: 2026-09-13
sha256:63f66b355db5…
Where it was measured
PASS means the release recorded a passing observation at PROJECT_TEST and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- 4.1.11 FAIL
- 4.1.10 PASS 1 passing observations
- 4.0.18 PASS 2 passing observations
- 4.0.16 PASS 1 passing observations
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 ×2 2026-09-13 → 2026-09-13
Nearest known PASS/FAIL boundaries
The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.
-
Last passing release 4.1.10 → first failing release 4.1.11
Both trees resolved every dependency to the same version. Nothing here moved.
Evidence gaps
- No failure domain was inferred for this failure.
Published answers for the affected releases
- @vitest/spy 4.1.11: fn, isMockFunction, spyOn This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWfnisMockFunctionspyOnnode 22.23.2 MIT-0 · 2026-08-28