CodeSampleX

Recordsnpm@babel/plugin-transform-async-to-generator

Change the conditions
Fixed
Package version8.0.1 Package managernpm 10
Filter OSubuntu glibc Runtimenode 22 Architecturex64 Execution contextnode libcglibc Clear filters

Current conditions

@babel/plugin-transform-async-to-generator @8.0.1ubuntu glibc · x64 · node 22 · npm 10 · node

0 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 failed (3)

Project observations
6 / 6
Contract verifications
0 / 1
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.

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

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.