Replacing Sharp with WASM: How a Hidden SVG Dependency Broke Our Rendering Pipeline

This article details a production incident where Open Graph social cards returned 404s due to a runtime security setting that disabled libvips's SVG loader, breaking the Sharp-based rasterization path. The author describes the debugging process using Datadog and Splunk, the discovery of an intermediate SVG stage, and the two-part fix: replacing Sharp with resvg WASM for deterministic rendering and using a static fallback image. The article covers technical details about Next.js file-based Open Graph routes, Satori, and runtime dependency selection, making it relevant for developers dealing with similar rendering pipeline issues.