Recordsnpmpretty-format27.5.1prettyFormat
Change the conditions
Current conditions
prettyFormat @27.5.1alpine musl · x64 · node 22 · npm · node
1 of 1 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate came back clean (1)
- Project observations
- nothing at this coordinate
- Contract verifications
- 1 / 1
- Last recorded
- 2026-08-27
Dependency Health
Observed combinations and failure evidence for this release
First observed break
27.5.1
linux · node@22.23 · executionContext=node
7 FAIL · stage: PROJECT_PROCESS
| 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.
| 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.
Recent failure clusters
-
observed PROJECT_PROCESS ERR_PACKAGE_PATH_NOT_EXPORTED Evidence gap ×7 27.5.1 → 29.7.0 executionContext=node · os=linux · runtime=node@22.23Evidence quality: legacy-evidence-incomplete · Environment variants: 2 · First recorded: 2026-08-21 · Last seen: 2026-08-30Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 ERR_MODULE_NOT_FOUND Evidence gap ×2 27.5.1 → 29.7.0 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:88af852f99a8…node:internal/modules/package_json_reader:<n> · throw new ERR_MODULE_NOT_FOUND(packageName, fileURLToPath(base), null); · ^ …node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-30 · Last seen: 2026-09-12Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×1 27.5.1 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:c3c298454ef9…node:internal/modules/run_main:<n> · triggerUncaughtException( · ^ · AssertionError [ERR_ASSERTION]: DEFAULT_OPTIONS.maxDepth must be nullnode · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-05 · Last seen: 2026-09-05Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 27.5.1 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:529aac3b1da7…<url> · globalThis.navigator = dom.window.navigator; · ^ · TypeError: Cannot set property navigator of #<Object> which has only a getternode · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-12 · Last seen: 2026-09-12Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 27.5.1 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:8420f774ca6a…fil<path>:<n> · if (document[isPrepared]) { · ^ · TypeError: Cannot read properties of undefined (reading <str>)node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-12 · Last seen: 2026-09-12Diagnostic re-verification candidate