[dannote]

For vize 0.16.1.

The bug

vapor_split silently dropped slots when a text node came before an element:

Vize.vapor_split!(~S|<ul><li>a<ul><li>{{ b }}</li></ul></li><li>c</li></ul>|)
# before: statics ["<ul><li>a<ul><li> </li></ul></li><li>c</li></ul>"], slots []
# after:  statics ["<ul><li>a<ul><li>", "</li></ul></li><li>c</li></ul>"], slots [%{kind: :set_text, ...}]

Vize's IR is correct. It navigates with child_ref/next_ref offsets that count every DOM child node, including text runs and <!----> anchors, so the inner ul is offset 1 inside its li, after the text a. The split's tag mapping counted element children only, so it found no element at that offset and skipped the slot without an error. A text-only fallback hid the problem in some simpler templates.

The fix

• The template scanner records each tag's DOM node index, counting text runs and anchors, and child_ref/next_ref resolve by it. The element-only child_index is removed.
• If an element that a text, HTML or prop slot, an event, v-model or v-show belongs to still can't be located, vapor_split returns {:error, [message]} instead of dropping the slot.

Found while checking Vue 3.6.0-rc.10's compiler-vapor fixes against Vize. Those fixes are upstream Vize's to port; this bug was in vize_ex's own split code.

This also carries a docs-only commit linking Vue's documentation for Vapor mode, SFCs and SSR.

Verification

• VIZE_EX_BUILD=1 mix ci passes: lint (including clippy) and 125 tests.
• Regression tests cover:
  • the nested-list case;
  • mixed text and elements with text, prop and later text slots;
  • an event binding after a text node.
• A Rust unit test covers node indices across text runs and anchors.
• Templates with tables, SVG foreignObject, interleaved text and v-for options all place every slot and binding.