CodeSampleX

Recordsnpm@jest/fake-timers30.4.1

Change the conditions
Fixed
Runtimenode 24 Package version30.4.1
Filter OSwindows 11 Symbolwhole package Architecturex64 Package managernpm 11 Execution contextnode Clear filters

Current conditions

@jest/fake-timers @30.4.1windows 11 · x64 · node 24 · npm 11 · node

package-level total, not an API

1 of 4 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
1 / 4
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Failures with a captured fingerprint
0 / 3
Last recorded
2026-08-17
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 7 · Steady 0

First observed break

30.4.1

windows · node@24.13 · executionContext=node · moduleSystem=esm

3 FAIL · stage: PROJECT_TEST

View exact conditions View failure cluster
Library Version Health Measured there Projects
@jest/types 30.4.1 CANDIDATE Correlated change; unproven combination contract passed 12 project-days
@sinonjs/fake-timers 15.4.0 CANDIDATE Correlated change; unproven combination contract passed 10 project-days
@types/node 26.4.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
@types/node 26.4.1 CANDIDATE Correlated change; unproven combination contract passed 10 project-days
jest-message-util 30.4.1 CANDIDATE Correlated change; unproven combination contract passed 10 project-days
jest-mock 30.4.1 CANDIDATE Correlated change; unproven combination contract passed 12 project-days
jest-util 30.4.1 CANDIDATE Correlated change; unproven combination contract passed 10 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.

Library30.4.129.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.

Recent failure clusters