Recordsnpmjest-validate
Change the conditions
Current conditions
jest-validate.validateCLIOptions @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
- 2 / 2
- Contract verifications
- 1 / 1
- Independent reporting peers
- 1
- Last recorded
- 2026-08-21
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
alpine musl · x64 · node 22 · npm · node
1 of 1 passed
Verified — this network ran a contract at this coordinate.
-
ubuntu glibc · x64 · node 22 · npm 10 · node
2 of 2 passed
Observed — real project builds reported from this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
30.4.1
windows · node@24.13 · moduleSystem=esm · executionContext=node
3 FAIL · stage: PROJECT_TEST
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.
| Library | 30.4.1 | 29.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.