how to skip caching for notFound or redirect?

[hkmute]

Is there a the correct way to prevent ISR caching when notFound or redirect is used in app router?

I am trying to create a route handler that calls revalidatePath and fetch it when no server data is available for a page. But it seems to be unstable when used with generateMetadata which fetches the same data inside

Sample code

export const dynamic = "force-static";
export const revalidate = 604800;

export async function generateMetadata(
  {
    params,
  }: {
    params: Promise<{ locale: Locale; slug: string }>;
  },
  parent: ResolvingMetadata,
): Promise<Metadata> {
  const { locale, slug } = await params;
  const blogDetails = await getBlogBySlug(slug, locale);

  return ...
}

const BlogDetailsPage = async ({ params }: Props) => {
  const { slug } = await params;
  const locale = await getLocale();
  const blogDetails = await getBlogBySlug(slug, locale);

  if (!blogDetails) {
    fetchRevalidatePath(`http://localhost:3000/api/revalidate?path=${currentPath}`)
    return redirect({
      href: routes.blog.index,
      locale,
    });
  }

  return ...
};

[icyJoseph]

I think, maybe here you want to group everything into a function, call it getBlogDetailsForPage, that gets the blog details, and if no details exist, does the revalidate - without a call to a route handler which won't exist during build time - call redirect. That call to redirect throws, so you don't have to return

Wrap that getBlogDetailsForPage with React.cache:

const getBlogDetailsForPage = React.cache(async (slug, locale) => {/* call getBlogBySlug  */});