CodeSampleX

Recordsnpm@vitest/mocker2.1.9

Change the conditions
Fixed
OSubuntu glibc Package version2.1.9
Filter Runtimenode 22 Symbolwhole package Architecturex64 Package managernpm 10 Execution contextnode libcglibc Clear filters

Current conditions

@vitest/mocker @2.1.9ubuntu glibc · x64 · node 22 · npm 10 · node

package-level total, not an API

0 of 5 passed

Verified — this network ran a contract at this coordinate.

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

Project observations
16 / 16
Contract verifications
0 / 5
Usage records
20
Independent reporting peers
2
Last recorded
2026-08-31
Evidence you can open

Dependencies

LibraryVersionMeasured thereProjects
@vitest/spy 2.1.9 contract passed 3 project-days
estree-walker 3.0.3 contract passed 3 project-days
magic-string 0.30.21 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.

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/spy 4.1.11 4.1.10 3.2.7 2.1.9
estree-walker 3.0.3 3.0.3 3.0.3 3.0.3
magic-string 0.30.21 0.30.21 0.30.21 0.30.21

Moved: 1 · unchanged at every release: 2

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