CodeSampleX

Compatibilitynpmespree10.4.0espree.parse

Change the conditions
Fixed
OSalpine musl Symbolespree.parse
Filter Runtimenode 22 Package version10.4.0 Architecturex64 Package managernpm Execution contextnode libcmusl Clear filters

Current conditions

espree.parse @10.4.0alpine musl · x64 · node 22 · npm · 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
nothing at this coordinate
Contract verifications
1 / 1
Last recorded
2026-08-27

Dependencies

LibraryVersionMeasured thereProjects
acorn 8.18.0 contract passed 5 project-days
acorn-jsx 5.3.2 contract passed 5 project-days
eslint-visitor-keys 4.2.1 contract passed 5 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.

Library11.2.010.4.0
eslint-visitor-keys 5.0.1 4.2.1
acorn 8.18.0 8.18.0
acorn-jsx 5.3.2 5.3.2

Moved: 1 · unchanged at every release: 2

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