generateMetadata is getting trigered on notFound

[quiloos39]

Summary

I am getting following behaviour and not sure if its normal or not. I would expect when notFound got trigered it would not trigger generateMetadata. Also it seems it's overriding not-found page metadata as well.

Packages:

"next": "14.2.3",
"react": "^18",
"react-dom": "^18",

To replicate it:

Inside /test/page.tsx

import { Metadata } from "next";
import { notFound } from "next/navigation";

const Page = () => {
  return notFound();
};

export const generateMetadata = async (): Promise<Metadata> => {
  console.log("generateMetadata");
  return {};
};

export default Page;

Output:

generateMetadata
 GET /test 404 in 1089ms
 GET /_next/static/chunks/app/react-toastify.esm.mjs.map 404 in 1100ms
 GET /_next/static/css/app/ReactToastify.css.map 404 in 949ms

Additional information

No response

Example

No response

[nOji]

The same issue here!