Global configuration for custom MDX components

[ohansemmanuel]

Hey there 👋🏽

Out of curiosity, Is there an ongoing consideration to make it possible to configure custom MDX components for an Astro project in one place? Without repetition across multiple pages/files?

As it stands, it appears custom components have to be defined per page where they are consumed.

While one may arguably build a remark plugin / Astro integration to auto-import components, it might be nice to support configuring these in one place, if it doesn't already exist. Similar to how NextJS uses an MDXProvider in the app.js file.

Potentially, these may work:

• configure components in a layout component, and use this layout in every MDX file
• expose a markdown configuration option in astro.config.mjs
• some other clever idea, as I haven't given this deep thought

...

Cheers

[yanthomasdev]

Hey @ohansemmanuel 👋, we don't have plans for global MDX components for now, according to our public roadmap.

The community package astro-auto-import is compatible with MDX and works similarly to what you proposed, I hope it can help you!

EDIT: Also, our recent Markdoc integration, which is a different file format/syntax, so I would not recommend migrating to it only for that, can do that: https://docs.astro.build/en/guides/integrations-guide/markdoc/#render-markdoc-tags-as-astro-components

[ohansemmanuel]

In that case, auto-importing suffices for now. Many thanks, @Yan-Thomas 🙏