CodeSampleX

Recordsnpmvite-node3.0.0

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

Current conditions

vite-node @3.0.0ubuntu glibc · x64 · node 22 · npm 10 · node

package-level total, not an API

0 of 11 passed

Verified — this network ran a contract at this coordinate.

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

Project observations
7 / 7
Contract verifications
0 / 11
Usage records
6
Independent reporting peers
3
Last recorded
2026-09-08
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 3

First observed break

3.0.0

executionContext=node

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

View exact conditions View failure cluster
Library Version Health Measured there Projects
pathe 2.0.3 CANDIDATE Correlated change; unproven combination contract passed 10 project-days
vite 6.4.3 CANDIDATE Correlated change; unproven combination contract passed 10 project-days
cac 6.7.14 PASS All observations passed contract passed 10 project-days
debug 4.4.3 PASS All observations passed contract passed 10 project-days
es-module-lexer 1.7.0 PASS All observations passed contract passed 10 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.

Library3.2.43.0.02.1.9
pathe 2.0.3 2.0.3 1.1.2
vite 7.3.6 6.4.3 5.4.14
cac 6.7.14 6.7.14 6.7.14
debug 4.4.3 4.4.3 4.4.3
es-module-lexer 1.7.0 1.7.0 1.7.0

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