Export complete MDX unified processor

[silvenon]

This will allow advanced usage besides just compiling MDX string to JSX, like providing a vfile and attaching various data to it via remark and rehype plugins.

[vercel]

This pull request is being automatically deployed with ZEIT Now (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://zeit.co/mdx/mdx/j424x7or6
✅ Preview: https://mdx-git-export-full-compiler.mdx.now.sh

[silvenon]

My use case: I'm extracting various metadata from MDX files, like YAML frontmatter, in Next.js getStaticProps so I can generate my blog posts using dynamic routes.

Adding .mdx files directly to pages directory just doesn't give me enough control, this brings me a bit closer.

[wooorm]

Nice! Not necessarily for you/now, but maybe a good idea to add docs for these things?

[wooorm]

Btw, what are you missing if you do: unified().use(remarkParse).use(remarkMdx)?

[silvenon]

Nice! Not necessarily for you/now, but maybe a good idea to add docs for these things?

Done!

Btw, what are you missing if you do: unified().use(remarkParse).use(remarkMdx)?

• I can't call .process() because I don't have a compiler, so I have to awkwardly execute phases parse and run
• MDX adds remark-squeeze-paragraphs and md-ast-to-mdx-ast.js before adding remark plugins, so it's not the same
• I can't use rehype plugins (not that I need to, currently)
• having this abstraction would generally make me less anxious about whether I'm doing it right

[silvenon]

I'll assume that I'm free to merge this 😃