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 | vitest.afterEach | vitest.beforeEach | vitest.defineConfig | vitest.describe | vitest.expect | vitest.it | vitest.vi | |
|---|---|---|---|---|---|---|---|---|
| 11 | 29%66 | 29%66 | 29%66 | 29%66 | 29%66 | 29%66 | 29%66 | 29%66 |
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
4.0.16 @vitest/expect@4.0.16
windows · node@24.13 · moduleSystem=cjs · executionContext=node
4 FAIL
· stage: PROJECT_COMPILE
· fingerprint: sha256:0470f88d95bb52932e5704cdc30cfcecbd43ae71af54d4c5f93d16aa27317cd2
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @vitest/expect | 4.0.16 | FAIL Linked failure observed; version changed across releases | contract passed | 1 project-day |
| @vitest/mocker | 4.0.16 | FAIL Linked failure observed; version changed across releases | contract passed | 1 project-day |
| @vitest/pretty-format | 4.0.16 | FAIL Linked failure observed; version changed across releases | contract passed | 1 project-day |
| @vitest/runner | 4.0.16 | FAIL Linked failure observed; version changed across releases | contract passed | 1 project-day |
| @vitest/snapshot | 4.0.16 | FAIL Linked failure observed; version changed across releases | contract passed | 1 project-day |
| @vitest/spy | 4.0.16 | FAIL Linked failure observed; version changed across releases | contract passed | 1 project-day |
| @vitest/utils | 4.0.16 | FAIL Linked failure observed; version changed across releases | contract passed | 1 project-day |
| es-module-lexer | 1.7.0 | FAIL Linked failure observed; version changed across releases | contract passed | 1 project-day |
| expect-type | 1.3.0 | FAIL Linked failure observed; version changed across releases | contract passed | 1 project-day |
| magic-string | 0.30.21 | FAIL Linked failure observed on this release | contract passed | 1 project-day |
| obug | 2.1.1 | FAIL Linked failure observed; version changed across releases | contract passed | 1 project-day |
| pathe | 2.0.3 | FAIL Linked failure observed; version changed across releases | contract passed | 1 project-day |
| picomatch | 4.0.3 | FAIL Linked failure observed; version changed across releases | contract passed | 1 project-day |
| std-env | 3.10.0 | FAIL Linked failure observed; version changed across releases | contract passed | 1 project-day |
| tinybench | 2.9.0 | FAIL Linked failure observed on this release | contract passed | 1 project-day |
| tinyexec | 1.0.2 | FAIL Linked failure observed; version changed across releases | contract passed | 1 project-day |
| tinyglobby | 0.2.15 | FAIL Linked failure observed; version changed across releases | contract passed | 1 project-day |
| tinyrainbow | 3.0.3 | FAIL Linked failure observed; version changed across releases | contract passed | 1 project-day |
| vite | 7.3.1 | FAIL Linked failure observed; version changed across releases | contract passed | 1 project-day |
| why-is-node-running | 2.3.0 | FAIL Linked failure observed on this release | 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.
Moved: 18 · unchanged at every release: 7
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.