Recordsnpm@jest/fake-timers29.7.0
Change the conditions
Current conditions
@jest/fake-timers @29.7.0windows 11 · x64 · node 24 · npm 11 · node
package-level total, not an API
2 of 2 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 (3)
- Project observations
- 2 / 2
- Contract verifications
- nothing at this coordinate
- Usage records
- 1
- Independent reporting peers
- 1
- Last recorded
- 2026-08-18
Dependency Health
Observed combinations and failure evidence for this release
First observed break
29.7.0
linux · node@22.23 · executionContext=node
2 FAIL · stage: PROJECT_PROCESS
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @jest/types | 29.6.3 | CANDIDATE Correlated change; unproven combination | contract passed | 10 project-days |
| @sinonjs/fake-timers | 10.3.0 | CANDIDATE Correlated change; unproven combination | contract passed | 9 project-days |
| @types/node | 26.2.0 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| @types/node | 26.3.0 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| @types/node | 26.4.0 | CANDIDATE Correlated change; unproven combination | contract passed | 5 project-days |
| @types/node | 26.4.1 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| jest-message-util | 29.7.0 | CANDIDATE Correlated change; unproven combination | contract passed | 9 project-days |
| jest-mock | 29.7.0 | CANDIDATE Correlated change; unproven combination | contract passed | 10 project-days |
| jest-util | 29.7.0 | CANDIDATE Correlated change; unproven combination | contract passed | 8 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 |
| @sinonjs/fake-timers | 15.4.0 | 10.3.0 |
| @types/node | 26.4.0 | 26.3.0 |
| jest-message-util | 30.4.1 | 29.7.0 |
| jest-mock | 30.4.1 | 29.7.0 |
| jest-util | 30.4.1 | 29.7.0 |
Moved: 6 · unchanged at every release: 0
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.