Upgrade to MDX 3

[valentinpalkovic]

Breaking Changes

The main breaking change is that Node.js 16 is now the minimum supported version.
Across the ecosystem there were several small internal breaking changes. Everything’s released already. You can update all plugins now. If you ran into problems before, it should work now.
We also removed some infrequently used deprecated APIs. You’re likely fine but gloss over the v3 migration guide if you get errors.
Important to note when you use your lesser-known but powerful evaluate, run, or outputFormat: 'function-body' APIs, please pass the baseUrl option. That makes sure import.meta.url, import, and export work. You’ll get a runtime error when those features are used otherwise.

from https://mdxjs.com/blog/v3/

Migration Guide

https://mdxjs.com/migrating/v3/

Tasks

Tasks

Preview Give feedback

1. Update to MDX 3
2. Update documentation
3. Upgrade MDX in @storybook/docs-mdx
4. Deprecate/remove @storybook/mdx1-csf and @storybook/mdx2-csf packages
5. Refactor addon-docs to use mdx 3 compiler directly

[yannbf]

As additional information, here are the packages that relate to MDX:

• @storybook/docs-mdx (upgrade PR here)
• @storybook/mdx1-csf
• @storybook/mdx2-csf
• @storybook/addon-docs (via usage of the aforementioned mdx-csf packages)

According to @shilman we ideally should get rid of both mdx-csf packages, and bring their functionality directly into addon-docs (and use @mdxjs/mdx v3 there). This means we will also stop supporting the CSF in MDX format.