CodeSampleX

Recordsnpmstring-width4.2.3

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

Current conditions

string-width @4.2.3windows 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 (1)

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

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 1

First observed break

4.2.3

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

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

View exact conditions View failure cluster
Library Version Health Measured there Projects
emoji-regex 8.0.0 CANDIDATE Correlated change; unproven combination contract passed 71 project-days
strip-ansi 6.0.1 CANDIDATE Correlated change; unproven combination contract passed 76 project-days
is-fullwidth-code-point 3.0.0 PASS All observations passed contract passed 68 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.

Library8.2.27.2.05.1.24.2.3
emoji-regex — 10.6.0 9.2.2 8.0.0
strip-ansi 7.2.0 7.2.0 7.1.2 6.0.1
eastasianwidth — — 0.2.0 —
get-east-asian-width 1.6.0 1.6.0 — —
is-fullwidth-code-point — — — 3.0.0

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