CodeSampleX

Recordsnpm@vitest/runner2.1.9onTestFinished

Change the conditions
Fixed
OSalpine musl Package version2.1.9 SymbolonTestFinished
Filter Runtimenode 22 Architecturex64 Package managernpm Execution contextnode libcmusl Clear filters

Current conditions

onTestFinished @2.1.9alpine musl · x64 · node 22 · npm · node

1 of 1 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate came back clean (1)

Project observations
nothing at this coordinate
Contract verifications
1 / 1
Last recorded
2026-08-26

Dependencies

LibraryVersionMeasured thereProjects
@vitest/utils 2.1.9 contract passed 4 project-days
pathe 1.1.2 contract passed 4 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.103.2.72.1.9
@vitest/utils 4.1.11 4.1.10 3.2.7 2.1.9
pathe 2.0.3 2.0.3 2.0.3 1.1.2
strip-literal 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