CodeSampleX

Recordsnpmpretty-format27.5.1

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

Current conditions

pretty-format @27.5.1windows 11 · x64 · node 24 · npm 11 · node

package-level total, not an API

0 of 11 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate failed (4)

Project observations
25 / 28
Contract verifications
0 / 11
Usage records
47
Independent reporting peers
1
Failures with a captured fingerprint
1 / 3
Last recorded
2026-09-16
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 2

First observed break

27.5.1

linux · node@22.23 · executionContext=node

7 FAIL · stage: PROJECT_PROCESS

View exact conditions View failure cluster
Library Version Health Measured there Projects
react-is 17.0.2 CANDIDATE Correlated change; unproven combination contract passed 15 project-days
ansi-regex 5.0.1 PASS All observations passed contract passed 16 project-days
ansi-styles 5.2.0 PASS All observations passed contract passed 17 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.

Library30.4.129.7.027.5.1
@jest/schemas 30.4.1 29.6.3 —
react-is 19.2.8 18.3.1 17.0.2
ansi-regex — — 5.0.1
ansi-styles 5.2.0 5.2.0 5.2.0

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