[Feature Request] export

[alexanderbluhm]

It would be very nice to use export in the .mdx files to better use layouts and other stuff. I also saw a few issues here where users tried to do this.

In my use case I am building a table of contents which should be rendered next to the markdown content.
I have a custom remark plugin which simply creates a list of all headings. In another project I simply write
export const toc = content which is pretty useful because I can now use this toc e.g. as the sidebar of my current layout.

In the current mdx-remote implementation I think the easiest way would be to parse the headings and insert the result into the frontmatter part but this is a bit ugly.

So maybe this feature will be implemented in the future :)

[max-pod]

@alexanderbluhm Hi, I'm actually trying to do this exact same thing with building a TOC. Would it be possible for you to share your code?

[alexanderbluhm]

@max-pod I didn't implemented it yet unfortunately.

[max-pod]

@alexanderbluhm
Gotcha!

I think I'll end up resolving my problems in the short term just using regular expressions to parse the content, #231 (comment). Some of the other ideas might also help.

[AugustinMauroy]

if #396 is merge it's can solve your issue ?

[dimaMachina]

For anyone who wanted this feature, I created PR to add this feature #407

[talatkuyuk]

next-mdx-remote-client supports export statements in MDX, and it allows you pass vFile.data into the scope automatically.

Hence you can create table of contents (TOC) via using a custom remark plugin or a remark plugin like remark-flexible-toc and supply into MDX easily thanks to the option vfileDataIntoScopeof next-mdx-remote-client. See here for an example.