Recordsnpmexpect
Compatibility cube
Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.
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
First observed break
30.4.1 @jest/expect-utils@30.4.1
linux · node@22.23 · moduleSystem=esm · executionContext=node
1 FAIL
· stage: UNKNOWN
· fingerprint: sha256:054c93088b95acdec26c27553355ea7447db339349572fdd4ba431478ecb744a
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @jest/expect-utils | 30.4.1 | FAIL Linked failure observed; version changed across releases | contract passed | 9 project-days |
| @jest/get-type | 30.1.0 | FAIL Linked failure observed on this release | contract passed | 9 project-days |
| jest-matcher-utils | 30.4.1 | FAIL Linked failure observed; version changed across releases | contract passed | 7 project-days |
| jest-message-util | 30.4.1 | FAIL Linked failure observed; version changed across releases | contract passed | 9 project-days |
| jest-mock | 30.4.1 | FAIL Linked failure observed on this release | contract passed | 9 project-days |
| jest-util | 30.4.1 | FAIL Linked failure observed; version changed across releases | 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 | 30.4.1 | 29.7.0 |
|---|---|---|
| @jest/expect-utils | 30.4.1 | 29.7.0 |
| jest-matcher-utils | 30.4.1 | 29.7.0 |
| jest-message-util | 30.4.1 | 29.7.0 |
| jest-util | 30.4.1 | 29.7.0 |
| @jest/get-type | 30.1.0 | — |
| jest-get-type | — | 29.6.3 |
| jest-mock | 30.4.1 | — |
Moved: 4 · 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.