hast VS remark-rehype

contentlayer uses remark to parse the markdown in an mdast. We can now use remark plugins to modify the mdast. Then rehype comes into play and converts the mdast into a hast. rehype plugins can now modify the hast. Finally the hast is converted into react components.

remark-rehype translates the mdast structure into a Hypertext Abstract Syntax Tree (hast) structure, also composed of unist nodes.

We have to pass hast elements thought. If you want to read more about hast elements, check out this documentation link.

Is it so hard to accept that a tool or app could compile a html document into some intermediate form and then use that to internally construct a DOM representation, maybe out of a cache?

I usually combine remark-parse, remark-rehype and rehype-react to transform markdown into react components. The configuration of the processor is like:

remark-rehype: remark plugin that turns markdown into HTML to support rehype.

The trouble is when i use use remark-rehype each item from the frontmatter gets converted to either a

Astro supports Markdown input files out of the box as well as remark and rehype plugins.