I'm glad it's useful. Enjoy!

All the MDEx.Document handling is done in Elixir including buffering and completing markdown chunks (using nimble_parsec). On the Rust side it "only" does parsing and rendering via crates.io/crates/comrak (an amazing project btw).

Exactly, it's not event based. MDEx doesn't care how or how often you push chunks into the Document. So you can keep a Document in a LiveView and keep pushing into it and render when needed. There's an example here github.com/leandrocp/md...

It can afford to re-render as many times as needed because it's very efficient, although I'm expecting to gather some feedback and adjust if needed. One of the reasons this is considered experimental yet.

This approach is similar to streamdown.ai but using nimble_parsec. A more optimized approach would require rewriting the parser from scratch like github.com/thetarnav/st... is doing but that's not on my plans.

Fragments are buffered until a render or parser is requested (when `MDEx.to_html` or `Document.run` or others are called). At this moment the buffer tail is completed if needed (**text -> **text**) then appended to the rest of the document and re-rendered (that's where Rustler is called). 1/n

And more detailed in the CHANGELOG at hexdocs.pm/mdex/changel...

4. `MDEx.Pipe` is gone. Now all operations are centralized into `MDEx.Document`. Yes that's a **breaking** change but it's worth it.

Pipelines are as simple as adding steps into the document:

3. The Document struct is now displayed in a tree format for better visualization with each node indexed:

Here's a short demo of Markdown streaming in MDEx 👀

Note it's still experimental and disabled by default.

2. Streaming! Now it does complete and render incomplete chunks of Markdown for you:

hexdocs.pm/mdex/MDEx.Do...

Thanks to @jskalc.bsky.social we now support converting Markdown to quilljs.com/docs/delta

The difference between `Keyword.get(opts, :foo, :default)` and `opts[:foo] || :default` when opts[:foo] is nil. Not a big deal but easy to miss.

Valeu Dhony :)

Example highlighting some lines. It does use the `CursorLine` highlight group (the current line in Neovim) to style the line but you can change both class/style(1) to fine-tune it for your needs.

(1) Depends on the formatter.

Example overwriting the theme. Use one of the themes available from autumnus.dev

But I'd say to avoid it if you can :)

Beacon does build and compile modules at runtime github.com/BeaconCMS/be...

Whenever a module is requested and still not available, it will run the compiler. Here's where that happens github.com/BeaconCMS/be...