Open theabhayprajapati opened 1 year ago
@theabhayprajapati Can you spin up a codesandbox or a repository with a minimal reproduction? That will make it easier for us to determine the root cause, thanks!
@theabhayprajapati did you ever get this resolved? I am experiencing the same issue
Facing the same issue.
The same issue with nextjs turbo
Anybody found solution to this?
If anyone can provide a minimal reproduction I'd be happy to take a look.
@dstaley check this sandbox
Error is about hydration..can you please help?
@chetanpan That sandbox is private. Mind making it public so I can access it?
@dstaley sorry, please check again...made it public...
@chetanpan Upgrade to the latest version of Next to get better hydration errors. <hr />
can't be a child of <p>
.
@dstaley
I have upgraded to latest next, also changed to very simple code.
Still getting hydration error.
@chetanpan Can you see if the issue occurs with next-mdx-remote@0.0.0-canary-20240321205249
? I don't think it does, so this might be a MDX v2 issue that was fixed in v3.
@dstaley, I tried with canary, same error. Page (uses compilation) hydration error seems to have something to do with MDXContent rendering. Page2 (uses MDXRemote) gives error about MDXRemote as well.
Also, I have observed that if I use <>{result.content}</>
instead of <div>{result.content}</div>
, it works fine! How come?
@chetanpan I'm not seeing the same behavior in my fork of your CodeSandbox. Since this is mainly hydration issues (and not Cannot read properties of undefined
) would you mind opening a new issue with a reproduction? We can take a closer look together there!
@dstaley I get error in your fork in chrome as well...So, I tried Firefox, alas, error is there, too
I will create new issue.
SOURCE CODE.
when even i use MDXRemote component i am getting this error. please let me know how can i fix this.
Built with "next": "13.4.3",