json-render 0.21.3 repairs repeated stream operations and patch-state drift
Released October 24, json-render 0.21.3 stops dropping identical consecutive JSONL operations, keeps YAML move/copy results in the working state used by later edits, and constrains inherited-property and out-of-range array paths.
Why it matters
Every streamed operation in generative UI represents a state transition. Text deduplication, shared references after copy, or prototype-chain path traversal can drop items, leave deleted content visible, or let a patch affect objects outside its intended scope.
A closer look
Previously, two identical add /items/- lines were treated as duplicate text by processedLines, so the second item disappeared; the compiler now applies every line. The YAML transform applies each yaml-patch to its working spec and clones copied and emitted values, allowing later yaml-edit blocks to remove or modify move/copy results correctly while bounding copy growth. Path helpers now traverse own properties and dense arrays only. The preceding 0.21.2 also fixed code generation for non-identifier object keys, production Devtools detection, server-side PDF repeat containers, and React actions without a setter.
Who this is for
Frontend and agent-platform teams using json-render streamed specs, YAML patches, React/PDF renderers or model-generated object keys
Original sources
- json-render official releases and pull requests ↗github.com
- YAML patch-state and path-boundary fix ↗github.com
- Repeated SpecStream JSONL operations fix ↗github.com
- Official v0.21.2 release — 2026-10-23 ↗github.com
Revisions & corrections (1)
— Published a verified official patch sequence with direct Generative UI state-integrity impact. The October 24 release date, repeated-stream bug, YAML move/copy state drift, cloning and path-boundary behavior were confirmed in the release and merged pull requests; limits were kept explicit.