Recordsnpm@jest/transform29.7.0shouldInstrument
Change the conditions
Current conditions
shouldInstrument @29.7.0alpine musl · x64 · node 22 · npm · 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
- nothing at this coordinate
- Contract verifications
- 1 / 1
- Last recorded
- 2026-08-26
Dependencies
| Library | Version | Measured there | Projects |
|---|---|---|---|
| @babel/core | 7.29.7 | contract passed | 6 project-days |
| @jest/types | 29.6.3 | contract passed | 7 project-days |
| @jridgewell/trace-mapping | 0.3.31 | contract passed | 7 project-days |
| babel-plugin-istanbul | 6.1.1 | contract passed | 6 project-days |
| chalk | 4.1.2 | contract passed | 7 project-days |
| convert-source-map | 2.0.0 | contract passed | 6 project-days |
| fast-json-stable-stringify | 2.1.0 | contract passed | 6 project-days |
| graceful-fs | 4.2.11 | contract passed | 6 project-days |
| jest-haste-map | 29.7.0 | contract passed | 6 project-days |
| jest-regex-util | 29.6.3 | contract passed | 6 project-days |
| jest-util | 29.7.0 | contract passed | 7 project-days |
| micromatch | 4.0.8 | contract passed | 6 project-days |
| pirates | 4.0.7 | contract passed | 6 project-days |
| slash | 3.0.0 | contract passed | 6 project-days |
| write-file-atomic | 4.0.2 | 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/types | 30.4.1 | 29.6.3 |
| babel-plugin-istanbul | 7.0.1 | 6.1.1 |
| jest-haste-map | 30.4.1 | 29.7.0 |
| jest-regex-util | 30.4.0 | 29.6.3 |
| jest-util | 30.4.1 | 29.7.0 |
| write-file-atomic | 5.0.1 | 4.0.2 |
| @babel/core | 7.29.7 | 7.29.7 |
| @jridgewell/trace-mapping | 0.3.31 | 0.3.31 |
| chalk | 4.1.2 | 4.1.2 |
| convert-source-map | 2.0.0 | 2.0.0 |
| fast-json-stable-stringify | 2.1.0 | 2.1.0 |
| graceful-fs | 4.2.11 | 4.2.11 |
| micromatch | — | 4.0.8 |
| pirates | 4.0.7 | 4.0.7 |
| slash | 3.0.0 | 3.0.0 |
Moved: 6 · unchanged at every release: 9
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
-
observed UNKNOWN exit 1 Evidence gap ×2 29.7.0 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:91ad26545eb1…node:internal/modules/cjs/loader:<n> · throw err; · ^ · Error: Cannot find module <str>node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-29 · Last seen: 2026-08-31Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×1 29.7.0 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:eb0938a47430…node:assert:<n> · throw new AssertionError(obj); · ^ · AssertionError [ERR_ASSERTION]: jest.getVersion() should return 29.6.3node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 29.7.0 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:83bb774d0366…<path>:<n> · const snapshotsAdded = snapshotResults.added; · ^ · TypeError: Cannot read properties of undefined (reading <str>)node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31Diagnostic re-verification candidate