Essential content lives in the initial response.
framework v1.3.3 · typescript-native
Serve the document.
Wake the interaction.
Nexis starts with useful server-rendered HTML, then extracts only the event or binding a person actually reaches. No virtual DOM. No whole-tree hydration.
static routes SSR ISR partial render
01
Route traceHTML → boundary → direct update
Handlers become small chunks, not an app replay.
A changing value updates the target—nothing else.
The Nexis default
The page is not a browser app waiting to become useful.
Nexis separates rendering from interaction. A route without a boundary emits HTML and CSS—not route-specific application JavaScript. A route with a boundary serializes only supported references and waits for an intent to load its chunk.
Read the architectureOne framework. Carefully separated runtimes.
Make every byte explain itself.
STATIC
Static and server render modes
Choose static, ISR, server, or partial work per route—without changing the component model.
Rendering modes →EVENT
Resumable events
Append $ to an event prop. Nexis compiles the boundary and loads it on the first interaction.
BINDING
Fine-grained signals
Bind text and scalar DOM properties directly. The component does not run again.
Inspect direct binding →FORM
Progressive forms
Native submission remains intact; enhancement layers in only where it helps.
Open form example →
Useful without JavaScript
The first response is the interface.
SEO, reader mode, slow connections, and direct links all begin with HTML that contains the content. Nexis treats progressive enhancement as the default delivery path, not a fallback.
src/routes/index.tsx0 KB route JS
export default function Home() {
return <main>Useful HTML</main>
}Ready when your route is.