Added comprehensive logging to diagnose the WASM loading issue: - Log the WASM URL being fetched - Log fetch response (status, content-type, content-length) - Log actual WASM file size after fetching - Verify the buffer is not empty before initialization - Pass ArrayBuffer directly to initializeImageMagick - Better error messages with context This will help identify why the WASM file appears empty: - Is the fetch failing? (wrong path, 404, CORS) - Is the response empty? (server issue) - Is the content-type wrong? (misconfigured server) The logs will appear in the browser console when converting images. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
4.2 KiB
4.2 KiB