With full latest setup (Next.js 15.2.x + next-mdx-remote 5.0.0), cannot use RSC mode at all.

[LumaKernel]

Describe the bug

Simply just follow the instruction on https://nextjs.org/docs/pages/building-your-application/configuring/mdx#remote-mdx, and try rendering the MDX including math inline (like $1 + 1 = 2$) anything like # Hello, you'll see the error.

....
 GET / 500 in 711ms
kj ⨯ [TypeError: Cannot read properties of undefined (reading 'stack')] {
  digest: '3975977629'
}
 ⨯ [Error: failed to pipe response] {
  [cause]: [TypeError: Cannot read properties of undefined (reading 'stack')] {
    digest: '3975977629'
  }
}
 GET / 500 in 835ms

Cannot do the simplest thing as following.

import { MDXRemote } from "next-mdx-remote/rsc";

export default function RemoteMdxPage() {
  const mdxText = "# Hello";
  return <MDXRemote source={mdxText} />;
}

It seems like a fatal error, completely nothing will be shown in the browser.

Reproduction

https://github.com/LumaKernel/nextjs-issue-mdx-remote-rsc

next-mdx-remote version

5.0.0

[LumaKernel]

I believe the stack is coming from micromark's extension, usually uses the this.stack, which is done in many rehype/remark plugins.

For example, remark-math is doing like this: https://github.com/syntax-tree/mdast-util-math/blob/23647664692ae59be25896d0099ba3f7157d6a76/lib/index.js#L85

[LumaKernel]

But at least, I injected debug console.log for remark-math, but seems this.stack is always existing. So other plugin may affect.

[ginkcode]

This happen since we upgrade next from 15.1.7 to 15.2.x
Temporarily downgrade next version can help.

[Elmosh]

yes same exact error

[LumaKernel]

@ginkcode Thanks, I confirmed that worked on my real project too.

[joshwcomeau]

This appears to be related to a change made in Next 15.2, and tracked here: vercel/next.js#76395

Sounds like the team is saying that this is due to an issue to how other libraries are importing React, so it should be fixable within next-mdx-remote? Though it is kind of a bummer to see them deflecting when it’s affecting so many packages!

[KilianSL]

Confirm we are experiencing the same error with "next-mdx-remote": "^4.4.1", and "next": "15.2.1",

[MikeCodeur]

same problem with next 15.2.1

[ullenboom]

Same, I have to downgrade Next.

[Vacilando]

Bump!

[timtbdev]

Same problem and downgraded back to Next.js 15.1.7.

[Entropy-10]

same issue

[niko20]

same issue here

[pjuerg]

Same!