Compatibilitynpmjest-config29.7.0
Change the conditions
Current conditions
jest-config @29.7.0windows 11 · x64 · node 24 · npm 11 · node
package-level total, not an API
1 of 1 passed
Observed — real project builds reported from this coordinate.
there is a sample here, and nothing of ours has run it at this coordinate yet (1)
- Project observations
- 1 / 1
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Last recorded
- 2026-08-17
Dependencies
| Library | Version | Measured there | Projects |
|---|---|---|---|
| @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.
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.2 | 29.7.0 |
|---|---|---|
| @jest/test-sequencer | 30.4.1 | 29.7.0 |
| @jest/types | 30.4.1 | 29.6.3 |
| babel-jest | 30.4.1 | 29.7.0 |
| ci-info | 4.4.0 | 3.9.0 |
| glob | 10.5.0 | 7.2.3 |
| jest-circus | 30.4.2 | 29.7.0 |
| jest-environment-node | 30.4.1 | 29.7.0 |
| jest-regex-util | 30.4.0 | 29.6.3 |
| jest-resolve | 30.4.1 | 29.7.0 |
| jest-runner | 30.4.2 | 29.7.0 |
| jest-util | 30.4.1 | 29.7.0 |
| jest-validate | 30.4.1 | 29.7.0 |
| pretty-format | 30.4.1 | 29.7.0 |
| @babel/core | 7.29.7 | 7.29.7 |
| @jest/get-type | 30.1.0 | — |
| @jest/pattern | 30.4.0 | — |
| chalk | 4.1.2 | 4.1.2 |
| deepmerge | 4.3.1 | 4.3.1 |
| graceful-fs | 4.2.11 | 4.2.11 |
| jest-docblock | 30.4.0 | — |
| jest-get-type | — | 29.6.3 |
| micromatch | — | 4.0.8 |
| parse-json | 5.2.0 | 5.2.0 |
| slash | 3.0.0 | 3.0.0 |
| strip-json-comments | 3.1.1 | 3.1.1 |
Moved: 13 · unchanged at every release: 12
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.