CodeSampleX

Recordsnpmjest-config

Change the conditions
Fixed
SymbolreadConfig Architecturex64
Filter Runtimenode 22 Package version29.7.0 Execution contextnode Clear filters

Current conditions

readConfig @29.7.0x64 · node 22 · node

1 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 came back clean (1)

Project observations
1 / 1
Contract verifications
1 / 1
Independent reporting peers
1
Last recorded
2026-08-27

Exact records

This slice is down to its measured combinations — the environments below are exactly what ran.

Dependencies

LibraryVersionMeasured thereProjects
@babel/core 7.29.7 contract passed 3 project-days
@jest/test-sequencer 29.7.0 contract passed 3 project-days
@jest/types 29.6.3 contract passed 4 project-days
babel-jest 29.7.0 contract passed 3 project-days
chalk 4.1.2 contract passed 4 project-days
ci-info 3.9.0 contract passed 4 project-days
deepmerge 4.3.1 contract passed 3 project-days
glob 7.2.3 contract passed 3 project-days
graceful-fs 4.2.11 contract passed 4 project-days
jest-circus 29.7.0 contract passed 3 project-days
jest-environment-node 29.7.0 contract passed 3 project-days
jest-get-type 29.6.3 contract passed 3 project-days
jest-regex-util 29.6.3 contract passed 4 project-days
jest-resolve 29.7.0 contract passed 3 project-days
jest-runner 29.7.0 contract passed 3 project-days
jest-util 29.7.0 contract passed 4 project-days
jest-validate 29.7.0 contract passed 3 project-days
micromatch 4.0.8 contract passed 3 project-days
parse-json 5.2.0 contract passed 3 project-days
pretty-format 29.7.0 contract passed 3 project-days
slash 3.0.0 contract passed 4 project-days
strip-json-comments 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.