CodeSampleX

Recordsnpmpretty-format30.4.1

Change the conditions
Fixed
Package version30.4.1 Architecturex64
Filter OSubuntu glibc Runtimenode 22 Symbolwhole package Package managernpm 10 Execution contextnode libcglibc Clear filters

Current conditions

pretty-format @30.4.1ubuntu glibc · x64 · node 22 · npm 10 · node

package-level total, not an API

0 of 4 passed

Verified — this network ran a contract at this coordinate.

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

Project observations
20 / 20
Contract verifications
0 / 4
Usage records
5
Independent reporting peers
2
Last recorded
2026-08-31

Dependencies

LibraryVersionMeasured thereProjects
@jest/schemas 30.4.1 contract passed 3 project-days
ansi-styles 5.2.0 contract passed 3 project-days
react-is 18.3.1 contract passed 3 project-days
react-is 19.2.8 contract passed 3 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