CodeSampleX

Recordsnpm@emnapi/runtime1.11.3

Change the conditions
Fixed
Runtimenode 24 Package version1.11.3
Filter OSwindows 11 Symbolwhole package Architecturex64 Package managernpm 11 Execution contextnode Clear filters

Current conditions

@emnapi/runtime @1.11.3windows 11 · x64 · node 24 · npm 11 · node

package-level total, not an API

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
Usage records
3
Independent reporting peers
1
Last recorded
2026-09-17
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 1

First observed break

1.11.3

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
tslib 2.8.1 PASS All observations passed 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.

Library1.11.31.11.11.10.01.7.1
tslib 2.8.1 2.8.1 2.8.1 2.8.1

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