Recordsnpm@jest/fake-timers
Change the conditions
Current conditions
LegacyFakeTimers @29.7.0x64 · node 22 · node
2 of 3 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and this coordinate records both a passing and a failing run of it (2)
- Project observations
- 3 / 3
- Contract verifications
- 2 / 3
- Independent reporting peers
- 1
- Last recorded
- 2026-08-31
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
alpine musl · x64 · node 22 · npm · node
2 of 2 passed
Verified — this network ran a contract at this coordinate.
-
ubuntu glibc · x64 · node 22 · npm 10 · node
0 of 1 passed
Verified — this network ran a contract at this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
30.4.1
windows · node@24.13 · executionContext=node · moduleSystem=esm
3 FAIL · stage: PROJECT_TEST
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.