Recordsnpm@jest/console30.4.1@jest/console.getConsoleOutput
Change the conditions
Current conditions
@jest/console.getConsoleOutput @30.4.1ubuntu glibc · x64 · node 22 · npm 10 · node
2 of 2 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 (2)
- Project observations
- 2 / 2
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Last recorded
- 2026-09-06
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
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @jest/types | 30.4.1 | CANDIDATE Correlated change; unproven combination | 10 project-days | |
| @types/node | 26.4.0 | CANDIDATE Correlated change; unproven combination | 2 project-days | |
| @types/node | 26.4.1 | CANDIDATE Correlated change; unproven combination | 8 project-days | |
| jest-message-util | 30.4.1 | CANDIDATE Correlated change; unproven combination | 10 project-days | |
| jest-util | 30.4.1 | CANDIDATE Correlated change; unproven combination | 10 project-days | |
| chalk | 4.1.2 | UNKNOWN No linked outcome measured | 10 project-days | |
| slash | 3.0.0 | UNKNOWN No linked outcome measured | 10 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 |
| @types/node | 26.4.0 | 26.3.0 |
| jest-message-util | 30.4.1 | 29.7.0 |
| jest-util | 30.4.1 | 29.7.0 |
| chalk | 4.1.2 | 4.1.2 |
| slash | 3.0.0 | 3.0.0 |
Moved: 4 · 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.
Recent failure clusters
-
observed UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×1 30.4.1 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:054c93088b95…node:internal/modules/run_main:<n> · triggerUncaughtException( · ^ …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
-
observed UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×1 30.4.1 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:769e5b509341…node:internal/process/promises:<n> · triggerUncaughtException(err, true <path> fromPromise */); · ^ …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
-
observed UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×1 30.4.1 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:a878372dcfe9…AssertionError [ERR_ASSERTION]: getVersion must return 30.4.2 · <str> !== <str> · at main (<path>:<n>:<n>) · at Object.<anonymous> (<path>:<n>:<n>)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