CodeSampleX

Recordsnpmvitest3.2.7

Change the conditions
Fixed
Runtimenode (version not recorded) Execution contextnode
Filter OSwindows 11 Package version3.2.7 Symbolwhole package Architecturex64 Package managerpnpm 10 Clear filters

Current conditions

vitest @3.2.7windows 11 · x64 · node (version not recorded) · pnpm 10 · 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.

there is a sample here, and nothing of ours has run it at this coordinate yet (13)

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
1
Independent reporting peers
1
Last recorded
2026-09-01
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 17 · Steady 7

First observed break

3.2.7

windows · node@24.13 · moduleSystem=esm · executionContext=node

32 FAIL · stage: UNKNOWN · fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10

View exact conditions View failure cluster
Library Version Health Measured there Projects
@vitest/expect 3.2.7 CANDIDATE Correlated change; unproven combination contract passed 5 project-days
@vitest/mocker 3.2.7 CANDIDATE Correlated change; unproven combination contract passed 4 project-days
@vitest/pretty-format 3.2.7 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
@vitest/runner 3.2.7 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
@vitest/snapshot 3.2.7 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
@vitest/spy 3.2.7 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
@vitest/utils 3.2.7 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
expect-type 1.4.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
pathe 2.0.3 CANDIDATE Correlated change; unproven combination contract passed 4 project-days
picomatch 4.0.5 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
picomatch 4.0.7 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
std-env 3.10.0 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
tinyexec 0.3.2 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
tinyglobby 0.2.17 CANDIDATE Correlated change; unproven combination contract passed 5 project-days
tinyrainbow 2.0.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
vite 7.3.6 CANDIDATE Correlated change; unproven combination contract passed 5 project-days
vite-node 3.2.4 CANDIDATE Correlated change; unproven combination contract passed 4 project-days
@types/chai 5.2.3 PASS All observations passed contract passed 5 project-days
chai 5.3.3 PASS All observations passed contract passed 2 project-days
debug 4.4.3 PASS All observations passed contract passed 5 project-days
magic-string 0.30.21 PASS All observations passed contract passed 2 project-days
tinybench 2.9.0 PASS All observations passed contract passed 2 project-days
tinypool 1.1.1 PASS All observations passed contract passed 3 project-days
why-is-node-running 2.3.0 PASS All observations passed contract passed 2 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.104.0.184.0.164.0.03.2.73.2.43.0.02.1.9
@vitest/expect 4.1.11 4.1.10 4.0.18 4.0.16 4.0.0 3.2.7 3.2.4 3.0.0 2.1.9
@vitest/mocker 4.1.11 4.1.10 4.0.18 4.0.16 4.0.0 3.2.7 3.2.4 3.0.0 2.1.9
@vitest/pretty-format 4.1.11 4.1.10 4.0.18 4.0.16 4.0.0 3.2.7 3.2.7 3.2.7 2.1.9
@vitest/runner 4.1.11 4.1.10 4.0.18 4.0.16 4.0.0 3.2.7 3.2.4 3.0.0 2.1.9
@vitest/snapshot 4.1.11 4.1.10 4.0.18 4.0.16 4.0.0 3.2.7 3.2.4 3.0.0 2.1.9
@vitest/spy 4.1.11 4.1.10 4.0.18 4.0.16 4.0.0 3.2.7 3.2.4 3.0.0 2.1.9
@vitest/utils 4.1.11 4.1.10 4.0.18 4.0.16 4.0.0 3.2.7 3.2.4 3.0.0 2.1.9
es-module-lexer 2.3.2 2.3.2 1.7.0 1.7.0 1.7.0 — — — —
expect-type 1.4.0 1.4.0 1.4.0 1.3.0 1.4.0 1.4.0 1.4.0 1.4.0 1.4.0
obug 2.1.4 2.1.4 2.2.1 2.1.1 — — — — —
pathe 2.0.3 2.0.3 2.0.3 2.0.3 2.0.3 2.0.3 2.0.3 2.0.3 1.1.2
picomatch 4.0.7 4.0.5 4.0.7 4.0.3 4.0.5 4.0.5 4.0.7 — —
std-env 4.2.0 4.2.0 3.10.0 3.10.0 3.10.0 3.10.0 3.10.0 3.10.0 3.10.0
tinyexec 1.3.0 1.3.0 1.3.1 1.0.2 0.3.2 0.3.2 0.3.2 0.3.2 0.3.2
tinyglobby 0.2.17 0.2.17 0.2.17 0.2.15 0.2.17 0.2.17 0.2.17 — —
tinyrainbow 3.1.1 3.1.1 3.1.1 3.0.3 3.1.1 2.0.0 2.0.0 2.0.0 1.2.0
vite 8.2.2 8.2.1 7.3.6 7.3.1 7.3.6 7.3.6 7.3.6 6.4.3 5.4.21
vite-node — — — — — 3.2.4 3.2.4 3.0.0 2.1.9
@types/chai — — — — — 5.2.3 5.2.3 — —
chai — — — — — 5.3.3 5.3.3 5.3.3 5.3.3
debug — — — — 4.4.3 4.4.3 4.4.3 4.4.3 4.4.3
magic-string 0.30.21 0.30.21 0.30.21 0.30.21 0.30.21 0.30.21 0.30.21 0.30.21 0.30.21
tinybench 2.9.0 2.9.0 2.9.0 2.9.0 2.9.0 2.9.0 2.9.0 2.9.0 2.9.0
tinypool — — — — — 1.1.1 1.1.1 1.1.1 1.1.1
why-is-node-running 2.3.0 2.3.0 2.3.0 2.3.0 2.3.0 2.3.0 2.3.0 2.3.0 2.3.0

Moved: 18 · unchanged at every release: 7

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