Recordsnpmvite
Change the conditions
Current conditions
vite @5.4.21windows 11 · x64 · node 24 · pnpm 10 · node
32 of 34 passed
Observed — real project builds reported from this coordinate.
there is a sample here, and nothing of ours has run it at this coordinate yet (4)
- Project observations
- 32 / 34
- Contract verifications
- nothing at this coordinate
- Usage records
- 2
- Independent reporting peers
- 1
- Failures with a captured fingerprint
- 0 / 2
- Last recorded
- 2026-09-01
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
32 of 34 passed
Observed — real project builds reported from this coordinate.
-
vite.defineConfig
32 of 34 passed
Observed — real project builds reported from this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
5.4.21
executionContext=node
41 FAIL
· stage: PROCESS_START
· fingerprint: sha256:c12549970456efb5abdc90b679695c6689107d4f097d612245d6bfb25e01ec32
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| esbuild | 0.21.5 | CANDIDATE Correlated change; unproven combination | contract passed | 35 project-days |
| postcss | 8.5.25 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| postcss | 8.5.26 | CANDIDATE Correlated change; unproven combination | contract passed | 8 project-days |
| postcss | 8.5.28 | CANDIDATE Correlated change; unproven combination | contract passed | 24 project-days |
| rollup | 4.62.3 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| rollup | 4.63.0 | CANDIDATE Correlated change; unproven combination | contract passed | 4 project-days |
| rollup | 4.63.1 | CANDIDATE Correlated change; unproven combination | contract passed | 17 project-days |
| rollup | 4.63.3 | CANDIDATE Correlated change; unproven combination | contract passed | 9 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 | 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.