CodeSampleX

Recordsnpm@vitest/snapshot4.0.0

Change the conditions
Fixed
Runtimenode 22 Package version4.0.0
Filter OSalpine musl Symbolwhole package Architecturex64 Package managernpm Execution contextnode libcmusl Clear filters

Current conditions

@vitest/snapshot @4.0.0alpine musl · x64 · node 22 · npm · node

package-level total, not an API

Recorded as present in projects. Nothing was run at this coordinate.

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
1
Independent reporting peers
1
Last recorded
2026-09-08

Dependency Health

Observed combinations and failure evidence for this release

Changed 2 · Steady 1

Dependency changes observed: 2. No failure evidence is linked to these resolved trees yet.

Library Version Health Measured there Projects
@vitest/pretty-format 4.0.0 CHANGED Version changed, no linked failure builds observed 1 project-day
pathe 2.0.3 CHANGED Version changed, no linked failure contract passed 1 project-day
magic-string 0.30.21 PASS All observations passed 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.

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.