CodeSampleX

Recordsnpmvitest3.2.7vitest.createVitest

Change the conditions
Fixed
OSalpine musl Symbolvitest.createVitest
Filter Runtimenode 22 Package version3.2.7 Architecturex64 Package managernpm Execution contextnode libcmusl Clear filters

Current conditions

vitest.createVitest @3.2.7alpine 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-21

Dependencies

LibraryVersionMeasured thereProjects
@types/chai 5.2.3 contract passed 5 project-days
@vitest/expect 3.2.7 contract passed 5 project-days
@vitest/mocker 3.2.7 contract passed 4 project-days
@vitest/pretty-format 3.2.7 contract passed 3 project-days
@vitest/runner 3.2.7 contract passed 3 project-days
@vitest/snapshot 3.2.7 contract passed 3 project-days
@vitest/spy 3.2.7 contract passed 2 project-days
@vitest/utils 3.2.7 contract passed 2 project-days
chai 5.3.3 contract passed 2 project-days
debug 4.4.3 contract passed 5 project-days
expect-type 1.4.0 contract passed 2 project-days
magic-string 0.30.21 contract passed 2 project-days
pathe 2.0.3 contract passed 4 project-days
picomatch 4.0.5 contract passed 2 project-days
picomatch 4.0.7 contract passed 3 project-days
std-env 3.10.0 contract passed 3 project-days
tinybench 2.9.0 contract passed 2 project-days
tinyexec 0.3.2 contract passed 3 project-days
tinyglobby 0.2.17 contract passed 5 project-days
tinypool 1.1.1 contract passed 3 project-days
tinyrainbow 2.0.0 contract passed 2 project-days
vite 7.3.6 contract passed 5 project-days
vite-node 3.2.4 contract passed 4 project-days
why-is-node-running 2.3.0 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.

Recent failure clusters