CodeSampleX

Recordsnpmjest-watcher

Change the conditions
Fixed
Runtimenode 22 Package version30.4.1 SymbolTestWatcher
Filter Architecturex64 Execution contextnode Clear filters

Current conditions

TestWatcher @30.4.1x64 · node 22 · node

1 of 2 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 (1)

Project observations
2 / 2
Contract verifications
1 / 2
Independent reporting peers
1
Last recorded
2026-08-31
Evidence you can open

Exact records

This slice is down to its measured combinations — the environments below are exactly what ran.

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 4 · Steady 4

First observed break

30.4.1

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

3 FAIL · stage: PROJECT_TEST

View exact conditions View failure cluster
Library Version Health Measured there Projects
@jest/test-result 30.4.1 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
@jest/types 30.4.1 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
@types/node 26.4.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
jest-util 30.4.1 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
ansi-escapes 4.3.2 PASS All observations passed contract passed 2 project-days
chalk 4.1.2 PASS All observations passed contract passed 2 project-days
emittery 0.13.1 PASS All observations passed contract passed 2 project-days
string-length 4.0.2 PASS All observations passed contract passed 2 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/test-result 30.4.1 29.7.0
@jest/types 30.4.1 29.6.3
@types/node 26.4.0 26.2.0
jest-util 30.4.1 29.7.0
ansi-escapes 4.3.2 4.3.2
chalk 4.1.2 4.1.2
emittery 0.13.1 0.13.1
string-length 4.0.2 4.0.2

Moved: 4 · unchanged at every release: 4

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.