-
Notifications
You must be signed in to change notification settings - Fork 0
fix: og image #1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
c05a9f0
to
3803a9a
Compare
|
@vicatnight |
Claude finished @cs50victor's task —— View job I'll analyze this and get back to you. |
@vicatnight you didnt do anything |
Claude finished @cs50victor's task —— View job I'll analyze this and get back to you. |
- Add dynamic OpenGraph image generation using Next.js ImageResponse - Create root-level opengraph-image.tsx for homepage - Add /t route opengraph-image.tsx for thoughts section - Implement dynamic [slug] opengraph-image.tsx for individual posts - Update metadata generation to use dynamic images instead of static files - Add proper OpenGraph and Twitter card metadata to layouts - Ensure compatibility with Twitter, LinkedIn, and other social platforms Co-authored-by: cs50victor <[email protected]>
@vicatnight ci failed |
Claude finished @cs50victor's task —— View job I'll analyze this and get back to you. |
- Remove Node.js fs/path imports from Edge Runtime OG image components - Replace dynamic file system access with hardcoded metadata for edge compatibility - Add generateStaticParams for proper build-time generation - Fix unused import warnings - Update metadata to match actual post content This resolves CI failures caused by using Node.js APIs in Edge Runtime context. Co-authored-by: cs50victor <[email protected]>
No description provided.