CodeSampleX

Recordsnpm@babel/plugin-transform-optional-chaining7.29.7

Change the conditions
Fixed
OSdebian glibc Package version7.29.7
Filter Runtimenode 22 Symbolwhole package Architecturex64 Package managernpm Execution contextnode libcglibc Clear filters

Current conditions

@babel/plugin-transform-optional-chaining @7.29.7debian glibc · x64 · node 22 · npm · node

package-level total, not an API

Recorded as present in projects. Nothing was run at this coordinate.

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
2
Independent reporting peers
1
Last recorded
2026-09-03

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 2 · Steady 0

First observed break

7.29.7 @babel/helper-plugin-utils@7.29.7

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

4 FAIL · stage: UNKNOWN · fingerprint: sha256:88af852f99a8104e4bc3c23eea27ebf2990625ccabf45313970f5fd7fe56c4e2

Library Version Health Measured there Projects
@babel/helper-plugin-utils 7.29.7 FAIL Linked failure observed; version changed across releases contract passed 27 project-days
@babel/helper-skip-transparent-expression-wrappers 7.29.7 FAIL Linked failure observed; version changed across releases contract passed 27 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: 2 · 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

Showing the 12 most-reported of 14 recorded failure clusters. The rest are single reports.