CodeSampleX

Recordsnpm@vitest/snapshot3.2.7@vitest/snapshot.SnapshotClient

Change the conditions
Fixed
Package version3.2.7 Symbol@vitest/snapshot.SnapshotClient libcglibc
Filter OSubuntu glibc Runtimenode 22 Architecturex64 Package managernpm 10 Execution contextnode Clear filters

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

Dependencies

LibraryVersionMeasured thereProjects
@vitest/pretty-format 3.2.7 contract passed 6 project-days
magic-string 0.30.21 contract passed 6 project-days
pathe 2.0.3 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.

Library4.1.114.1.103.2.72.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