Overview — Nexis documentation

What Nexis is

Nexis is a TypeScript framework for useful server-rendered HTML with browser JavaScript emitted only for the parts that require interaction. It combines SSR/SSG, progressive enhancement, resumability, and fine-grained DOM updates without a virtual DOM.

How a request moves

The Router selects a route, the Renderer produces HTML and metadata, the Compiler records interaction boundaries and ScopeRef metadata, and the CLI writes output files. In the browser, the event bootstrap imports a lazy chunk only after an interaction.

Choose boundaries deliberately

Begin with the HTML users must receive. Then identify the smallest region that truly needs browser behavior.

Keep marketing, articles, docs, and essential product data static when possible.
Put interaction in focused buttons, searches, forms, or directly bound scalar properties.
Do not expect Nexis to turn arbitrary closures, databases, or authentication into transferable client state.

PRACTICAL LABS

Run this capability.

Each example states the observable output, the boundary that remains your responsibility, and the check that proves the result.

Start with meaningful HTML

TSX

export default function Home() {
  return <main><h1>Inventory</h1><p>Useful before scripts.</p></main>
}

OUTPUT: The heading and content are in the first response.
BOUNDARY: Do not make essential content depend on a browser-only fetch.
PROVE IT: View Source and confirm the heading exists.

VERIFICATION

Prove the contract.

Inspect the generated HTML before JavaScript runs and use the analyzer to confirm that static routes emit no route-specific JavaScript.