[ Package conformance ]
Image · >=11.0.0
expo-image-manipulator
real worker-safe implementation via OffscreenCanvas + createImageBitmap + convertToBlob; both legacy manipulateAsync and v12+ class-based ImageManipulator/Context/Image APIs are wired through to actual pixel work. Output bytes are real PNG/JPEG/WEBP, base64 is real, Context chaining produces correct intermediate frames, SaveFormat/FlipType enums match upstream identity. The remaining gap is SharedObject identity (not a functional difference in pixel output) and a slightly different resize algorithm (OffscreenCanvas drawImage with imageSmoothingQuality=high vs. upstream JS Hermite resampler — outputs match iOS bicubic in practice).93%
API coverage
No visual conformance cases have been published for this package yet. The registry summary below describes what the compat layer implements.
Working (7)
manipulateAsync (resize/rotate/flip/crop/extent + JPEG/PNG/WEBP output + base64)ImageManipulator.manipulateuseImageManipulator hookContext chaining (resize/rotate/flip/crop/extent/reset/renderAsync/release)Image.saveAsync with qualityFlipType/SaveFormat enumsall type exports
Missing (1)
SharedRef identity across cross-module boundaries (expo-modules-core SharedObject) — we mirror the public API surface but consumer code that compares ref identity across modules will see different objects