CodeSampleX

Recordsnpm@babel/code-frame7.29.7

Change the conditions
Fixed
Runtimenode (version not recorded) Package version7.29.7
Filter OSwindows 11 Symbolwhole package Architecturex64 Package managerpnpm 10 Execution contextnode Clear filters

Current conditions

@babel/code-frame @7.29.7windows 11 · x64 · node (version not recorded) · pnpm 10 · 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.

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

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
1
Independent reporting peers
1
Last recorded
2026-09-01
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 1

First observed break

7.29.7

windows · node@24.13 · moduleSystem=esm · executionContext=node

32 FAIL · stage: UNKNOWN · fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10

View exact conditions View failure cluster
Library Version Health Measured there Projects
@babel/helper-validator-identifier 7.29.7 CANDIDATE Correlated change; unproven combination contract passed 212 project-days
js-tokens 4.0.0 CANDIDATE Correlated change; unproven combination contract passed 211 project-days
picocolors 1.1.1 PASS All observations passed contract passed 212 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.07.29.77.27.1
@babel/helper-validator-identifier 8.0.4 7.29.7 7.28.5
js-tokens 10.0.0 4.0.0 4.0.0
picocolors — 1.1.1 1.1.1

Moved: 2 · 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