Recordsnpm@vitest/runnerfailure issue
Failure signature
PROJECT_PROCESS ERR_ASSERTION Evidence gap ×1
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-08-27 · Last seen: 2026-08-27
@vitest/runner.afterAll @vitest/runner.afterEach @vitest/runner.beforeAll @vitest/runner.beforeEach @vitest/runner.describe @vitest/runner.it @vitest/runner.onTestFinished @vitest/runner.startTests @vitest/runner.suite @vitest/runner.test
Where it was measured
PASS means the release recorded a passing observation at PROJECT_PROCESS 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 PASS 6 passing observations
- 4.0.16 PASS 11 passing observations
- 4.0.0 not measured
- 3.2.7 FAIL
- 3.2.4 PASS 2 passing observations
- 3.0.0 PASS 4 passing observations
- 2.1.9 PASS 36 passing observations
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 ×1 2026-08-27 → 2026-08-27
Nearest known PASS/FAIL boundaries
The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.
-
Last passing release 3.2.4 → first failing release 3.2.7
What differs across the boundary
- @vitest/utils 3.2.4 → 3.2.7 hypothesis
A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.
-
Last failing release 3.2.7 → first passing release 4.0.16
Releases between them never measured at this stage: 1
What differs across the boundary
- @vitest/utils 4.0.16 → 3.2.7 hypothesis
- strip-literal — → 3.1.0 hypothesis
A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.
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.
- Releases in this window never measured at PROJECT_PROCESS: 1
- 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