export feature does not work unless surrounded by newlines

This is a strange issue, but finally found the source after digging for a bit. Basically, if you run an export, like this, but do not include newlines around the export, it is not detected at all, and will drop the export verbatim as a string into the resulting mdx file. As far as I know, es6 modules do not have any rules around adding extra newlines, so the behavior was pretty confusing to me.

I would be more than happy to submit a patch to fix this, just want to make sure that the maintainer(s) of the library give me the green light first!

To reproduce - this works:

import Layout from './Layout'

export default ({ children }) => <Layout some='metadata' >{children}</Layout>

# Hello, world!

However, this does not:

import Layout from './Layout'
export default ({ children }) => <Layout some='metadata' >{children}</Layout>

# Hello, world!

[johno]

I’m going to preemptively close this because it will be supported in 0.18 that should go out next week. Thanks for opening up the issue!

[johno]

The other thing is introducing a substantially larger bundle size (for the library itself not the output which affects things like the runtime), but that might be inevitable to ensure our parsing is solid. It’s definitely something I’m open to, but might make sense as its own issue to weigh the pros and cons to kick off such an initiative.