CodeSampleX

Recordsnpm@babel/plugin-transform-async-to-generator8.0.1plugin-transform-async-to-generator

Change the conditions
Fixed
Runtimenode 22 Symbolplugin-transform-async-to-generator
Filter OSdebian glibc Package version8.0.1 Architecturex64 Package managernpm Execution contextnode libcglibc Clear filters

Current conditions

plugin-transform-async-to-generator @8.0.1debian glibc · x64 · 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 (1)

Project observations
1 / 1
Contract verifications
1 / 1
Independent reporting peers
1
Last recorded
2026-09-14

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

Library Version Health Measured there Projects
@babel/helper-module-imports 8.0.0 CANDIDATE Correlated change; unproven combination contract passed 6 project-days
@babel/helper-plugin-utils 8.0.1 CANDIDATE Correlated change; unproven combination contract passed 6 project-days
@babel/helper-remap-async-to-generator 8.0.1 CANDIDATE Correlated change; unproven combination contract passed 6 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.

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