CodeSampleX

Recordsnpmenhanced-resolve5.24.5enhanced-resolve.create

Change the conditions
Fixed
Symbolenhanced-resolve.create Package managernpm 10
Filter OSubuntu glibc Runtimenode 22 Package version5.24.5 Architecturex64 Execution contextnode libcglibc Clear filters

Current conditions

enhanced-resolve.create @5.24.5ubuntu glibc · x64 · node 22 · npm 10 · node

4 of 4 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
4 / 4
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-10-09

Dependency Health

Observed combinations and failure evidence for this release

Changed 1 · Steady 1

Dependency changes observed: 1. No failure evidence is linked to these resolved trees yet.

Library Version Health Measured there Projects
tapable 2.3.3 CHANGED Version changed, no linked failure contract passed 8 project-days
graceful-fs 4.2.11 PASS All observations passed contract passed 8 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.

Library5.25.15.24.55.18.4
tapable 2.3.3 2.3.3 2.3.0
graceful-fs 4.2.11 4.2.11 4.2.11

Moved: 1 · unchanged at every release: 1

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.