Hi. I left a like and a comment on the issue you opened, as I'm currently facing the same problem. However, I am weary of "throwing AI" at the problem here, and I don't think this code should be merged if you, as the author, can't validate whether you believe it's a good fix. This seems to be a complex issue related to having the same version/instance of React available to the parent app / child React component within an MDX page.

It seems like the solution you proposed would instantiate a new version of React for every component rendered by MDX, which does not seem like a great idea.

Thanks @icco for opening the issue. Rather than instantiating a new version of React for every component rendered by MDX as @isaacmattern, let me try modifying getMDXComponent directly. This is the code that builds the component and it seems that in the latest version of mdx-bundler it is not possible to pass in a custom runtime to it.

Hi. I left a like and a comment on the issue you opened, as I'm currently facing the same problem. However, I am weary of "throwing AI" at the problem here, and I don't think this code should be merged if you, as the author, can't validate whether you believe it's a good fix. This seems to be a complex issue related to having the same version/instance of React available to the parent app / child React component within an MDX page.

It seems like the solution you proposed would instantiate a new version of React for every component rendered by MDX, which does not seem like a great idea.

Mostly just wanted to kick off discussion and provide a possible solution. Glad we've got folks looking into a better solution.