CodeSampleX

Recordsnpm@vitest/expect4.1.11@vitest/expect.ObjectContaining

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

Current conditions

@vitest/expect.ObjectContaining @4.1.11ubuntu 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

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

Dependencies

LibraryVersionMeasured thereProjects
@standard-schema/spec 1.1.0 builds observed 3 project-days
@types/chai 5.2.3 contract passed 3 project-days
@vitest/spy 4.1.11 contract passed 3 project-days
@vitest/utils 4.1.11 contract passed 3 project-days
chai 6.2.2 contract passed 3 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.113.2.72.1.9
@vitest/spy 4.1.11 3.2.7 2.1.9
@vitest/utils 4.1.11 3.2.7 2.1.9
chai 6.2.2 5.3.3 5.3.3
tinyrainbow 3.1.1 2.0.0 1.2.0
@standard-schema/spec 1.1.0
@types/chai 5.2.3 5.2.3

Moved: 4 · 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