Architecture

WRNexusJS separates server work, generated markup, and browser behavior so applications stay understandable and efficient.

Request path

Request → Router → Middleware → Page/API → SSR document → Browser runtime

Compiler

The compiler parses .wrn files and lowers state, events, interpolation, loops, conditionals, data bindings, components, and styles into server modules and small declarative browser directives.

Runtime

The server owns routing, data, secrets, sessions, validation, uploads, and rendering. The browser owns reactive scopes, navigation, forms, realtime clients, and native capability dispatch.

Package boundaries

Each package is independently installable. Start with the CLI and core, then add database, security, realtime, native, UI, and operational packages as required.