CodeSampleX

Recordsnpmjest-validate30.4.1jest-validate.logValidationWarning

Change the conditions
Fixed
Package version30.4.1 Symboljest-validate.logValidationWarning
Filter OSubuntu glibc Runtimenode 22 Architecturex64 Package managernpm 10 Execution contextnode libcglibc Clear filters

Current conditions

jest-validate.logValidationWarning @30.4.1ubuntu glibc · x64 · node 22 · npm 10 · node

1 of 1 passed

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

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

Dependencies

LibraryVersionMeasured thereProjects
@jest/get-type 30.1.0 contract passed 2 project-days
@jest/types 30.4.1 contract passed 2 project-days
camelcase 6.3.0 contract passed 2 project-days
chalk 4.1.2 contract passed 2 project-days
leven 3.1.0 contract passed 2 project-days
pretty-format 30.4.1 contract passed 2 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.

Library30.4.129.7.0
@jest/types 30.4.1 29.6.3
pretty-format 30.4.1 29.7.0
@jest/get-type 30.1.0
camelcase 6.3.0 6.3.0
chalk 4.1.2 4.1.2
jest-get-type 29.6.3
leven 3.1.0 3.1.0

Moved: 2 · unchanged at every release: 5

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