Migrate to MDX 2.0

[slorber]

🚀 Feature

We should migrate to MDX 2.0

PR: #8288

---

Update

• The MDX 2 PR has been merged
• I documented many breaking changes and provided some compatibility options (see PR)
• A canary release is now available (>= 0.0.0-5556)
• Need support to upgrade to MDX v2? See MDX v2 Upgrade Support

Please test it and give me some feedback here! 🙏

[armano2]

mdx 2.0 introduced breaking change, comments <!-- --> are not longer allowed in code, and thus mdxjs can't be used for simple markdown files

[slorber]

There are also disagreements in the MDX core contributors:

• Remove runtime renderer, still support MDXProvider mdx-js/mdx#1425
• An alternative “shortcode” (mdxType alternative) proposal mdx-js/mdx#1385

There's also a "fork" xdm project from Titus himself.

Let's not rush on this migration for now and see how things evolve.

[lunelson]

I strongly encourage using xdm, it's a simpler, faster and more stable pipeline, it is always in sync with the remark/rehype ecosystem and its development is moving quickly

[birdofpreyru]

Ok, @lex111, probably then add a warning block to the top of https://docusaurus.io/docs/markdown-features/react page, saying that current Docusaurus uses MDX v1? Cause I believe the current docs do not mention it, and the linked MDX site pages do not make it clear that there are two version with some features not supported in v1.

[lex111]

@birdofpreyru alright, although it seems self-evident for now, because MDX v2 is not officially released. However, the migration to MDX v2 will probably not be that easy, so it makes sense to do it (see #5575).
FYI, earlier in header of MDX website listed its latest version, but currently they have removed that info.

[pomber]

MDX v2 release candidate landing soon

[slorber]

MDX 2 RC 👍
https://v2.mdxjs.com/blog/v2/

And there's a migration guide: https://v2.mdxjs.com/migrating/v2/