feat: handle simple mdx rendering

[ematipico]

Changes

This PR adds some infrastructure to handle compiled languages such asmdx. In particular, this PR addresses mdx, but we will explore an architecture that would allow to render Markdoc documents too.

The idea is to introduce a flag called isModule (better names are welcome). If an entry is treated as a module, then its rendering phase is deferred at runtime.

The store exposes new APIs to create a temporary file called modules.mjs where people can create a map that will look like this:

{
	"content/file.mdx": () => import("virtual-module")
}

This logic is implemented in our glob loader, which will generate a file like this:

{
	"content/file.mdx": () => import('astro:content-module-imports?astro%3Acontent-module-imports=&importer=content-outside-src-mdx%2Figuana.mdx&astroContentModuleFlag=true')
}

In the runtime, via virtual modules, we retrieve the correct file to render and we execute the dynamic import. The vite system will transform the import, and it will return to us an Astro component, which we will map to the collection

Testing

For now, I added a test. I plan to add more of them while I will explore a more stable way to re-use our existing architecture

Docs

[changeset-bot]

⚠️ No Changeset found

Latest commit: 9637227

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR