CodeSampleX

Recordsnpm@jest/expect-utils30.4.1@jest/expect-utils.arrayBufferEquality

Change the conditions
Fixed
Symbol@jest/expect-utils.arrayBufferEquality
Filter OSubuntu glibc Runtimenode 22 Package version30.4.1 Architecturex64 Package managernpm 10 Execution contextnode libcglibc Clear filters

Current conditions

@jest/expect-utils.arrayBufferEquality @30.4.1ubuntu glibc · x64 · node 22 · npm 10 · node

1 of 2 passed

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
1 / 2
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-08-31

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 1

First observed break

30.4.1

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

3 FAIL · stage: PROJECT_TEST

Library Version Health Measured there Projects
@jest/get-type 30.1.0 PASS All observations passed 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/get-type 30.1.0 —
jest-get-type — 29.6.3

Moved: 0 · unchanged at every release: 2

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