Recordsnpmvite
Compatibility cube
Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.
| vite | expect.rejects shared ×2 | expect.toEqual shared ×2 | expect.toStrictEqual shared ×2 | expect.toThrow shared ×2 | startVitest shared ×2 | vi.advanceTimersByTime shared ×2 | vi.advanceTimersByTimeAsync shared ×2 | |
|---|---|---|---|---|---|---|---|---|
| alpine musl | 100%4 | 100%1 | 100%1 | 100%1 | 100%1 | 100%1 | 100%1 | 100%1 |
Showing the environments with the most evidence. The cube reads the newest 6 versions and the first 10 symbols of each, so an empty cell here can mean "outside that window" rather than "never measured".
How to read the grid
Reading a cell: The number is how many recorded observations the rate divides — one build files an observation per stage it reached, so it counts neither builds nor machines nor people. The document beside it is a different fact from a different source: whether a sample exists at that coordinate, and how our own run of it went there.
- no sample at this coordinate yet
- there is a sample here, and nothing of ours has run it at this coordinate yet
- there is a sample here, and our run of it at this coordinate came back clean
- there is a sample here, and our run of it at this coordinate failed
- there is a sample here, and this coordinate records both a passing and a failing run of it
- nothing recorded — unknown, never "works" and never "broken"
- there is a level below this cell — click to open it
A document means there is a sample at that coordinate. Whether one EXISTS is a fact about this release and this API and does not change with OS, runtime or package manager; its COLOUR is how that sample ran in the environment you are looking at.
Cells are aggregates of everything still varying in this slice (the n/m count says how much). Click one to pin its coordinates and see the next level.
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.