CodeSampleX

Recordsnpm@babel/code-frame

Change the conditions
Fixed
Package version8.0.0 Symbol@babel/code-frame.highlight
Filter Runtimenode 22 Architecturex64 Execution contextnode Clear filters

Current conditions

@babel/code-frame.highlight @8.0.0x64 · node 22 · node

1 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 came back clean (1)

Project observations
1 / 1
Contract verifications
1 / 1
Independent reporting peers
1
Last recorded
2026-08-20

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 2 · Steady 0

First observed break

8.0.0

linux · node@22.23 · executionContext=node

8 FAIL · stage: UNKNOWN · fingerprint: sha256:986d98189e70ab6bb81e3ca5f5feb96281ba0dfa6e522caa6ddd3d9b148578cc

Library Version Health Measured there Projects
@babel/helper-validator-identifier 8.0.4 CANDIDATE Correlated change; unproven combination contract passed 46 project-days
js-tokens 10.0.0 CANDIDATE Correlated change; unproven combination contract passed 45 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: 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.