CodeSampleX

Recordsnpm@vitest/pretty-format2.1.9@vitest/pretty-format.format

Change the conditions
Fixed
Package version2.1.9 Symbol@vitest/pretty-format.format Execution contextnode
Filter OSubuntu glibc Runtimenode 22 Architecturex64 Package managernpm 10 libcglibc Clear filters

Current conditions

@vitest/pretty-format.format @2.1.9ubuntu glibc · x64 · node 22 · npm 10 · node

0 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 failed (1)

Project observations
1 / 1
Contract verifications
0 / 1
Independent reporting peers
1
Last recorded
2026-08-29

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 0

First observed break

2.1.9

executionContext=node

21 FAIL · stage: PROCESS_START · fingerprint: sha256:c12549970456efb5abdc90b679695c6689107d4f097d612245d6bfb25e01ec32

Library Version Health Measured there Projects
tinyrainbow 1.2.0 CANDIDATE Correlated change; unproven combination contract passed 44 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.

Library4.1.114.1.104.0.184.0.164.0.03.2.73.2.43.0.02.1.9
tinyrainbow 3.1.1 3.1.1 3.1.1 3.0.3 3.1.1 2.0.0 2.0.0 2.0.0 1.2.0

Moved: 1 · unchanged at every release: 0

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

Showing the 12 most-reported of 18 recorded failure clusters. The rest are single reports.