Recordsnpm@babel/plugin-transform-arrow-functions
Change the conditions
Current conditions
@babel/plugin-transform-arrow-functions @7.29.7ubuntu glibc · x64 · node 22 · npm 10 · node
0 of 27 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate failed (2)
- Project observations
- 113 / 113
- Contract verifications
- 0 / 27
- Usage records
- 42
- Independent reporting peers
- 3
- Last recorded
- 2026-09-17
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
0 of 27 passed
Verified — this network ran a contract at this coordinate.
-
@babel/plugin-transform-arrow-functions.default
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.7
windows · node@24.13 · moduleSystem=esm · executionContext=node
32 FAIL
· stage: UNKNOWN
· fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @babel/helper-plugin-utils | 7.29.7 | CANDIDATE Correlated change; unproven combination | contract passed | 58 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.1 | 7.29.7 |
|---|---|---|
| @babel/helper-plugin-utils | 8.0.1 | 7.29.7 |
Moved: 1 · unchanged at every release: 0
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.