Recordsnpmjest-haste-map29.7.0
Change the conditions
Current conditions
jest-haste-map @29.7.0windows 11 · x64 · node 24 · npm 11 · node
package-level total, not an API
1 of 1 passed
Observed — real project builds reported from this coordinate.
there is a sample here, and nothing of ours has run it at this coordinate yet (1)
- Project observations
- 1 / 1
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Last recorded
- 2026-08-17
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.