Recordsnpm@vitest/snapshot3.2.7@vitest/snapshot.SnapshotClient
Change the conditions
Current conditions
@vitest/snapshot.SnapshotClient @3.2.7ubuntu glibc · x64 · node 22 · npm 10 · node
1 of 2 passed
Observed — real project builds reported from this coordinate.
no sample at this coordinate yet
- 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
Dependency Health
Observed combinations and failure evidence for this release
First observed break
3.2.7
windows · node@24.13 · moduleSystem=esm · executionContext=node
31 FAIL
· stage: UNKNOWN
· fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @vitest/pretty-format | 3.2.7 | CANDIDATE Correlated change; unproven combination | contract passed | 6 project-days |
| pathe | 2.0.3 | CANDIDATE Correlated change; unproven combination | contract passed | 6 project-days |
| magic-string | 0.30.21 | PASS All observations passed | 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 | 4.1.11 | 4.1.10 | 4.0.18 | 4.0.16 | 4.0.0 | 3.2.7 | 3.2.4 | 3.0.0 | 2.1.9 |
|---|---|---|---|---|---|---|---|---|---|
| @vitest/pretty-format | 4.1.11 | 4.1.10 | 4.0.18 | 4.0.16 | 4.0.0 | 3.2.7 | 3.2.4 | 3.0.0 | 2.1.9 |
| @vitest/utils | 4.1.11 | 4.1.10 | — | — | — | — | — | — | — |
| pathe | 2.0.3 | 2.0.3 | 2.0.3 | 2.0.3 | 2.0.3 | 2.0.3 | 2.0.3 | 2.0.3 | 1.1.2 |
| magic-string | 0.30.21 | 0.30.21 | 0.30.21 | 0.30.21 | 0.30.21 | 0.30.21 | 0.30.21 | 0.30.21 | 0.30.21 |
Moved: 3 · unchanged at every release: 1
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 PROCESS_START process start failed Evidence gap ×10 2.1.9 → 3.0.0 → 3.2.4 → 3.2.7 executionContext=node sha256:c12549970456…· structured-termination · gap diagnostic-missingEvidence quality: partial · Environment variants: 3 · First recorded: 2026-08-31 · Last seen: 2026-09-16Diagnostic re-verification candidate
-
observed PROJECT_PROCESS ERR_ASSERTION Evidence gap ×7 3.2.7 → 4.1.10 executionContext=nodeEvidence quality: legacy-evidence-incomplete · Environment variants: 3 · 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=cjs · os=linux · runtime=node@22.23 @vitest/snapshot.SnapshotClientEvidence quality: legacy-evidence-incomplete · Environment variants: 1 · First recorded: 2026-08-27 · Last seen: 2026-08-27
-
observed UNKNOWN exit 1 ERR_MODULE_NOT_FOUND Evidence gap ×1 3.2.7 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:88af852f99a8…node:internal/modules/package_json_reader:<n> · throw new ERR_MODULE_NOT_FOUND(packageName, fileURLToPath(base), null); · ^ …node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31Diagnostic re-verification candidate