CodeSampleX

Recordsnpmansi-escapes4.3.2

Change the conditions
Fixed
Runtimenode 24 Architecturex64
Filter OSwindows 11 Package version4.3.2 Symbolwhole package Package managernpm 11 Execution contextnode Clear filters

Current conditions

ansi-escapes @4.3.2windows 11 · x64 · node 24 · npm 11 · node

package-level total, not an API

3 of 6 passed

Observed — real project builds reported from this coordinate.

there is a sample here, and nothing of ours has run it at this coordinate yet (2)

Project observations
3 / 6
Contract verifications
nothing at this coordinate
Usage records
1
Independent reporting peers
1
Failures with a captured fingerprint
0 / 3
Last recorded
2026-08-17
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 1

First observed break

4.3.2

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

3 FAIL · stage: PROJECT_TEST

View exact conditions View failure cluster
Library Version Health Measured there Projects
type-fest 0.21.3 PASS All observations passed contract passed 36 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.

Library7.3.04.3.2
environment 1.1.0 —
type-fest — 0.21.3

Moved: 0 · unchanged at every release: 2

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