CodeSampleX

Recordsnpm@babel/plugin-transform-async-generator-functions8.0.1

Change the conditions
Fixed
OSalpine musl Package managernpm
Filter Runtimenode 22 Package version8.0.1 Symbolwhole package Architecturex64 Execution contextnode libcmusl Clear filters

Current conditions

@babel/plugin-transform-async-generator-functions @8.0.1alpine musl · x64 · node 22 · npm · node

package-level total, not an API

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 (1)

Project observations
2 / 2
Contract verifications
1 / 1
Usage records
1
Independent reporting peers
1
Last recorded
2026-09-05
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 3 · Steady 0

First observed break

8.0.1

windows · node@24.13 · moduleSystem=esm · executionContext=node

4 FAIL · stage: PROJECT_TEST

View exact conditions View failure cluster
Library Version Health Measured there Projects
@babel/helper-plugin-utils 8.0.1 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
@babel/helper-remap-async-to-generator 8.0.1 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
@babel/traverse 8.0.4 CANDIDATE Correlated change; unproven combination contract passed 3 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.

Library8.0.17.29.7
@babel/helper-plugin-utils 8.0.1 7.29.7
@babel/helper-remap-async-to-generator 8.0.1 7.29.7
@babel/traverse 8.0.4 7.29.8

Moved: 3 · 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.

Recent failure clusters