CodeSampleX

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

Change the conditions
Fixed
OSwindows 11 Symbolwhole package
Filter Runtimenode 24 Package version8.0.1 Architecturex64 Package managernpm 11 Execution contextnode Clear filters

Current conditions

@babel/plugin-transform-async-to-generator @8.0.1windows 11 · x64 · node 24 · npm 11 · node

package-level total, not an API

3 of 7 passed

Observed — real project builds reported from this coordinate.

there is a sample here, and nothing of ours has run it at this coordinate yet (3)

Project observations
3 / 7
Contract verifications
nothing at this coordinate
Usage records
2
Independent reporting peers
1
Failures with a captured fingerprint
0 / 4
Last recorded
2026-08-17
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 · executionContext=node · moduleSystem=esm

4 FAIL · stage: PROJECT_TEST

View exact conditions View failure cluster
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.

Library8.0.17.29.7
@babel/helper-module-imports 8.0.0 7.29.7
@babel/helper-plugin-utils 8.0.1 7.29.7
@babel/helper-remap-async-to-generator 8.0.1 7.29.7

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