Recordsnpmvite-node3.2.4
Change the conditions
Current conditions
vite-node @3.2.4windows · x64 · node (version not recorded) · pnpm 10 · node
package-level total, not an API
Recorded as present in projects. Nothing was run at this coordinate.
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
- nothing at this coordinate
- Contract verifications
- nothing at this coordinate
- Usage records
- 1
- Independent reporting peers
- 1
- Last recorded
- 2026-09-01
Dependency Health
Observed combinations and failure evidence for this release
First observed break
3.2.4
windows · executionContext=node
47 FAIL · stage: PROJECT_TEST
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| pathe | 2.0.3 | CANDIDATE Correlated change; unproven combination | 32 project-days | |
| vite | 7.3.6 | CANDIDATE Correlated change; unproven combination | 31 project-days | |
| cac | 6.7.14 | UNKNOWN No linked outcome measured | 32 project-days | |
| debug | 4.4.3 | UNKNOWN No linked outcome measured | 32 project-days | |
| es-module-lexer | 1.7.0 | UNKNOWN No linked outcome measured | 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.
| 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 PROJECT_TEST ELIFECYCLE Evidence gap ×47 2.1.9 → 3.2.4 executionContext=node · os=windowsEvidence quality: legacy-evidence-incomplete · Environment variants: 5 · First recorded: 2026-08-21 · Last seen: 2026-11-21Diagnostic re-verification candidate
-
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 PROJECT_PROCESS ERR_ASSERTION Evidence gap ×10 2.1.9 → 3.2.4 executionContext=nodeEvidence quality: legacy-evidence-incomplete · Environment variants: 3 · First recorded: 2026-08-30 · Last seen: 2026-11-20Diagnostic re-verification candidate