Recordsnpm@jest/test-sequencer29.7.0
Change the conditions
Current conditions
@jest/test-sequencer @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.
no sample at this coordinate yet
- Project observations
- 1 / 1
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Last recorded
- 2026-08-18
Dependencies
| Library | Version | Measured there | Projects |
|---|---|---|---|
| @jest/test-result | 29.7.0 | contract passed | 5 project-days |
| graceful-fs | 4.2.11 | contract passed | 5 project-days |
| jest-haste-map | 29.7.0 | contract passed | 5 project-days |
| slash | 3.0.0 | contract passed | 5 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.1 | 29.7.0 |
|---|---|---|
| @jest/test-result | 30.4.1 | 29.7.0 |
| jest-haste-map | 30.4.1 | 29.7.0 |
| graceful-fs | 4.2.11 | 4.2.11 |
| slash | 3.0.0 | 3.0.0 |
Moved: 2 · unchanged at every release: 2
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.