CodeSampleX

Recordsnpm@vitest/spy4.1.10

Change the conditions
Fixed
OSwindows 11 Package version4.1.10 Execution contextnode
Filter Runtimenode 24 Symbolwhole package Architecturex64 Package managernpm 11 Clear filters

Current conditions

@vitest/spy @4.1.10windows 11 · x64 · node 24 · npm 11 · node

package-level total, not an API

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

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 0

First observed break

3.2.7

windows · node@24.13 · moduleSystem=esm · executionContext=node

31 FAIL · stage: UNKNOWN · fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10

View exact conditions View failure cluster

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.

Library3.2.73.2.43.0.02.1.9
tinyspy 4.0.4 4.0.6 3.0.2 3.0.2

Moved: 1 · unchanged at every release: 0

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