CodeSampleX

Recordsnpm@vitest/pretty-format4.1.10

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

Current conditions

@vitest/pretty-format @4.1.10windows 11 · x64 · node 24 · npm 11 · node

package-level total, not an API

0 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 (2)

Project observations
0 / 1
Contract verifications
nothing at this coordinate
Usage records
2
Independent reporting peers
1
Failures with a captured fingerprint
0 / 1
Last recorded
2026-08-14
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 0

First observed break

4.1.10

linux · node@22.23 · executionContext=node

10 FAIL · stage: UNKNOWN · fingerprint: sha256:986d98189e70ab6bb81e3ca5f5feb96281ba0dfa6e522caa6ddd3d9b148578cc

View exact conditions View failure cluster
Library Version Health Measured there Projects
tinyrainbow 3.1.1 CANDIDATE Correlated change; unproven combination contract passed 60 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