Skip to content
nexisv1.3.3Build with Nexis

Architecture

Render the route.
Resume the edge.

Nexis starts with a simple premise: server rendering and browser interaction are different jobs. Treat them as different runtimes.

01Route component

Returns semantic server-rendered HTML.

02Compiler boundary

Finds events and bindings marked with $.

03Direct DOM work

Loads only when someone reaches that edge.

HTML FIRST

Content is an initial deliverable.

A static route sends HTML and CSS without route-specific JavaScript. That keeps essential information readable before any script executes and makes progressive enhancement the normal path.

RESUMABILITY

Do not replay what the server already did.

When an event prop ends in $, Nexis extracts the handler into a hashed chunk. The browser delegates the event, imports the chunk at first use, materializes its serializable scope, and runs only that boundary.

FINE-GRAINED

Touch the node, not the tree.

Signals can bind to a text node or a scalar DOM property. An effect() subscription updates the target directly; there is no virtual DOM diff and no component rerender.

“HTML first → progressive enhancement → resumable interaction → fine-grained DOM updates”

The delivery model behind every Nexis route.