Recordsnpm@babel/generator7.29.8
Change the conditions
Current conditions
@babel/generator @7.29.8windows 11 · x64 · node 22 · pnpm 10 · node
package-level total, not an API
11 of 14 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
- 11 / 14
- Contract verifications
- nothing at this coordinate
- Usage records
- 72
- Independent reporting peers
- 1
- Failures with a captured fingerprint
- 0 / 3
- Last recorded
- 2026-08-21
Dependency Health
Observed combinations and failure evidence for this release
First observed break
7.29.8
windows · node@24.13 · moduleSystem=esm · executionContext=node
32 FAIL
· stage: UNKNOWN
· fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @babel/parser | 7.29.8 | CANDIDATE Correlated change; unproven combination | contract passed | 160 project-days |
| @babel/types | 7.29.8 | CANDIDATE Correlated change; unproven combination | contract passed | 160 project-days |
| @jridgewell/gen-mapping | 0.3.13 | PASS All observations passed | contract passed | 151 project-days |
| @jridgewell/trace-mapping | 0.3.31 | PASS All observations passed | contract passed | 151 project-days |
| jsesc | 3.1.0 | PASS All observations passed | contract passed | 147 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 | 8.0.0 | 7.29.8 | 7.29.7 | 7.28.5 |
|---|---|---|---|---|
| @babel/parser | 8.0.4 | 7.29.8 | 7.29.7 | 7.28.5 |
| @babel/types | 8.0.4 | 7.29.8 | 7.29.7 | 7.28.5 |
| @jridgewell/gen-mapping | 0.3.13 | 0.3.13 | 0.3.13 | 0.3.13 |
| @jridgewell/trace-mapping | 0.3.31 | 0.3.31 | 0.3.31 | 0.3.31 |
| @types/jsesc | 2.5.1 | — | — | — |
| jsesc | 3.1.0 | 3.1.0 | 3.1.0 | 3.1.0 |
Moved: 2 · unchanged at every release: 4
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 PROJECT_TEST Evidence gap ×5 7.29.7 → 7.29.8 executionContext=node · os=windowsEvidence quality: legacy-evidence-incomplete · Environment variants: 3 · First recorded: 2026-08-21 · Last seen: 2026-08-25Diagnostic re-verification candidate
-
observed PROCESS_START process start failed Evidence gap ×3 7.29.8 → 8.0.0 executionContext=node sha256:c12549970456…· structured-termination · gap diagnostic-missingEvidence quality: partial · Environment variants: 2 · First recorded: 2026-09-05 · Last seen: 2026-09-16Diagnostic re-verification candidate
-
observed PROJECT_TYPECHECK Evidence gap ×2 7.29.7 → 7.29.8 executionContext=node · moduleSystem=cjs · os=windowsEvidence quality: legacy-evidence-incomplete · Environment variants: 2 · First recorded: 2026-08-19 · Last seen: 2026-08-21Diagnostic re-verification candidate