Recordsnpm@vitest/runnerfailure issue
Failure signature
PROCESS_START process start failed Evidence gap ×10
Evidence quality: partial · structured-termination · gap diagnostic-missing · First recorded: 2026-08-31 · Last seen: 2026-09-16
sha256:c12549970456…
Where it was measured
PASS means the release recorded a passing observation at PROCESS_START and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- 4.0.18 not measured
- 4.0.16 not measured
- 4.0.0 not measured
- 3.2.7 FAIL
- 3.2.4 FAIL
- 3.0.0 FAIL
- 2.1.9 FAIL
Where it reproduced
- executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 ×7 2026-09-08 → 2026-09-08
- executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×2 2026-09-16 → 2026-09-16
- executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 ×1 2026-08-31 → 2026-08-31
Nearest known PASS/FAIL boundaries
No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.
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 | 4.0.18 | 4.0.16 | 4.0.0 | 3.2.7 | 3.2.4 | 3.0.0 | 2.1.9 |
|---|---|---|---|---|---|---|---|
| @vitest/utils | 4.0.18 | 4.0.16 | 4.0.0 | 3.2.7 | 3.2.4 | 3.0.0 | 2.1.9 |
| pathe | 2.0.3 | 2.0.3 | 2.0.3 | 2.0.3 | 2.0.3 | 2.0.3 | 1.1.2 |
| strip-literal | — | — | — | 3.1.0 | 3.1.0 | — | — |
Moved: 2 · unchanged at every release: 1
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.
Evidence gaps
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- The captured output could not establish: diagnostic-missing.
- No release in this window recorded a passing observation at PROCESS_START.
- Releases in this window never measured at PROCESS_START: 3
- No failure domain was inferred for this failure.
Published answers for the affected releases
- @vitest/runner 3.2.7: execute test suites and hooks with custom runner using startTests This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWstartTestsdescribetestitbeforeAllafterAllbeforeEachafterEachonTestFinished MIT-0 · 2026-08-23