Compatibilitynpmjest-haste-map
there is a sample for this release and API (1)
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 |
|---|---|---|---|
| @jest/types | 29.6.3 | contract passed | 8 project-days |
| @types/graceful-fs | 4.1.9 | contract passed | 5 project-days |
| @types/node | 26.2.0 | contract passed | 1 project-day |
| @types/node | 26.3.0 | contract passed | 2 project-days |
| @types/node | 26.4.0 | contract passed | 3 project-days |
| anymatch | 3.1.3 | contract passed | 5 project-days |
| fb-watchman | 2.0.2 | contract passed | 5 project-days |
| graceful-fs | 4.2.11 | contract passed | 8 project-days |
| jest-regex-util | 29.6.3 | contract passed | 8 project-days |
| jest-util | 29.7.0 | contract passed | 8 project-days |
| jest-worker | 29.7.0 | contract passed | 5 project-days |
| micromatch | 4.0.8 | contract passed | 7 project-days |
| walker | 1.0.8 | contract passed | 5 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/types | 30.4.1 | 29.6.3 |
| @types/node | 26.4.0 | 26.2.0 |
| jest-regex-util | 30.4.0 | 29.6.3 |
| jest-util | 30.4.1 | 29.7.0 |
| jest-worker | 30.4.1 | 29.7.0 |
| @types/graceful-fs | — | 4.1.9 |
| anymatch | 3.1.3 | 3.1.3 |
| fb-watchman | 2.0.2 | 2.0.2 |
| graceful-fs | 4.2.11 | 4.2.11 |
| micromatch | — | 4.0.8 |
| picomatch | 4.0.7 | — |
| walker | 1.0.8 | 1.0.8 |
Moved: 5 · 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.