CodeSampleX

Recordsnpmmagic-string0.30.21MagicString.prototype.appendLeft

Change the conditions
Fixed
Runtimenode 22 SymbolMagicString.prototype.appendLeft
Filter OSalpine musl Package version0.30.21 Architecturex64 Package managernpm Execution contextnode libcmusl Clear filters

Current conditions

MagicString.prototype.appendLeft @0.30.21alpine 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-27

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 2

First observed break

0.30.21

windows · node@24.13 · moduleSystem=esm · executionContext=node

32 FAIL · stage: UNKNOWN · fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10

Library Version Health Measured there Projects
@jridgewell/sourcemap-codec 1.5.5 PASS All observations passed contract passed 26 project-days
@jridgewell/sourcemap-codec 1.6.0 PASS All observations passed contract passed 85 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.

Library0.30.210.30.8
@jridgewell/sourcemap-codec 1.5.5 1.5.5

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

Showing the 12 most-reported of 43 recorded failure clusters. The rest are single reports.