CodeSampleX

Recordsnpmvite-node3.2.4vite-node.ModuleCacheMap

Change the conditions
Fixed
OSdebian glibc Package version3.2.4 Symbolvite-node.ModuleCacheMap
Filter Runtimenode 22 Architecturex64 Package managernpm Execution contextnode libcglibc Clear filters

Current conditions

vite-node.ModuleCacheMap @3.2.4debian glibc · 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
2 / 2
Contract verifications
1 / 1
Independent reporting peers
1
Last recorded
2026-09-17

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 3

First observed break

3.2.4

executionContext=node

40 FAIL · stage: PROCESS_START · fingerprint: sha256:c12549970456efb5abdc90b679695c6689107d4f097d612245d6bfb25e01ec32

Library Version Health Measured there Projects
pathe 2.0.3 CANDIDATE Correlated change; unproven combination contract passed 32 project-days
vite 7.3.6 CANDIDATE Correlated change; unproven combination contract passed 31 project-days
cac 6.7.14 PASS All observations passed contract passed 32 project-days
debug 4.4.3 PASS All observations passed contract passed 32 project-days
es-module-lexer 1.7.0 PASS All observations passed contract passed 32 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.

Moved: 2 · unchanged at every release: 3

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