Auto-detect WASM fallback for unsupported platforms (Termux/Android)

[kore4lyf]

Problem

Sharp v0.35.2 fails to load on Termux (Android ARM64):

Error: Could not load the "sharp" module using the android-arm64 runtime

No prebuilt binaries exist for android-arm64v8.

Workaround (verified working)

npm install @img/sharp-wasm32

Proposed Solution

Auto-detect unsupported platforms and fall back to WASM:

if (loadError && !process.env.SHARP_IGNORE_WASM_FALLBACK) {
  try {
    module.exports = require('@img/sharp-wasm32');
    return;
  } catch (_wasmError) {}
}

Benefits

• Zero-config for unsupported platforms
• WASM is slower but functional
• Opt-out via SHARP_IGNORE_WASM_FALLBACK=1

Related

• Termux, binaries are not yet available for android-arm64v8 #3850, Feature Request: Enable Sharp on Termux with Pre-built Binaries (Android arm64-v8) #4324, Failed to install sharp on termux #4161

[lovell]

Does the following work?

npm install --os=linux sharp

https://sharp.pixelplumbing.com/install/#cross-platform

[hiSandog]

It would be useful to distinguish Termux-as-Android from Linux ARM64 here. If npm install --os=linux sharp works in Termux, a WASM fallback might be unnecessary and slower for a platform that can use the Linux package. If it does not work, the issue should probably include the exact process.platform, process.arch, libc/runtime details, and the attempted package resolution path so the fallback decision does not accidentally mask other install problems.