CodeSampleX

Recordsnpmstring-width8.2.2

Change the conditions
Fixed
OSalpine musl Package version8.2.2
Filter Runtimenode 22 Symbolwhole package Architecturex64 Package managernpm Execution contextnode libcmusl Clear filters

Current conditions

string-width @8.2.2alpine musl · x64 · node 22 · npm · 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.

no sample at this coordinate yet

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
1
Independent reporting peers
1
Last recorded
2026-09-08

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 1

First observed break

8.2.2

linux · node@22.23 · moduleSystem=cjs · executionContext=node

4 FAIL · stage: UNKNOWN · fingerprint: sha256:986d98189e70ab6bb81e3ca5f5feb96281ba0dfa6e522caa6ddd3d9b148578cc

Library Version Health Measured there Projects
strip-ansi 7.2.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
get-east-asian-width 1.6.0 PASS All observations passed contract passed 2 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: 2 · unchanged at every release: 3

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