CodeSampleX

Recordsnpm@vitest/snapshot4.1.11

Change the conditions
Fixed
OSwindows Runtimenode 22 Package version4.1.11
Filter Symbolwhole package Architecturex64 Package managernpm 11 Execution contextnode Clear filters

Current conditions

@vitest/snapshot @4.1.11windows · x64 · node 22 · npm 11 · node

package-level total, not an API

15 of 16 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 (3)

Project observations
15 / 16
Contract verifications
nothing at this coordinate
Usage records
5
Independent reporting peers
1
Failures with a captured fingerprint
0 / 1
Last recorded
2026-08-24

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 3 · Steady 1

First observed break

4.1.11

windows · executionContext=node

39 FAIL · stage: PROJECT_TEST

Library Version Health Measured there Projects
@vitest/pretty-format 4.1.11 CANDIDATE Correlated change; unproven combination contract passed 10 project-days
@vitest/utils 4.1.11 CANDIDATE Correlated change; unproven combination contract passed 10 project-days
pathe 2.0.3 CANDIDATE Correlated change; unproven combination contract passed 10 project-days
magic-string 0.30.21 PASS All observations passed contract passed 10 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.

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