CodeSampleX

Recordsnpmvite-node2.1.9

Change the conditions
Fixed
Package version2.1.9 Package managerpnpm 10 Execution contextnode
Filter OSwindows 11 Runtimenode 24 Symbolwhole package Architecturex64 Clear filters

Current conditions

vite-node @2.1.9windows 11 · x64 · node 24 · pnpm 10 · node

package-level total, not an API

32 of 34 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 (14)

Project observations
32 / 34
Contract verifications
nothing at this coordinate
Usage records
2
Independent reporting peers
1
Failures with a captured fingerprint
0 / 2
Last recorded
2026-09-01

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 3 · Steady 3

First observed break

2.1.9

executionContext=node

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

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

Showing the 12 most-reported of 13 recorded failure clusters. The rest are single reports.