CodeSampleX

Recordsnpm@vitest/runner3.2.7@vitest/runner.onTestFinished

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

Current conditions

@vitest/runner.onTestFinished @3.2.7ubuntu glibc · x64 · node 22 · npm 10 · node

0 of 1 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 (1)

Project observations
0 / 1
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Failures with a captured fingerprint
0 / 1
Last recorded
2026-08-27
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 1

First observed break

3.2.7

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

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

View exact conditions View failure cluster
Library Version Health Measured there Projects
@vitest/utils 3.2.7 CANDIDATE Correlated change; unproven combination contract passed 6 project-days
pathe 2.0.3 CANDIDATE Correlated change; unproven combination contract passed 6 project-days
strip-literal 3.1.0 PASS All observations passed 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.104.0.184.0.164.0.03.2.73.2.43.0.02.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
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
strip-literal — — — — — 3.1.0 3.1.0 — —

Moved: 2 · 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