Recordsnpm@emnapi/core1.10.0
Change the conditions
Current conditions
@emnapi/core @1.10.0windows 11 · x64 · node 24 · npm 11 · node
package-level total, not an API
Recorded as present in projects. Nothing was run at this coordinate.
Observed — real project builds reported from this coordinate.
no sample at this coordinate yet
- Project observations
- nothing at this coordinate
- Contract verifications
- nothing at this coordinate
- Usage records
- 1
- Independent reporting peers
- 1
- Last recorded
- 2026-08-13
Dependency Health
Observed combinations and failure evidence for this release
First observed break
1.10.0
linux · node@22.23 · executionContext=node · moduleSystem=esm
1 FAIL
· stage: UNKNOWN
· fingerprint: sha256:054c93088b95acdec26c27553355ea7447db339349572fdd4ba431478ecb744a
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @emnapi/wasi-threads | 1.2.1 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| tslib | 2.8.1 | PASS All observations passed | 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.11.3 | 1.11.1 | 1.10.0 | 1.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.