fix: restore OG image generation in production (pin @takumi-rs to 0.62.8)#649
Merged
Conversation
…to 0.62.8 The Jul 2 dependency bump (#631) took @takumi-rs/image-response and @takumi-rs/wasm from 0.62.8 to 1.8.7. Since that deploy, every /api/og request in production returns 200 with an empty body: the render crashes the lambda's Node process (exit status 128) while working fine locally on macOS under Node 22/24/26. Bisected across production deployments — the deploy before #631 serves real images, the #631 deploy does not. Pin both packages back to 0.62.8 (verified rendering locally and the options API is compatible), set format: 'png' explicitly since takumi's default output format changed across versions and some social crawlers don't render WebP, and add a dependabot ignore so the pin isn't silently re-bumped before a fixed release is verified against production. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Since the Jul 2 dependency bump (#631) took
@takumi-rs/*from 0.62.8 → 1.8.7, every/api/ogrequest in production returns 200 with an empty body — social cards have had no image. The render crashes the lambda's Node process (fatal: Node.js process exited with exit status: 128in Vercel logs) while working fine locally on macOS under Node 22, 24, and 26.Bisected across production deployments (with the automation-bypass header):
pny5kssqb(Jul 2, pre-#631)c1b45d7o6xs10ty9(Jul 3, #631)0e580346b14228Fix
@takumi-rs/image-responseand@takumi-rs/wasmback to 0.62.8. The 0.62.8 options API is compatible with the current handler (itsImageResponseOptionsalso extendsResponseInit, so the cache header from fix: serve correct SEO/social-card head tags on marketing and blog pages #648 still applies).format: 'png'explicitly — takumi's default output changed across versions (0.62.8 emits WebP by default) and some social crawlers (notably Facebook) don't render WebPog:images.ignorefor@takumi-rs/*with an explanatory comment, so the pin isn't silently re-bumped before a fixed release is verified against a production deployment.Verification
Local build +
dist/preview.js:/api/og?...returns 200image/png, 92KB, correct 1200×657 card (pill breadcrumb, title, logo),cache-control: public, max-age=31536000, immutable. 130 vitest + biome + tsgo green.🤖 Generated with Claude Code