Compatibilitynpmvitest
Compatibility cube
Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.
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 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.1.11 | 3.2.7 | 2.1.9 |
|---|---|---|---|
| @vitest/expect | 4.1.11 | 3.2.7 | 2.1.9 |
| @vitest/mocker | 4.1.11 | 3.2.7 | 2.1.9 |
| @vitest/pretty-format | 4.1.11 | 3.2.7 | 2.1.9 |
| @vitest/runner | 4.1.11 | 3.2.7 | 2.1.9 |
| @vitest/snapshot | 4.1.11 | 3.2.7 | 2.1.9 |
| @vitest/spy | 4.1.11 | 3.2.7 | 2.1.9 |
| @vitest/utils | 4.1.11 | 3.2.7 | 2.1.9 |
| pathe | 2.0.3 | 2.0.3 | 1.1.2 |
| picomatch | 4.0.7 | 4.0.5 | — |
| std-env | 4.2.0 | 3.10.0 | 3.10.0 |
| tinyexec | 1.3.0 | 0.3.2 | 0.3.2 |
| tinyrainbow | 3.1.1 | 2.0.0 | 1.2.0 |
| vite | 8.2.2 | 7.3.6 | 5.4.21 |
| vite-node | — | 3.2.4 | 2.1.9 |
| @types/chai | — | 5.2.3 | — |
| chai | — | 5.3.3 | 5.3.3 |
| debug | — | 4.4.3 | 4.4.3 |
| es-module-lexer | 2.3.2 | — | — |
| expect-type | 1.4.0 | 1.4.0 | 1.4.0 |
| magic-string | 0.30.21 | 0.30.21 | 0.30.21 |
| obug | 2.1.4 | — | — |
| tinybench | 2.9.0 | 2.9.0 | 2.9.0 |
| tinyglobby | 0.2.17 | 0.2.17 | — |
| tinypool | — | 1.1.1 | 1.1.1 |
| why-is-node-running | 2.3.0 | 2.3.0 | 2.3.0 |
Moved: 14 · unchanged at every release: 11
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.