CodeSampleX

Recordsnpm@napi-rs/wasm-runtime1.1.4@napi-rs/wasm-runtime.Memory

Change the conditions
Fixed
Symbol@napi-rs/wasm-runtime.Memory
Filter OSubuntu glibc Runtimenode 22 Package version1.1.4 Architecturex64 Package managernpm 10 Execution contextnode libcglibc Clear filters

Current conditions

@napi-rs/wasm-runtime.Memory @1.1.4ubuntu glibc · x64 · node 22 · npm 10 · node

1 of 1 passed

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

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

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 0

First observed break

1.1.4

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

1 FAIL · stage: UNKNOWN · fingerprint: sha256:4735bf6fa39c0046f09c0dd2775986b49a1a5f7ca807a70aee10bf5e443efcd7

View exact conditions View failure cluster
Library Version Health Measured there Projects
@tybys/wasm-util 0.10.2 CANDIDATE Correlated change; unproven combination contract passed 4 project-days
@tybys/wasm-util 0.10.4 CANDIDATE Correlated change; unproven combination contract passed 2 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.2.31.1.40.2.12
@tybys/wasm-util 0.10.3 0.10.4 0.10.1
@emnapi/core — — 1.7.1
@emnapi/runtime — — 1.7.1

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