[Feature]: Migrate from xdm to mdx-js v2

[benseitz]

What is the new or updated feature that you are suggesting?

A few days ago MDX 2 got released!

I propose to migrate from xdm to mdx-js v2.

Why should this feature be included?

As far as I understand all features from xdm are now part of mdx-js v2.
Also, it seems like xdm could not be supported sometime in the future.
(see: wooorm/xdm/issues/94 and kentcdodds/mdx-bundler/issues/137)

For me, it would make sense to migrate to the official mdx-js for these reasons.

Is this something you would want as well?
Or is someone already working on this? Would you be interested in a PR?

[axe312ger]

As far as I know, MDX2 got a lot of learnings & code from xdm. That should mean, the migration effort is not too high.

[mayank99]

xdm now explicitly recommends using mdx 2 as well.

[chaance]

Happy to take a PR to address this. Going to close the issue as it's not a top priority in the meantime.

[jacobwgillespie]

Hey, I have opened a PR for this here: #4054. As a bonus, removing xdm will remove deasync, which is a native dependency that requires compilation (which can break).

[github-actions]

🤖 Hello there,

We just published version v0.0.0-nightly-b1149bb-20230810 which involves this issue. If you'd like to take it for a test run please try it out and let us know what you think!

Thanks!