Recordsnpm@napi-rs/wasm-runtime1.1.4@napi-rs/wasm-runtime.createFsProxy
Change the conditions
Current conditions
@napi-rs/wasm-runtime.createFsProxy @1.1.4ubuntu 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
- 1 / 1
- Contract verifications
- 0 / 1
- Independent reporting peers
- 1
- Last recorded
- 2026-09-19
Dependency Health
Observed combinations and failure evidence for this release
First observed break
1.1.4
linux · node@22.23 · moduleSystem=esm · executionContext=node
1 FAIL
· stage: UNKNOWN
· fingerprint: sha256:4735bf6fa39c0046f09c0dd2775986b49a1a5f7ca807a70aee10bf5e443efcd7
| 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.
| Library | 1.2.3 | 1.1.4 | 0.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
-
observed UNKNOWN exit 1 Evidence gap ×1 1.1.4 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 @napi-rs/wasm-runtime.createFsProxy sha256:4735bf6fa39c…<url> · createContext, · ^^^^^^^^^^^^^ · SyntaxError: The requested module <str> does not provide an export named <str>node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-19 · Last seen: 2026-09-19Diagnostic re-verification candidate