CodeSampleX

Recordsnpmexpect29.7.0expect.extend

Change the conditions
Fixed
OSalpine musl Symbolexpect.extend Package managernpm
Filter Runtimenode 22 Package version29.7.0 Architecturex64 Execution contextnode libcmusl Clear filters

Current conditions

expect.extend @29.7.0alpine musl · x64 · node 22 · npm · node

1 of 1 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate came back clean (1)

Project observations
nothing at this coordinate
Contract verifications
1 / 1
Last recorded
2026-08-26

Dependencies

LibraryVersionMeasured thereProjects
@jest/expect-utils 29.7.0 contract passed 11 project-days
jest-get-type 29.6.3 contract passed 10 project-days
jest-matcher-utils 29.7.0 contract passed 8 project-days
jest-message-util 29.7.0 contract passed 10 project-days
jest-util 29.7.0 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/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