CodeSampleX

Recordsnpmp-limit3.1.0

Change the conditions
Fixed
Runtimenode (version not recorded)
Filter OSwindows 11 Package version3.1.0 Symbolwhole package Architecturex64 Package managerpnpm 10 Execution contextnode Clear filters

Current conditions

p-limit @3.1.0windows 11 · x64 · node (version not recorded) · pnpm 10 · node

package-level total, not an API

Recorded as present in projects. Nothing was run at this coordinate.

Observed — real project builds reported from this coordinate.

there is a sample here, and nothing of ours has run it at this coordinate yet (2)

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
1
Independent reporting peers
1
Last recorded
2026-09-01
Evidence you can open

Dependencies

LibraryVersionMeasured thereProjects
yocto-queue 0.1.0 contract passed 21 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.

Library3.1.02.3.0
p-try — 2.2.0
yocto-queue 0.1.0 —

Moved: 0 · unchanged at every release: 2

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