markdown_view_leptos
Compile-time Markdown to Leptos view! with MDX‑like inline components.
- Inline components in Markdown using
{{ <MyComp prop=value/> }} - Use string,
file = "...", orurl = "..."sources - Fenced‑code aware: ignores
{{ ... }}inside triple‑backtick code blocks - Works in CSR or SSR; no runtime parser cost in the browser
Security note: the generated HTML is injected via
inner_html. Only use trusted Markdown or sanitize upstream.
Install
cargo add markdown_view_leptos
For CSR (WASM):
rustup target add wasm32-unknown-unknown- Use a bundler like Trunk (
cargo install trunk)
Quick start
use *;
use markdown_view;
Inline string
Works with normal or raw strings; inline {{ ... }} components are spliced in.
use *;
use markdown_view;
From a file
file paths are resolved relative to your crate root (CARGO_MANIFEST_DIR). Literal paths are embedded at compile time so edits trigger recompiles.
You can also point to a variable. If the macro can resolve it at compile time (e.g., let content = "content.md"; or format!("content.md") where the file exists), it behaves like a literal path. Otherwise it falls back to reading at runtime (non-wasm only) and inline components are rendered as plain Markdown.
let base = "/opt/articles";
let name = "welcome.md";
let view = markdown_view!;
For wasm builds, use a path the macro can resolve at compile time so the content is embedded (no filesystem at runtime).
Dynamic string at runtime
String/&str variables are accepted; Markdown is rendered at runtime and {{ ... }} is left untouched.
From a URL (build‑time fetch)
use *;
use markdown_view;
- Happens at compile‑time (not client runtime), using a blocking HTTP GET.
- For editor tooling (rust‑analyzer), remote fetch is disabled and a small placeholder is returned for responsiveness.
- Remote fetch happens at build time on non‑wasm targets (blocking HTTP GET). rust‑analyzer and wasm builds get a placeholder for responsiveness. Network errors fall back to a placeholder; otherwise the fetched content is embedded.
- Prefer
file = "..."for reproducible builds.
How it works
- Markdown → HTML: Parsed with
pulldown‑cmark(tables, footnotes, strikethrough, task lists). Injected viainner_htmlinto aview!tree. - Inline components: Any
{{ ... }}outside fenced code blocks is parsed as Rust/RSX and spliced into theview!tree (for compile-time sources: string literal,file, orurl). DynamicStringinputs render as plain Markdown without expanding{{ ... }}. - Fenced code: Triple‑backtick fences (```) are respected;
{{ ... }}inside them is ignored and rendered literally. - Parse fallback: If a snippet inside
{{ ... }}doesn’t parse, it is rendered as plain Markdown so your build doesn’t fail unexpectedly. - Front matter: Pass
strip_front_matter = trueto drop a leading--- ... ---block (YAML-style) before rendering if you don't want it to show up.
Options: strip front matter
When your Markdown carries YAML front matter, prefix the macro with strip_front_matter = true before the source.
use *;
use markdown_view;
The flag also works with inline strings:
let view = markdown_view!;
Example
This repo includes a CSR example (Trunk):
examples/markdown-csr-example: Renders a canvas‑basedParticleTextcomponent from within Markdown.
Run with Trunk:
cd examples/markdown-csr-example
trunk serve --open
Tips & caveats
- Scope: Components referenced inside
{{ ... }}must be in scope where you invoke the macro. - Styling: Wrap the macro output with your own container and styles, then target markdown elements with CSS.
- Sanitization: If you need strict XSS safety, sanitize before compile time or filter the source.
- Rebuilds:
file = "..."usesinclude_str!to make the file a build input; saving it triggers a rebuild.
Testing & contributing
- Run tests:
cargo test - Lint & format:
cargo clippy --all-targets -- -D warningsandcargo fmt --all - Issues & PRs welcome. Keep scopes small and messages clear (Conventional Commits).
Thank you for reading this 💙