CodeSampleX

Recordsnpm@img/sharp-wasm320.35.3

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

Current conditions

@img/sharp-wasm32 @0.35.3windows 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
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 0

First observed break

0.34.5

windows · node@24.13 · executionContext=node · moduleSystem=cjs

4 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:0470f88d95bb52932e5704cdc30cfcecbd43ae71af54d4c5f93d16aa27317cd2

View exact conditions View failure cluster

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.

Library0.35.40.35.20.34.5
@emnapi/runtime 1.11.3 1.11.3 1.7.1

Moved: 1 · unchanged at every release: 0

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.