CodeSampleX

Recordsnpm@vitest/utils4.1.11@vitest/utils.cleanUrl

Change the conditions
Fixed
Package version4.1.11 Symbol@vitest/utils.cleanUrl Architecturex64
Filter OSubuntu glibc Runtimenode 22 Package managernpm 10 Execution contextnode libcglibc Clear filters

Current conditions

@vitest/utils.cleanUrl @4.1.11ubuntu glibc · x64 · node 22 · npm 10 · node

1 of 2 passed

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
1 / 2
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-08-31

Dependencies

LibraryVersionMeasured thereProjects
@vitest/pretty-format 4.1.11 contract passed 2 project-days
convert-source-map 2.0.0 contract passed 2 project-days
tinyrainbow 3.1.1 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.

Library4.1.114.1.103.2.72.1.9
@vitest/pretty-format 4.1.11 4.1.10 3.2.7 2.1.9
tinyrainbow 3.1.1 3.1.1 2.0.0 1.2.0
convert-source-map 2.0.0 2.0.0
loupe 3.2.1 3.2.1

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