CodeSampleX

Recordsnpmjest-resolve30.4.1

Change the conditions
Fixed
Runtimenode 22 Package version30.4.1 Architecturex64
Filter OSubuntu glibc Symbolwhole package Package managernpm 10 Execution contextnode libcglibc Clear filters

Current conditions

jest-resolve @30.4.1ubuntu glibc · x64 · node 22 · npm 10 · node

package-level total, not an API

0 of 2 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
4 / 4
Contract verifications
0 / 2
Independent reporting peers
1
Last recorded
2026-08-31
Evidence you can open

Dependencies

LibraryVersionMeasured thereProjects
chalk 4.1.2 contract passed 2 project-days
graceful-fs 4.2.11 contract passed 2 project-days
jest-haste-map 30.4.1 contract passed 2 project-days
jest-pnp-resolver 1.2.3 contract passed 2 project-days
jest-util 30.4.1 contract passed 2 project-days
jest-validate 30.4.1 contract passed 2 project-days
slash 3.0.0 contract passed 2 project-days
unrs-resolver 1.12.2 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-haste-map 30.4.1 29.7.0
jest-util 30.4.1 29.7.0
jest-validate 30.4.1 29.7.0
chalk 4.1.2 4.1.2
graceful-fs 4.2.11 4.2.11
jest-pnp-resolver 1.2.3 1.2.3
resolve — 1.22.12
resolve.exports — 2.0.3
slash 3.0.0 3.0.0
unrs-resolver 1.12.2 —

Moved: 3 · unchanged at every release: 7

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