Skip to content

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

Open
wants to merge 7 commits into
base: main
Choose a base branch
from
Open

fix: og image #1

wants to merge 7 commits into from

Conversation

cs50victor
Copy link
Owner

No description provided.

Copy link

vercel bot commented Apr 15, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
vic-so ❌ Failed (Inspect) May 23, 2025 6:08am

@cs50victor
Copy link
Owner Author

  • debug using vercel deployment og image viewer

@cs50victor
Copy link
Owner Author

@vicatnight
please make sure the og image works for twitter, linkedin etc and just in geenreal test to make sure it works

Copy link

claude bot commented May 23, 2025

Claude finished @cs50victor's task —— View job


I'll analyze this and get back to you.

@cs50victor
Copy link
Owner Author

@vicatnight you didnt do anything

Copy link

claude bot commented May 23, 2025

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]>
@cs50victor
Copy link
Owner Author

@vicatnight ci failed

Copy link

claude bot commented May 23, 2025

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]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant