Recordsnpm@vitest/snapshot4.1.10@vitest/snapshot.SnapshotState
Change the conditions
Current conditions
@vitest/snapshot.SnapshotState @4.1.10ubuntu glibc · x64 · node 22 · npm 10 · node
1 of 1 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 / 1
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Last recorded
- 2026-08-31
Dependencies
| Library | Version | Measured there | Projects |
|---|---|---|---|
| @vitest/pretty-format | 4.1.10 | contract passed | 1 project-day |
| @vitest/utils | 4.1.10 | contract passed | 1 project-day |
| magic-string | 0.30.21 | contract passed | 1 project-day |
| pathe | 2.0.3 | contract passed | 1 project-day |
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 | 3.2.7 | 2.1.9 |
|---|---|---|---|---|
| @vitest/pretty-format | 4.1.11 | 4.1.10 | 3.2.7 | 2.1.9 |
| @vitest/utils | 4.1.11 | 4.1.10 | — | — |
| pathe | 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 |
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 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