We encountered runtime errors where Next.js was attempting to tree-shake the @sparticuz/chromium package, removing the essential Chromium binary needed at runtime. By adding it to serverExternalPackages in next.config.ts, we ensure the binary is included as-is in the deployment, preventing the 'input directory does not exist' failure.