CodeSampleX

Recordsnpm@vitest/snapshot3.2.7

Change the conditions
Fixed
Package version3.2.7 Package managernpm 11
Filter OSwindows 11 Runtimenode 24 Symbolwhole package Architecturex64 Execution contextnode Clear filters

Current conditions

@vitest/snapshot @3.2.7windows 11 · x64 · node 24 · npm 11 · node

package-level total, not an API

461 of 484 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
461 / 484
Contract verifications
nothing at this coordinate
Usage records
67
Independent reporting peers
1
Failures with a captured fingerprint
0 / 23
Last recorded
2026-11-18

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Unknown 1 · Steady 0

First observed break

3.2.7

windows · executionContext=node

39 FAIL · stage: PROJECT_TEST

Library Version Health Measured there Projects
@vitest/pretty-format 3.2.7 CANDIDATE Correlated change; unproven combination 6 project-days
pathe 2.0.3 CANDIDATE Correlated change; unproven combination 6 project-days
magic-string 0.30.21 UNKNOWN No linked outcome measured 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.

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

Showing the 12 most-reported of 208 recorded failure clusters. The rest are single reports.