CodeSampleX

Recordsnpm@emnapi/core1.11.1@emnapi/core.MessageHandler

Change the conditions
Fixed
Symbol@emnapi/core.MessageHandler
Filter OSubuntu glibc Runtimenode 22 Package version1.11.1 Architecturex64 Package managernpm 10 Execution contextnode libcglibc Clear filters

Current conditions

@emnapi/core.MessageHandler @1.11.1ubuntu glibc · x64 · node 22 · npm 10 · node

0 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 failed

Project observations
nothing at this coordinate
Contract verifications
0 / 1
Last recorded
2026-09-19
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 1

First observed break

1.11.1

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

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

View exact conditions View failure cluster
Library Version Health Measured there Projects
@emnapi/wasi-threads 1.2.2 CANDIDATE Correlated change; unproven combination contract passed 6 project-days
tslib 2.8.1 PASS All observations passed contract passed 6 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.

Library1.11.31.11.11.10.01.7.1
@emnapi/wasi-threads 1.2.3 1.2.2 1.2.1 1.1.0
tslib 2.8.1 2.8.1 2.8.1 2.8.1

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