Recordsnpmvitestfailure issue
Failure signature
PROJECT_TYPECHECK Evidence gap ×2
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-08-20 · Last seen: 2026-08-21
vitest.afterAll vitest.afterEach vitest.beforeAll vitest.beforeEach vitest.defineConfig vitest.describe vitest.expect vitest.it vitest.vi
Where it was measured
PASS means the release recorded a passing observation at PROJECT_TYPECHECK and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- 4.1.11 FAIL
- 4.1.10 not measured
- 4.0.18 not measured
- 4.0.16 PASS 8 passing observations
- 3.2.7 not measured
- 3.2.4 not measured
- 3.0.0 not measured
- 2.1.9 FAIL
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=windows · runtime=node@22.16 ×1 2026-08-20 → 2026-08-20
- executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 ×1 2026-08-21 → 2026-08-21
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 failing release 2.1.9 → first passing release 4.0.16
Releases between them never measured at this stage: 4
What differs across the boundary
- @vitest/expect 4.0.16 → 2.1.9 hypothesis
- @vitest/mocker 4.0.16 → 2.1.9 hypothesis
- @vitest/pretty-format 4.0.16 → 2.1.9 hypothesis
- @vitest/runner 4.0.16 → 2.1.9 hypothesis
- @vitest/snapshot 4.0.16 → 2.1.9 hypothesis
- @vitest/spy 4.0.16 → 2.1.9 hypothesis
- @vitest/utils 4.0.16 → 2.1.9 hypothesis
- chai — → 5.3.3 hypothesis
- debug — → 4.4.3 hypothesis
- es-module-lexer 1.7.0 → — hypothesis
- expect-type 1.3.0 → 1.4.0 hypothesis
- obug 2.1.1 → — hypothesis
- pathe 2.0.3 → 1.1.2 hypothesis
- picomatch 4.0.3 → — hypothesis
- tinyexec 1.0.2 → 0.3.2 hypothesis
- tinyglobby 0.2.15 → — hypothesis
- tinypool — → 1.1.1 hypothesis
- tinyrainbow 3.0.3 → 1.2.0 hypothesis
- vite 7.3.1 → 5.4.21 hypothesis
- vite-node — → 2.1.9 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 passing release 4.0.16 → first failing release 4.1.11
Releases between them never measured at this stage: 2
What differs across the boundary
- @vitest/expect 4.0.16 → 4.1.11 hypothesis
- @vitest/mocker 4.0.16 → 4.1.11 hypothesis
- @vitest/pretty-format 4.0.16 → 4.1.11 hypothesis
- @vitest/runner 4.0.16 → 4.1.11 hypothesis
- @vitest/snapshot 4.0.16 → 4.1.11 hypothesis
- @vitest/spy 4.0.16 → 4.1.11 hypothesis
- @vitest/utils 4.0.16 → 4.1.11 hypothesis
- es-module-lexer 1.7.0 → 2.3.2 hypothesis
- expect-type 1.3.0 → 1.4.0 hypothesis
- obug 2.1.1 → 2.1.4 hypothesis
- picomatch 4.0.3 → 4.0.5, 4.0.7 hypothesis
- std-env 3.10.0 → 4.2.0 hypothesis
- tinyexec 1.0.2 → 1.3.0 hypothesis
- tinyglobby 0.2.15 → 0.2.17 hypothesis
- tinyrainbow 3.0.3 → 3.1.1 hypothesis
- vite 7.3.1 → 7.3.6, 8.2.2 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.
Moved: 18 · unchanged at every release: 7
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_TYPECHECK: 5
- No failure domain was inferred for this failure.
Published answers for the affected releases
- vitest 4.1.11: vi 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. HOWvitest.vinode 22.23.2 MIT-0 · 2026-08-28
- vitest 4.1.11: afterEach 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. HOWvitest.afterEachnode 22.23.2 MIT-0 · 2026-08-28
- vitest 4.1.11: it 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. HOWvitest.itnode 22.23.2 MIT-0 · 2026-08-28
- vitest 2.1.9: vi 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. HOWvinode 22.23.2 MIT-0 · 2026-08-30
- vitest 2.1.9: vi 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. HOWvitest.vinode 22.23.2 MIT-0 · 2026-08-28
- vitest 2.1.9: it 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. HOWvitest.itnode 22.23.2 MIT-0 · 2026-08-28