Recordsnpm@babel/plugin-transform-block-scoping
Change the conditions
Current conditions
@babel/plugin-transform-block-scoping @8.0.1ubuntu glibc · x64 · node 22 · npm 10 · node
0 of 2 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
- 8 / 8
- Contract verifications
- 0 / 2
- Independent reporting peers
- 1
- Last recorded
- 2026-09-05
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
0 of 2 passed
Verified — this network ran a contract at this coordinate.
-
@babel/plugin-transform-block-scoping.default
3 of 3 passed
Observed — real project builds reported from this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
8.0.1
windows · node@24.13 · moduleSystem=esm · executionContext=node
4 FAIL · stage: PROJECT_TEST
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @babel/helper-plugin-utils | 8.0.1 | CANDIDATE Correlated change; unproven combination | 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 | 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.