Recordsnpmpretty-format29.7.0
Change the conditions
Current conditions
pretty-format @29.7.0windows 11 · x64 · node 24 · npm 11 · node
package-level total, not an API
1 of 1 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 (7)
- Project observations
- 1 / 1
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Last recorded
- 2026-08-18
Dependency Health
Observed combinations and failure evidence for this release
First observed break
29.7.0
linux · node@22.23 · executionContext=node
7 FAIL · stage: PROJECT_PROCESS
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @jest/schemas | 29.6.3 | CANDIDATE Correlated change; unproven combination | contract passed | 32 project-days |
| react-is | 18.3.1 | CANDIDATE Correlated change; unproven combination | contract passed | 32 project-days |
| ansi-styles | 5.2.0 | PASS All observations passed | contract passed | 30 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.
| Library | 30.4.1 | 29.7.0 | 27.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.