CodeSampleX

Recordsnpmp-limit7.3.1

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

Current conditions

p-limit @7.3.1windows 11 · x64 · node 24 · npm 11 · node

package-level total, not an API

2 of 5 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 (3)

Project observations
2 / 5
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Failures with a captured fingerprint
0 / 3
Last recorded
2026-08-13
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 1

First observed break

7.3.1

executionContext=node · moduleSystem=cjs

14 FAIL · stage: PROJECT_PROCESS

View exact conditions View failure cluster
Library Version Health Measured there Projects
yocto-queue 1.2.2 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
yoga-layout 3.2.1 PASS All observations passed contract passed 1 project-day

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.

Library7.3.13.1.02.3.01.3.0
p-try — — 2.2.0 1.0.0
yocto-queue 1.2.2 0.1.0 — —
yoga-layout 3.2.1 — — —

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

Recent failure clusters