flux-md 0.18.1 → 0.18.3

package/CHANGELOG.md

@@ -4,6 +4,42 @@ Notable changes to flux-md. Format based on
 [Keep a Changelog](https://keepachangelog.com/); this project aims to follow
 [Semantic Versioning](https://semver.org/).
 
+## 0.18.3 — 2026-06-29
+
+### Fixed
+
+- **Nested bullets flattened mid-stream (a visible list reflow).** While
+  streaming a *loose* outer list (items separated by a blank line) whose items
+  contain indented nested sub-bullets, the incremental list fast path treated a
+  2-space-indented sub-bullet marker as a top-level **sibling** (it accepted any
+  marker within `edge + 3` columns). So the moment the outer list's second item
+  began streaming, the first item's nested `<ul>` **collapsed into flat top-level
+  items**, then re-nested at finalize — a jarring "indentation disappears then
+  comes back" flicker. The sibling test now uses the first item's content column,
+  so a marker at or past it correctly nests (the cache bails to the full reparse,
+  which renders the nesting). Streamed output now matches a one-shot parse at
+  **every prefix**; the only remaining list change while streaming is the
+  inherent tight→loose spacing, which a non-streaming parser shows too.
+
+## 0.18.2 — 2026-06-29
+
+### Fixed
+
+- **Streaming O(n²) cliff on a paragraph followed by a long link-reference /
+  footnote definition run** (e.g. reference-heavy LLM output: prose, then a
+  block of `[id]: url` definitions). The paragraph stayed speculative until
+  `finalize()` — a definition is not a renderable block, so the paragraph never
+  became "the last block" and `committed_offset` stalled, re-scanning the whole
+  growing definition run on every append. A 235 KB document streamed at a
+  256-byte chunk took **~59 s**; it now takes **~20 ms**, and streaming is linear
+  in document size across all chunk sizes. A renderable block followed by a
+  definition run now commits (a definition only parses at a block boundary, so
+  the block is closed). Narrow behavior note, within the existing
+  forward-reference limitation: the single paragraph immediately before such a
+  run now commits before the later definitions, so a *forward* reference from it
+  renders literally instead of resolving at finalize — consistent with every
+  earlier paragraph, which already commits mid-stream.
+
 ## 0.18.1 — 2026-06-29
 
 Performance + size pass. No API or output changes — CommonMark 652/652 and

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "flux-md",
-  "version": "0.18.1",
+  "version": "0.18.3",
   "description": "Zero-dep streaming markdown for the browser. Rust→WASM core, Web Worker per stream, incremental parse with speculative closure.",
   "type": "module",
   "sideEffects": ["./dist/worker.js", "./dist/styles.css"],