Recordsnpmvite8.2.1startVitest
Change the conditions
Current conditions
startVitest @8.2.1alpine musl · x64 · node 22 · npm · node
2 of 2 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate came back clean (1)
- Project observations
- 1 / 1
- Contract verifications
- 2 / 2
- Independent reporting peers
- 1
- Cross-checked
- reproduced by two or more independent peers
- Last recorded
- 2026-09-08
Dependency Health
Observed combinations and failure evidence for this release
First observed break
8.2.1
executionContext=node · moduleSystem=esm
5 FAIL · stage: PROJECT_PROCESS
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| picomatch | 4.0.5 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| postcss | 8.5.26 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| rolldown | 1.2.4 | CANDIDATE Correlated change; unproven combination | builds observed | 3 project-days |
| tinyglobby | 0.2.17 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| lightningcss | 1.33.0 | PASS All observations passed | contract passed | 3 project-days |
| vitest | 4.1.10 | PASS All observations passed | contract passed | 1 project-day |
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 | 8.3.0 | 8.2.2 | 8.2.1 | 7.3.6 | 7.3.1 | 6.4.3 | 6.2.0 | 5.4.21 | 5.4.14 |
|---|---|---|---|---|---|---|---|---|---|
| esbuild | — | — | — | 0.28.2 | 0.27.2 | 0.25.12 | 0.25.12 | 0.21.5 | 0.21.5 |
| picomatch | 4.0.7 | 4.0.7 | 4.0.5 | 4.0.5 | 4.0.3 | 4.0.5 | — | — | — |
| postcss | 8.5.28 | 8.5.28 | 8.5.26 | 8.5.26 | 8.5.6 | 8.5.26 | 8.5.28 | 8.5.25 | 8.5.28 |
| rolldown | 1.2.8 | 1.2.7 | 1.2.4 | — | — | — | — | — | — |
| rollup | — | — | — | 4.63.3 | 4.54.0 | 4.63.3 | 4.62.4 | 4.62.3 | 4.63.1 |
| tinyglobby | 0.2.17 | 0.2.17 | 0.2.17 | 0.2.17 | 0.2.15 | 0.2.17 | — | — | — |
| fdir | — | — | — | 6.5.0 | 6.5.0 | 6.5.0 | — | — | — |
| lightningcss | 1.33.0 | 1.33.0 | 1.33.0 | — | — | — | — | — | — |
| vitest | — | — | 4.1.10 | — | — | — | — | — | — |
Moved: 6 · 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_PROCESS ERR_ASSERTION Evidence gap ×5 7.3.6 → 8.2.1 executionContext=node · moduleSystem=esmEvidence quality: legacy-evidence-incomplete · Environment variants: 2 · First recorded: 2026-08-14 · Last seen: 2026-08-30Diagnostic re-verification candidate