Recordsnpmespree
Change the conditions
Current conditions
espree.parse @10.4.0x64 · node 22 · node
1 of 2 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and this coordinate records both a passing and a failing run of it (1)
- Project observations
- 9 / 9
- Contract verifications
- 1 / 2
- Independent reporting peers
- 1
- Last recorded
- 2026-09-17
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
alpine musl · x64 · node 22 · npm · node
1 of 1 passed
Verified — this network ran a contract at this coordinate.
-
ubuntu glibc · x64 · node 22 · npm 10 · node
0 of 1 passed
Verified — this network ran a contract at this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
10.4.0
windows · node@24.13 · moduleSystem=esm · executionContext=node
32 FAIL
· stage: UNKNOWN
· fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10
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.
| Library | 11.2.0 | 10.4.0 | 9.6.1 |
|---|---|---|---|
| acorn | 8.18.0 | 8.18.0 | 8.15.0 |
| eslint-visitor-keys | 5.0.1 | 4.2.1 | 3.4.3 |
| acorn-jsx | 5.3.2 | 5.3.2 | 5.3.2 |
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.