CodeSampleX

Recordsnpmexpect30.4.1

Change the conditions
Fixed
OSdebian glibc Runtimenode 22 Symbolwhole package
Filter Package version30.4.1 Architecturex64 Package managernpm Execution contextnode libcglibc Clear filters

Current conditions

expect @30.4.1debian glibc · x64 · node 22 · npm · node

package-level total, not an API

Recorded as present in projects. Nothing was run at this coordinate.

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
1
Independent reporting peers
1
Last recorded
2026-09-01
Evidence you can open

Dependency Health

Observed problems 6 · Steady 0

First observed break

30.4.1 @jest/expect-utils@30.4.1

linux · node@22.23 · moduleSystem=esm · executionContext=node

1 FAIL · stage: UNKNOWN · fingerprint: sha256:054c93088b95acdec26c27553355ea7447db339349572fdd4ba431478ecb744a

View exact conditions View failure cluster
Library Version Health Measured there Projects
@jest/expect-utils 30.4.1 FAIL Linked failure observed; version changed across releases contract passed 9 project-days
@jest/get-type 30.1.0 FAIL Linked failure observed on this release contract passed 9 project-days
jest-matcher-utils 30.4.1 FAIL Linked failure observed; version changed across releases contract passed 7 project-days
jest-message-util 30.4.1 FAIL Linked failure observed; version changed across releases contract passed 9 project-days
jest-mock 30.4.1 FAIL Linked failure observed on this release contract passed 9 project-days
jest-util 30.4.1 FAIL Linked failure observed; version changed across releases contract passed 9 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/expect-utils 30.4.1 29.7.0
jest-matcher-utils 30.4.1 29.7.0
jest-message-util 30.4.1 29.7.0
jest-util 30.4.1 29.7.0
@jest/get-type 30.1.0 —
jest-get-type — 29.6.3
jest-mock 30.4.1 —

Moved: 4 · unchanged at every release: 3

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