Recordsnpm@vitest/spyfailure issue
Failure signature
PROJECT_PROCESS ERR_ASSERTION Evidence gap ×7
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-08-14 · Last seen: 2026-08-30
@vitest/spy.fn @vitest/spy.isMockFunction @vitest/spy.mocks @vitest/spy.spyOn
Where it was measured
PASS means the release recorded a passing observation at PROJECT_PROCESS 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 PASS 18 passing observations
- 4.1.10 FAIL
- 4.0.18 PASS 6 passing observations
- 4.0.16 PASS 11 passing observations
- 4.0.0 not measured
- 3.2.7 FAIL
- 3.2.4 PASS 2 passing observations
- 3.0.0 PASS 4 passing observations
- 2.1.9 PASS 83 passing observations
Where it reproduced
- executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 ×6 2026-08-27 → 2026-08-30
- executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×1 2026-08-14 → 2026-08-14
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 3.2.4 → first failing release 3.2.7
What differs across the boundary
- tinyspy 4.0.6 → 4.0.4 hypothesis
A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.
-
Last failing release 3.2.7 → first passing release 4.0.16
Releases between them never measured at this stage: 1
What differs across the boundary
- tinyspy — → 4.0.4 hypothesis
A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.
-
Last passing release 4.0.18 → first failing release 4.1.10
One side of this boundary has no resolved dependency tree, so nothing could be compared.
-
Last failing release 4.1.10 → first passing release 4.1.11
Both trees resolved every dependency to the same version. Nothing here moved.
Dependency versions across releases
What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.
Moved: 1 · unchanged at every release: 0
An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.
Evidence gaps
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- Releases in this window never measured at PROJECT_PROCESS: 1
- No resolved dependency tree for 4.0.18 or for 4.1.10, so the versions either side of the boundary could not be compared.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- @vitest/spy 4.1.10: function and method spying with spyOn and fn 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-27
- @vitest/spy 3.2.7: spy function and method interception with 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. HOWfnspyOnnode 22.23.2 MIT-0 · 2026-08-23