CodeSampleX

Recordsnpm@vitest/mocker3.2.7@vitest/mocker.AutospiedModule

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

Current conditions

@vitest/mocker.AutospiedModule @3.2.7ubuntu glibc · x64 · node 22 · npm 10 · node

3 of 4 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
3 / 4
Contract verifications
nothing at this coordinate
Independent reporting peers
2
Failures with a captured fingerprint
0 / 1
Last recorded
2026-08-27
Evidence you can open

Dependencies

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