Recordsnpmvite-node2.1.9vite-node.ModuleCacheMap
Change the conditions
Current conditions
vite-node.ModuleCacheMap @2.1.9ubuntu glibc · x64 · node 22 · npm 10 · node
0 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 failed (1)
- Project observations
- 6 / 6
- Contract verifications
- 0 / 1
- Independent reporting peers
- 2
- Last recorded
- 2026-09-07
Dependency Health
Observed combinations and failure evidence for this release
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.
| Library | 3.2.4 | 3.0.0 | 2.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
-
observed PROCESS_START process start failed Evidence gap ×40 2.1.9 → 3.0.0 → 3.2.4 executionContext=node sha256:c12549970456…· structured-termination · gap diagnostic-missingEvidence quality: partial · Environment variants: 3 · First recorded: 2026-08-31 · Last seen: 2026-09-16Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×3 2.1.9 → 3.0.0 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:8fd30f2a6304…fil<path>:<n> · throw new Error(errorMsg); · ^ · Error: Vitest failed to access its internal state.node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-09-08Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×2 2.1.9 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 vite-node.ModuleCacheMap sha256:91ad26545eb1…node:internal/modules/cjs/loader:<n> · throw err; · ^ · Error: Cannot find module <str>node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-09-07Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 2.1.9 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:72ba2d1e946f…<path>: No module named pippython3 · unclassified-diagnostic · outer python3 · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 2.1.9 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:d7f5d491441c…Traceback (most recent call last): · File <str>, line 71, in <module> · AssertionError: is_annotated must return True for Annotated· unclassified-diagnostic · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 2.1.9 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:42623a56826f…fil<path>:<n> · Object.defineProperty(expect.not, expectAssertionName, { · ^ · TypeError: Object.defineProperty called on non-objectnode · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-04 · Last seen: 2026-09-04Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 2.1.9 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:43ce3cf35eeb…(!) Could not auto-determine entry point from rollupOptions or html files and there are no explicit optimizeDeps.include patterns. Skipping dependency …node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-07 · Last seen: 2026-09-07Diagnostic re-verification candidate