TSXLight / docsProject documentation

Reference

Rerender Consistency

Look up syntax, contracts, layouts, algorithms, and exact behavior.

Because the server owns the component tree, rerender consistency depends on sequencing. Callback invocation, state mutation, callback-table replacement, HTML generation, and shell delivery must occur as one ordered transaction for a renderer.

Rut+1=deliver(render(mutate(Rut,callback)))R_u^{t+1}=deliver(render(mutate(R_u^t, callback)))
Renderer transaction. A renderer advances by applying one callback mutation, rendering the new state, and delivering the resulting shell.
  • Only the addressed renderer is mutated by a callback transaction.
  • The active callback table is regenerated from the rendered tree.
  • Page transitions persist outgoing state before replacing the active page.
  • Viewport updates are stored per renderer and consumed during subsequent renders.
  • Duplicate or stale callbacks are rejected by renderer/page/callback identity checks.

This transaction model is the server-side equivalent of UI reconciliation. Instead of diffing fibers in the browser, TSXLight rebuilds the renderer-owned shell from authoritative server state.

Continue exploring

Tutorials →How-to guides →Explanation →Source repository →