Recordsnpm@babel/generator
Change the conditions
Current conditions
CodeGenerator @7.29.7x64 · 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 (2)
- Project observations
- 1 / 1
- Contract verifications
- 1 / 1
- Independent reporting peers
- 1
- Last recorded
- 2026-08-27
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
alpine musl · x64 · node 22 · npm · node
1 of 1 passed
Verified — this network ran a contract at this coordinate.
-
debian glibc · x64 · node 22 · npm · node
1 of 1 passed
Observed — real project builds reported from this coordinate.
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
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.