Recordsnpm@vitest/spy3.2.7@vitest/spy.fn
Change the conditions
Current conditions
@vitest/spy.fn @3.2.7ubuntu glibc · x64 · node 22 · npm 10 · node
1 of 2 passed
Observed — real project builds reported from this coordinate.
there is a sample here, and nothing of ours has run it at this coordinate yet (1)
- Project observations
- 1 / 2
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Failures with a captured fingerprint
- 0 / 1
- Last recorded
- 2026-08-27
Dependencies
| Library | Version | Measured there | Projects |
|---|---|---|---|
| tinyspy | 4.0.4 | contract passed | 6 project-days |
The measured column is about each dependency's own release, not about the pair. A resolver placing two releases side by side is not evidence that they work together.
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.
| Library | 3.2.7 | 2.1.9 |
|---|---|---|
| tinyspy | 4.0.4 | 3.0.2 |
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.
Recent failure clusters
-
observed PROJECT_PROCESS ERR_MODULE_NOT_FOUND Evidence gap ×7 3.2.7 → 4.1.10 executionContext=node · moduleSystem=esmEvidence quality: legacy-evidence-incomplete · Environment variants: 2 · First recorded: 2026-08-14 · Last seen: 2026-08-30Diagnostic re-verification candidate
-
observed PROJECT_PROCESS ERR_ASSERTION Evidence gap ×1 3.2.7 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 @vitest/spy.fnEvidence quality: legacy-evidence-incomplete · Environment variants: 1 · First recorded: 2026-08-27 · Last seen: 2026-08-27