CodeSampleX

Recordsnpmvitest

Change the conditions
Fixed
SymbolReportersMap Architecturex64
Filter Runtimenode 22 Package version2.1.9 Execution contextnode Clear filters

Current conditions

ReportersMap @2.1.9x64 · node 22 · 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
1 / 1
Contract verifications
1 / 1
Independent reporting peers
1
Last recorded
2026-08-27

Exact records

This slice is down to its measured combinations — the environments below are exactly what ran.

Dependencies

LibraryVersionMeasured thereProjects
@vitest/expect 2.1.9 contract passed 4 project-days
@vitest/mocker 2.1.9 contract passed 4 project-days
@vitest/pretty-format 2.1.9 contract passed 4 project-days
@vitest/runner 2.1.9 contract passed 4 project-days
@vitest/snapshot 2.1.9 contract passed 4 project-days
@vitest/spy 2.1.9 contract passed 4 project-days
@vitest/utils 2.1.9 contract passed 4 project-days
chai 5.3.3 contract passed 4 project-days
debug 4.4.3 contract passed 4 project-days
expect-type 1.4.0 contract passed 4 project-days
magic-string 0.30.21 contract passed 4 project-days
pathe 1.1.2 contract passed 4 project-days
std-env 3.10.0 contract passed 3 project-days
tinybench 2.9.0 contract passed 3 project-days
tinyexec 0.3.2 contract passed 3 project-days
tinypool 1.1.1 contract passed 3 project-days
tinyrainbow 1.2.0 contract passed 3 project-days
vite 5.4.21 contract passed 3 project-days
vite-node 2.1.9 contract passed 3 project-days
why-is-node-running 2.3.0 contract passed 3 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.