CodeSampleX

Recordsnpm@babel/plugin-bugfix-firefox-class-in-computed-class-key8.0.1

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

Current conditions

@babel/plugin-bugfix-firefox-class-in-computed-class-key @8.0.1ubuntu glibc · x64 · node 22 · npm 10 · node

package-level total, not an API

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

Project observations
3 / 3
Contract verifications
0 / 1
Independent reporting peers
1
Last recorded
2026-09-03
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 0

First observed break

8.0.1 @babel/helper-plugin-utils@8.0.1

linux · node@22.23 · moduleSystem=esm · executionContext=node

1 FAIL · stage: UNKNOWN · fingerprint: sha256:963dc79aa288c19eee01bb47568c83786a210bb952d8560eea6a22241495b6f7

View exact conditions View failure cluster
Library Version Health Measured there Projects
@babel/helper-plugin-utils 8.0.1 FAIL Linked failure observed; version changed across releases 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/traverse — 7.29.8

Moved: 1 · unchanged at every release: 1

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