CodeSampleX

Recordsnpm@jest/source-map29.6.3

Change the conditions
Fixed
Runtimenode 24 Architecturex64
Filter OSwindows 11 Package version29.6.3 Symbolwhole package Package managernpm 11 Execution contextnode Clear filters

Current conditions

@jest/source-map @29.6.3windows 11 · x64 · node 24 · npm 11 · node

package-level total, not an API

1 of 1 passed

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

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

Dependencies

LibraryVersionMeasured thereProjects
@jridgewell/trace-mapping 0.3.31 contract passed 5 project-days
callsites 3.1.0 contract passed 4 project-days
graceful-fs 4.2.11 contract passed 5 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.0.129.6.3
@jridgewell/trace-mapping 0.3.31 0.3.31
callsites 3.1.0 3.1.0
graceful-fs 4.2.11 4.2.11

Moved: 0 · 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.