Recordsnpmvitest
Compatibility cube
Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.
| vitest | BaseSequencer | JsonReporter | ReportersMap | builtinEnvironments | vi | vitest.afterAll | vitest.afterEach | |
|---|---|---|---|---|---|---|---|---|
| ubuntu glibc | 100%17 | 100%1 | 100%1 | 100%1 | 100%1 | 100%3 | 100%2 | 100%4 |
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.
Dependencies
| Library | Version | Measured there | Projects |
|---|---|---|---|
| @vitest/expect | 2.1.9 | contract passed | 4 project-days |
| @vitest/mocker | 2.1.9 | contract passed | 4 project-days |
| @vitest/pretty-format | 2.1.9 | contract passed | 4 project-days |
| @vitest/runner | 2.1.9 | contract passed | 4 project-days |
| @vitest/snapshot | 2.1.9 | contract passed | 4 project-days |
| @vitest/spy | 2.1.9 | contract passed | 4 project-days |
| @vitest/utils | 2.1.9 | contract passed | 4 project-days |
| chai | 5.3.3 | contract passed | 4 project-days |
| debug | 4.4.3 | contract passed | 4 project-days |
| expect-type | 1.4.0 | contract passed | 4 project-days |
| magic-string | 0.30.21 | contract passed | 4 project-days |
| pathe | 1.1.2 | contract passed | 4 project-days |
| std-env | 3.10.0 | contract passed | 3 project-days |
| tinybench | 2.9.0 | contract passed | 3 project-days |
| tinyexec | 0.3.2 | contract passed | 3 project-days |
| tinypool | 1.1.1 | contract passed | 3 project-days |
| tinyrainbow | 1.2.0 | contract passed | 3 project-days |
| vite | 5.4.21 | contract passed | 3 project-days |
| vite-node | 2.1.9 | contract passed | 3 project-days |
| why-is-node-running | 2.3.0 | contract passed | 3 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.