From a5c1216a4cf1ce16f9797f08225e00f3bb451449 Mon Sep 17 00:00:00 2001 From: "hyungji.k" Date: Thu, 8 May 2025 21:51:31 +0900 Subject: [PATCH] fix: correct file extension --- docs/01-app/01-getting-started/10-metadata-and-og-images.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/01-app/01-getting-started/10-metadata-and-og-images.mdx b/docs/01-app/01-getting-started/10-metadata-and-og-images.mdx index c1462f2314b9c..81a063b4da310 100644 --- a/docs/01-app/01-getting-started/10-metadata-and-og-images.mdx +++ b/docs/01-app/01-getting-started/10-metadata-and-og-images.mdx @@ -235,9 +235,9 @@ The more specific image will take precedence over any OG images above it in the The [`ImageResponse` constructor](/docs/app/api-reference/functions/image-response) allows you to generate dynamic images using JSX and CSS. This is useful for OG images that depend on data. -For example, to generate a unique OG image for each blog post, add a `opengraph-image.ts` file inside the `blog` folder, and import the `ImageResponse` constructor from `next/og`: +For example, to generate a unique OG image for each blog post, add a `opengraph-image.tsx` file inside the `blog` folder, and import the `ImageResponse` constructor from `next/og`: -```tsx filename="app/blog/[slug]/opengraph-image.ts" switcher +```tsx filename="app/blog/[slug]/opengraph-image.tsx" switcher import { ImageResponse } from 'next/og' import { getPost } from '@/app/lib/data'