TypeError: Cannot read properties of undefined (reading 'stack') when use next-seo

[PlutoCA]

When using the DefaultSeo or NextSeo components from next-seo, the following error occurs:

TypeError: Cannot read properties of undefined (reading 'stack')

codesandbox demo link

  "dependencies": {
    "next": "15.2.0",
    "next-seo": "^6.6.0",
    "next-sitemap": "^4.2.3",
    "react": "^19.0.0",
    "react-dom": "^19.0.0"
  },

Workaround:
Using the native component works, but the goal is to leverage next-seo's SEO features.

Request for Help:
Guidance is needed to resolve the configuration conflict or identify potential compatibility issues.

thanks！

[psdev0]

Identified the same issue with the usage of OrganizationJsonLd within Nextjs15 App Router.

[gijsbotje]

Ran into the same issue using <BreadcrumbJsonLd />. Removing this component from the DOM removes the error.

[gijsbotje]

In vercel/next.js#76395 someone said:

This is a pre-existing bug with these libraries. E.g. React.useId() wasn't working either. The affected library need to pass in the React module into the evaluated code instead of having the evaluated code import React which wouldn't be affected by bundlers.

Originally posted by @eps1lon in #76395

Maybe that will help pinpoint the issue.

[Pansther]

Ran into the same issue using <BreadcrumbJsonLd />. Removing this component from the DOM removes the error.

Same, working by downgrade next to v15.1.7

[dominik-sfl]

Any news on this? Breaking everywhere for us right now.

[gijsbotje]

@dominik-sfl someone just posted a temporary fix in vercel/next.js#76395

const nextConfig: NextConfig = {
  // ...
  transpilePackages: ['next-seo'],
};

This will fix the error, though the source of the issue should be fixed within next-seo.

[eps1lon]

next-seo seems fine. This is an issue with Next.js where we don't bundle next-seo which means next-seo doesn't get the right React version.