markstream-custom-components

You can customize Markdown rendering by applying scoped overrides to Markstream renderers using setCustomComponents(customId, mapping). This isolates changes to image, link, code_block, and other node types, preventing global modifications to core rendering behavior.

Yes, Markstream supports trusted custom tags that render inner Markdown via nested renderers. This allows complex content structures to be processed while preserving node context across the entire rendering pipeline.

The best way to scope renderer overrides is using setCustomComponents(customId, mapping) with a unique identifier. When the scope ends, you call removeCustomComponents(customId) to clean up and remove the applied mappings cleanly.

Yes, Markstream supports overriding renderers for mermaid, d2, and infographic nodes. You can map these keys in your custom component configuration to tailor how visual and diagram content is displayed per project.

Markstream preserves node context across renders when applying custom component overrides. This ensures that scoped mappings for image, link, code_block, or inline_code maintain their original context throughout the nested rendering process.

Scoped custom components are limited to supported override keys like image, link, code_block, mermaid, d2, infographic, and inline_code. Overrides require manual cleanup via removeCustomComponents(customId) to prevent stale mappings from persisting beyond their intended scope.