Recordsnpmmagic-string
Change the conditions
Current conditions
magic-string @0.30.21ubuntu glibc · x64 · node 22 · npm 10 · node
0 of 76 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate failed (1)
- Project observations
- 185 / 194
- Contract verifications
- 0 / 76
- Usage records
- 110
- Independent reporting peers
- 3
- Failures with a captured fingerprint
- 2 / 9
- Last recorded
- 2026-09-17
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
0 of 76 passed
Verified — this network ran a contract at this coordinate.
-
magic-string.Bundle
0 of 30 passed
Verified — this network ran a contract at this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
0.30.21
windows · node@24.13 · moduleSystem=esm · executionContext=node
32 FAIL
· stage: UNKNOWN
· fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10
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.
| Library | 0.30.21 | 0.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.