CodeSampleX

Recordsnpmhttp-errors2.0.0createError

Change the conditions
Fixed
SymbolcreateError Execution contextnode
Filter OSalpine musl Runtimenode 22 Package version2.0.0 Architecturex64 Package managernpm libcmusl Clear filters

Current conditions

createError @2.0.0alpine musl · x64 · node 22 · npm · node

1 of 1 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate came back clean (1)

Project observations
nothing at this coordinate
Contract verifications
1 / 1
Last recorded
2026-08-30

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 4

First observed break

2.0.0

executionContext=node

16 FAIL · stage: PROJECT_PROCESS

Library Version Health Measured there Projects
statuses 2.0.1 CANDIDATE Correlated change; unproven combination contract passed 23 project-days
depd 2.0.0 PASS All observations passed contract passed 25 project-days
inherits 2.0.4 PASS All observations passed contract passed 24 project-days
setprototypeof 1.2.0 PASS All observations passed contract passed 23 project-days
toidentifier 1.0.1 PASS All observations passed contract passed 22 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.

Moved: 1 · unchanged at every release: 4

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