01
Focused packages
Core owns render nodes, Router owns URL matching, Renderer owns HTML and streams, Reactivity owns Signals, Client owns scope materialization, Compiler and Vite plugin own boundaries and chunks, and CLI owns discovery and output.
02
Build output
nexis build discovers routes, expands static paths, renders pages, emits CSS, writes interaction runtimes only where required, then generates metadata artifacts such as sitemap, robots, feeds, and manifests.
03
ScopeRef is the boundary ABI
Instead of transferring arbitrary closures, Nexis serializes tagged references to values, Signals, stores, or Actions. Unsupported captures become visible diagnostics rather than silent runtime differences.
PRACTICAL LABS
Run this capability.
Each example states the observable output, the boundary that remains your responsibility, and the check that proves the result.
01
Inspect the artifact
Shellpnpm build
pnpm exec nexis routes
pnpm analyze- OUTPUT
- The build reports routes, output, and delivery assets.
- BOUNDARY
- Treat generated HTML and the manifest as the release contract, not a development preview.
- PROVE IT
- Compare route output with the source boundaries you wrote.
VERIFICATION
Prove the contract.
Open nexis-manifest.json and compare its routes, chunks, and emitted runtimes with the interaction boundaries in source.