Recordsnpm@jest/reporters
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.
Dependencies
| Library | Version | Measured there | Projects |
|---|---|---|---|
| @bcoe/v8-coverage | 0.2.3 | contract passed | 3 project-days |
| @jest/console | 29.7.0 | contract passed | 5 project-days |
| @jest/test-result | 29.7.0 | contract passed | 4 project-days |
| @jest/transform | 29.7.0 | contract passed | 4 project-days |
| @jest/types | 29.6.3 | contract passed | 5 project-days |
| @jridgewell/trace-mapping | 0.3.31 | contract passed | 3 project-days |
| @types/node | 26.2.0 | contract passed | 1 project-day |
| @types/node | 26.4.0 | contract passed | 4 project-days |
| chalk | 4.1.2 | contract passed | 5 project-days |
| collect-v8-coverage | 1.0.3 | contract passed | 3 project-days |
| exit | 0.1.2 | contract passed | 3 project-days |
| glob | 7.2.3 | contract passed | 2 project-days |
| graceful-fs | 4.2.11 | contract passed | 3 project-days |
| istanbul-lib-coverage | 3.2.2 | contract passed | 2 project-days |
| istanbul-lib-instrument | 6.0.3 | contract passed | 2 project-days |
| istanbul-lib-report | 3.0.1 | contract passed | 2 project-days |
| istanbul-lib-source-maps | 4.0.1 | contract passed | 2 project-days |
| istanbul-reports | 3.2.0 | contract passed | 2 project-days |
| jest-message-util | 29.7.0 | contract passed | 5 project-days |
| jest-util | 29.7.0 | contract passed | 5 project-days |
| jest-worker | 29.7.0 | contract passed | 2 project-days |
| slash | 3.0.0 | contract passed | 4 project-days |
| string-length | 4.0.2 | contract passed | 2 project-days |
| strip-ansi | 6.0.1 | contract passed | 2 project-days |
| v8-to-istanbul | 9.3.0 | contract passed | 2 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/console | 30.4.1 | 29.7.0 |
| @jest/test-result | 30.4.1 | 29.7.0 |
| @jest/transform | 30.4.1 | 29.7.0 |
| @jest/types | 30.4.1 | 29.6.3 |
| @types/node | 26.4.0 | 26.2.0 |
| glob | 10.5.0 | 7.2.3 |
| istanbul-lib-source-maps | 5.0.6 | 4.0.1 |
| jest-message-util | 30.4.1 | 29.7.0 |
| jest-util | 30.4.1 | 29.7.0 |
| jest-worker | 30.4.1 | 29.7.0 |
| @bcoe/v8-coverage | 0.2.3 | 0.2.3 |
| @jridgewell/trace-mapping | 0.3.31 | 0.3.31 |
| chalk | 4.1.2 | 4.1.2 |
| collect-v8-coverage | 1.0.3 | 1.0.3 |
| exit | — | 0.1.2 |
| exit-x | 0.2.2 | — |
| graceful-fs | 4.2.11 | 4.2.11 |
| istanbul-lib-coverage | 3.2.2 | 3.2.2 |
| istanbul-lib-instrument | 6.0.3 | 6.0.3 |
| istanbul-lib-report | 3.0.1 | 3.0.1 |
| istanbul-reports | 3.2.0 | 3.2.0 |
| slash | 3.0.0 | 3.0.0 |
| string-length | 4.0.2 | 4.0.2 |
| strip-ansi | — | 6.0.1 |
| v8-to-istanbul | 9.3.0 | 9.3.0 |
Moved: 10 · unchanged at every release: 15
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.