Sync with upstream/downstream projects regarding v2

[johno]

When we get a v2 canary released we should begin chatting with MDX dependents that will be affected. Generally speaking most integrations should be unaffected by v2, but it'd be worth sanity checking big projects. This change is also likely to affect Prettier (and also offer APIs that might help their formatting).

• Prettier
• gatsby-plugin-mdx (no updates needed) https://github.com/johno/johno.com/commit/087ec932f879517dab30ef66c418804fc6741888
• Next.js (pretty sure nothing changes)
• Docz (will no longer need some of their parser additions)
• Storybook (not sure if this changes anything)
• Docusaurus
• eslint-mdx Support for MDX v2 eslint-mdx#204
• Gatsby recipes (will likely begin shipping with the next tag before v2 ships)
• MDX Deck
• Spectacle

Are there any missing?

[jerelmiller]

In working on the latest MDX v2 alpha, there are a couple Gatsby plugins that are incompatible. Should these be added to the list?

• gatsby-plugin-autolink-headers - Custom IDs are no longer supported
• gatsby-remark-images - Images do not render with the changes to the AST. This plugin compiles to an html node, which went away with MDX v2

[wooorm]

I’ve also been reaching out to Gatsby folks and Gatsby plugin maintainers about aligning. I still think it’s unfortunate that Gatsby wants wrapper plugins, like: we have remark-images and remark-autolink-headers that’ll just keep on working 🤷‍♂️

[wooorm]

done and doing!