CodeSampleX

Recordsnpmjest-mock29.7.0replaceProperty

Change the conditions
Fixed
OSubuntu glibc SymbolreplaceProperty
Filter Runtimenode 22 Package version29.7.0 Architecturex64 Package managernpm 10 Execution contextnode libcglibc Clear filters

Current conditions

replaceProperty @29.7.0ubuntu glibc · x64 · node 22 · npm 10 · node

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

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

Dependencies

LibraryVersionMeasured thereProjects
@jest/types 29.6.3 contract passed 8 project-days
@types/node 26.2.0 contract passed 2 project-days
@types/node 26.3.0 contract passed 1 project-day
@types/node 26.4.0 contract passed 4 project-days
jest-util 29.7.0 contract passed 6 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
@types/node 26.4.0 26.3.0
jest-util 30.4.1 29.7.0

Moved: 3 · 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