Page not found
The address may be outdated or misspelled. No private or duplicate route is exposed here.
The address may be outdated or misspelled. No private or duplicate route is exposed here.
WRNexusJS 0.2.15 packages are not available from the public npm registry. Installation requires approval and private registry credentials supplied by WorkRoot. Never paste registry tokens into source control, issue reports, or support messages.
bunx @wrnexus/cli@0.2.15 create my-appAccess approval, response time, licensing terms, and support level remain owner-controlled. This site does not collect access requests directly.
WRNexusJS separates server work, generated markup, and browser behavior so applications stay understandable and efficient.
Request → Router → Middleware → Page/API → SSR document → Browser runtimeThe compiler parses .wrn files and lowers state, events, interpolation, loops, conditionals, data bindings, components, and styles into server modules and small declarative browser directives.
The server owns routing, data, secrets, sessions, validation, uploads, and rendering. The browser owns reactive scopes, navigation, forms, realtime clients, and native capability dispatch.
Each package is independently installable. Start with the CLI and core, then add database, security, realtime, native, UI, and operational packages as required.
WRNexusJS is Bun-native and SSR-first. File discovery maps pages and API handlers; middleware enriches or short-circuits a request; the compiler turns .wrn declarations into server render functions and small feature runtimes.
core owns contexts, middleware, sessions and rooms; router discovers routes; compiler parses .wrn; ssr renders documents; csr supplies browser runtimes; dev-server and cli orchestrate development and builds.
Validation happens at trust boundaries. Session authentication establishes identity; authorization makes resource decisions. CSP, Trusted Types, CSRF, upload checks, WebSocket origins, request limits, and output escaping are layered controls—not substitutes for application policy.
Rooms are process-local unless connected through pub/sub. Redis-backed pub/sub distributes events. Queue durability depends on the selected driver and must be evaluated explicitly.
The gateway can dispatch multiple applications while preserving route, component, asset, config, and session boundaries. Validate host routing and isolation before production.
wrnexus build . produces dist/server.js and hashed/static assets. Run the server with Bun, apply migrations before traffic, terminate TLS at a trusted edge, and forward only expected proxy headers.
Mobile compatibility bridges SSR-safe Capacitor capabilities; native route generation is experimental and is not general web portability. Test each target platform.
app/routes.gen.ts, .wrnexus/, and dist/ are generated. The runtime is Bun-only. Preview packages are private. Historical compatibility and long-term support policy are not yet published.
No comparative speed claims are published. A valid baseline must record scripts, commit, Bun/framework versions, hardware, OS, warmup, samples, workload, raw results, median, percentiles, memory, HTML size, browser JavaScript size, and run date.
The roadmap starts with WRNexusJS-only measurements before any maintained equivalent-workload comparison.
Documentation application aligned to all 25 installed packages, with generated README and TypeScript declaration references. This portal release establishes truthful private-preview access messaging and expanded framework navigation.
Keep all @wrnexus/* packages on the same release and run the installed CLI update workflow. No older framework release history is present in this repository.
The packages use semantic-looking versions, but a formal compatibility and old-release support policy has not been approved. Preview consumers should treat minor releases as potentially requiring migration review.
Examples are tied to installed 0.2.15 package documentation. The focused snippets in guides are source-verified; standalone runnable projects and CI compilation are tracked as remaining work.
Create a production-ready WRNexusJS application with Bun.
bunx @wrnexus/cli create my-app
+ W WRNexusJSPrivate preview · v0.2.15
+ Browse documentation
+ Preview guide · v0.2.15Build a contact inbox
This path creates a server-rendered page, validated API route, middleware, and realtime next step. It requires approved registry access and Bun 1.3.x; this site was verified with Bun 1.3.14.
1. Create the project
bunx @wrnexus/cli@0.2.15 create my-app
cd my-app
bun install
-bun run dev
2. Add a page
page Dashboard {
- state count = 0
- view {
- <main>
- <h1>Dashboard</h1>
- <button @click="count++">{count}</button>
+bun run dev
2. Know the structure
app/pages/ # file-based .wrn routes
+app/components/ # reusable .wrn components
+app/api/ # TypeScript request handlers
+app/middleware/ # ordered request middleware
+app/schemas/ # shared validation
+app/realtime/ # realtime rooms
+wrnexus.config.ts
3. Add a page
page Contacts {
+ view {
+ <main><h1>Contact inbox</h1>
+ <form data-schema="contact" action="/api/contacts" method="post">
+ <input name="email" type="email" /><span data-error="email"></span>
+ <textarea name="message"></textarea><span data-error="message"></span>
+ <button type="submit">Send</button>
+ </form>
</main>
- }
-}
3. Verify and build
wrnexus doctor
-wrnexus test
-wrnexus build
Where things live
app/pages contains routes.app/components contains reusable .wrn components.app/api contains server API handlers.app/layouts contains shared shells.app/middleware contains request middleware.wrnexus.config.ts configures security, styles, data, mobile, and deployment.
import schema from "../schemas/contact";
+import { parseBody } from "@wrnexus/validation";
+export const POST = async (ctx) => {
+ const result = await parseBody(schema, ctx.req);
+ return result.ok ? Response.json({ ok: true }, { status: 201 }) : result.response;
+};Use an ssr API binding and a server {#each} block. See Server data for the complete verified pattern.
export default async function logger(ctx, next) {
+ console.log(ctx.req.method, ctx.url.pathname);
+ return next();
+}bun run test
+bun run build
+bun dist/server.jsNext: deployment, database, authentication, and workspaces.
Export GET, POST, PUT, PATCH, or DELETE from app/api files. Validate request bodies, enforce authentication and authorization, cap request sizes, and return Web Responses.
This guide describes installed 0.2.15 capabilities. Follow linked package declarations for exact signatures; undocumented behavior is not guaranteed.
Configure session authentication, log users in through supported auth helpers, and read identity from context. Cookie flags, rotation, expiry, and secret storage remain deployment responsibilities.
This guide describes installed 0.2.15 capabilities. Follow linked package declarations for exact signatures; undocumented behavior is not guaranteed.
Authentication identifies; authorization decides. Enforce permissions in server routes and policies, including object ownership. UI hiding is never an authorization boundary.
This guide describes installed 0.2.15 capabilities. Follow linked package declarations for exact signatures; undocumented behavior is not guaranteed.
wrnexus.config.ts owns styles, SEO, security, data, mobile, fonts, and profiles. Keep secrets in validated environment variables and review merged production configuration.
This guide describes installed 0.2.15 capabilities. Follow linked package declarations for exact signatures; undocumented behavior is not guaranteed.
Configure SQLite or the installed supported driver, keep queries in named SQL blocks, generate typed functions, and apply migrations before traffic. Back up data and test rollback independently.
This guide describes installed 0.2.15 capabilities. Follow linked package declarations for exact signatures; undocumented behavior is not guaranteed.
Run bun run build, apply migrations, and start dist/server.js with Bun. Configure TLS, proxy trust, environment validation, health checks, graceful restarts, logs, backups, and restrictive security headers.
This guide describes installed 0.2.15 capabilities. Follow linked package declarations for exact signatures; undocumented behavior is not guaranteed.
Define a v.object schema, use data-schema on the form, show field errors with data-error, and always call parseBody on the server. refine is server-only.
This guide describes installed 0.2.15 capabilities. Follow linked package declarations for exact signatures; undocumented behavior is not guaranteed.
Store locale JSON under app/locales and use translation directives. Themes resolve CSS tokens; ensure contrast, system preference behavior, persistence, and non-color cues.
This guide describes installed 0.2.15 capabilities. Follow linked package declarations for exact signatures; undocumented behavior is not guaranteed.
Middleware receives context and next. Return next() to continue or return a Response to stop. Put request limits and trust-boundary controls before business logic.
This guide describes installed 0.2.15 capabilities. Follow linked package declarations for exact signatures; undocumented behavior is not guaranteed.
Mobile capabilities are experimental in this preview. Test Capacitor permissions and lifecycle on each platform; do not assume every .wrn or browser API converts to native.
This guide describes installed 0.2.15 capabilities. Follow linked package declarations for exact signatures; undocumented behavior is not guaranteed.
Use tracking middleware and sinks with redaction, sampling, stable request identifiers, alert ownership, and retention limits. Never capture registry tokens or session secrets.
This guide describes installed 0.2.15 capabilities. Follow linked package declarations for exact signatures; undocumented behavior is not guaranteed.
Pages are routable, components are reusable, and layouts provide shared slots. Mount a component with data-component and keep browser state scoped and minimal.
This guide describes installed 0.2.15 capabilities. Follow linked package declarations for exact signatures; undocumented behavior is not guaranteed.
Pages, components, layouts, APIs, middleware, schemas, database files, locales, realtime rooms, and styles live under app. Never edit app/routes.gen.ts, .wrnexus, or dist by hand.
This guide describes installed 0.2.15 capabilities. Follow linked package declarations for exact signatures; undocumented behavior is not guaranteed.
The in-process driver cannot cross processes. Use Redis where instances must share events, define channel ownership, and design for reconnects and duplicate delivery.
This guide describes installed 0.2.15 capabilities. Follow linked package declarations for exact signatures; undocumented behavior is not guaranteed.
Queue behavior is preview-level. Treat in-process work as non-durable, make handlers idempotent, cap retries, record failures, and choose a production persistence strategy.
This guide describes installed 0.2.15 capabilities. Follow linked package declarations for exact signatures; undocumented behavior is not guaranteed.
defineRoom handles connection and messages. Validate message shapes, authorize subscriptions, restrict origins, bound payloads, and use pub/sub to scale across processes.
This guide describes installed 0.2.15 capabilities. Follow linked package declarations for exact signatures; undocumented behavior is not guaranteed.
A page filename defines its URL; index maps to the directory root and bracket segments are dynamic parameters. API files under app/api expose HTTP method functions and receive a Context.
This guide describes installed 0.2.15 capabilities. Follow linked package declarations for exact signatures; undocumented behavior is not guaranteed.
Use CSP, CSRF, Trusted Types, session hardening, validation, origin checks, upload restrictions, encryption, request limits, and explicit CORS. See the security policy for reporting.
This guide describes installed 0.2.15 capabilities. Follow linked package declarations for exact signatures; undocumented behavior is not guaranteed.
Use an ssr API binding, return the desired response field, and render it with a server #each block. Values are escaped. Avoid fetching private data through a route that lacks authorization.
This guide describes installed 0.2.15 capabilities. Follow linked package declarations for exact signatures; undocumented behavior is not guaranteed.
Use Bun tests and @wrnexus/test helpers. Cover server HTML, API status and validation, authorization failures, reactive behavior, and a production startup smoke test.
This guide describes installed 0.2.15 capabilities. Follow linked package declarations for exact signatures; undocumented behavior is not guaranteed.
Confirm Bun and package versions, regenerate docs/routes through supported commands, read the first compiler diagnostic, check file naming, validate config, and reproduce under a production build.
This guide describes installed 0.2.15 capabilities. Follow linked package declarations for exact signatures; undocumented behavior is not guaranteed.
Back up and commit first, then use wrnexus update --latest as documented by the installed CLI. Review migrations and keep every @wrnexus package aligned. Current release: 0.2.15.
This guide describes installed 0.2.15 capabilities. Follow linked package declarations for exact signatures; undocumented behavior is not guaranteed.
Configure named stores, accepted MIME/extensions, and maxBytes. Random keys avoid path traversal. Private files require an authenticated serving route; v1 buffers each file in memory.
This guide describes installed 0.2.15 capabilities. Follow linked package declarations for exact signatures; undocumented behavior is not guaranteed.
The workspace gateway dispatches apps by configured boundaries. Test host matching, asset namespaces, cookies, sessions, errors, and cross-app authorization before deployment.
This guide describes installed 0.2.15 capabilities. Follow linked package declarations for exact signatures; undocumented behavior is not guaranteed.
An SSR-first, Bun-native framework with reactive .wrn components, typed data, realtime rooms, mobile capabilities, and production security built in.
page Counter {
- state count = 0
- view {
- <button @click="count++">
- Count {count}
- </button>
- }
-}Useful HTML reaches the browser immediately. Interactive pages hydrate only the runtime they use.
CSP, Trusted Types, CSRF, sessions, validation, authorization, encryption, and safe rendering are integrated.
Share markup through Capacitor or compile portable pages into Expo and React Native routes.
WRNexusJS v0.2.15
WRNexusJS is an SSR-first, Bun-native full-stack framework. Build typed pages, APIs, validated forms, realtime rooms, secure sessions, workspaces, and optional mobile experiences with the .wrn component language.
Packages require approved private-registry access. No public installation command is currently available.
Useful HTML is rendered first; reactive scopes hydrate only where declared.
.wrn componentsPages, layouts, props, state, events, server loops, and directives live in a focused language.
The runtime is Bun. Node compatibility is not claimed.
Database queries and shared validation connect server routes to forms.
CSP, CSRF, sessions, authorization, encryption, and safe output are framework primitives.
Rooms, Redis pub/sub, and multi-app gateways support live and isolated applications.
// app/schemas/contact.ts
+import { v } from "@wrnexus/validation";
+export default v.object({ email: v.string().email(), message: v.string().min(10) });
+
+// app/api/contacts.ts
+import schema from "../schemas/contact";
+import { parseBody } from "@wrnexus/validation";
+export const POST = async (ctx) => {
+ const result = await parseBody(schema, ctx.req);
+ return result.ok ? Response.json({ ok: true }, { status: 201 }) : result.response;
+};Public creator/company site and approved WRNexusJS production showcase.
This documentation application runs WRNexusJS 0.2.15.
| Capability | Status | Details |
|---|---|---|
| SSR, routing, compiler, APIs | Preview | Installed in 0.2.15; public support policy pending. |
| Mobile/native | Experimental | Capacitor compatibility and native generation have platform limitations. |
| Durable queues | Experimental | Production durability requires an appropriate driver strategy. |
This page documents the .wrn language and declarative browser features that span multiple packages.
-A file declares a page or component and can contain metadata, props, state, data, view, style, server functions, APIs, and realtime handlers.
page Dashboard {
- layout = "default"
- seo { title = "Dashboard" }
+ W WRNexusJSPrivate preview · v0.2.15
+ Browse documentation
+ Language reference · 0.2.15The .wrn language
File anatomy
page Account {
+ layout = "public"
+ seo { title = "Account" description = "Manage your account." }
state count = 0
- view { <button @click="count++">{count}</button> }
- style { button { padding: 12px; } }
-}
- State and interpolation
State is scoped to the nearest generated data-scope. Text expressions update reactively after hydration.
state count = 0
-state user = { name: "Ada" }
-
-view {
- <p>Count: {count}</p>
- <p>{user.name}</p>
-}
- Events
Any DOM event can use @event="statement". The compiler emits data-on-event. The expression receives event and can mutate state.
Syntax Purpose @clickPointer or keyboard activation. @inputRead live field values. @changeReact to committed field changes. @submitHandle form submission behavior. @browser-clickRun only in a browser target. @mobile-clickRun only in a native/mobile target.
<input @input="name = event.target.value">
-<button @click="count++">Add</button>
-<form @submit="submitted = true">...</form>
- Reactive data attributes
Directive Behavior data-scopeDeclares reactive state for a subtree. data-textSynchronizes textContent with an expression. data-showShows or hides an element by truthiness. data-forRepeats an element for a client-side list. data-on-<event>Compiled form of an event binding. data-componentMounts a server-rendered component. data-slotFills a named component or layout slot. data-wrnexus-csrConnects generated client data fetching.
- Conditional rendering
Server conditionals
Server blocks render only the selected branch into the response.
{#if user.isAdmin}
- <a href="/admin">Admin</a>
-{:else if user}
- <p>Welcome {user.name}</p>
-{:else}
- <a href="/login">Sign in</a>
-{/if}
Client visibility
<section data-show="open">Visible while open is true</section>
- Loops and lists
Server each block
{#each users as user, i}
- <p>{i + 1}. {user.name}</p>
-{:empty}
- <p>No users</p>
-{/each}
Reactive client loop
<li data-for="item, i in items">
- <span data-text="item.name"></span>
- <button data-on-click="items = items.filter(x => x !== item)">Remove</button>
-</li>
- Components, props, and slots
component Card {
- props { title = "Card" }
- view {
- <article><h2>{title}</h2><slot></slot></article>
- }
-}
-
-<div data-component="card" title="Profile">
- <p>Card content</p>
-</div>
- Server and client data
Use named data bindings for SSR data or client hydration. Secrets and database work stay on the server.
data users {
- ssr GET "/api/users"
-}
-
-view {
- {#each users as user}<p>{user.name}</p>{/each}
-}
- Forms and validation
Schema-backed forms validate in the browser and on the server with the same descriptor.
<form data-schema="login" method="post" action="/api/login" data-redirect="/dashboard">
- <input name="email" type="email">
- <span data-error="email"></span>
- <button>Sign in</button>
- <p data-success="Signed in" hidden></p>
-</form>
- Internationalization and themes
<h1>{t:home.title}</h1>
-<button data-wire-lang-set="fr">Français</button>
-<button data-wire-theme-toggle>Toggle theme</button>
-<button data-wire-theme-set="dark">Dark</button>
- Realtime rooms
<div data-room="chat" data-room-user="Ada">
- <span data-room-status></span>
- <div data-room-log></div>
- <template data-room-item="message"><p>%user%: %text%</p></template>
- <form data-room-send><input name="text" data-room-reset></form>
-</div>
- Browser and native directives
<button data-native-browser="share" data-native-mobile="share"
- data-native-options='{"title":"WRNexusJS"}'>Share</button>
-<nav data-native-only="mobile">Mobile navigation</nav>
-<p data-native-only="browser">Browser instructions</p>
-<button data-native-requires="haptics">Haptic action</button>
- Other framework attributes
Attribute Purpose data-errorField validation error destination. data-successSuccessful form message. data-redirectNavigation after form success. data-room-*Realtime status, templates, sending, and reset behavior. data-uploaderConfig-driven upload widget. data-wire-theme-*Theme selection and toggling. data-wire-lang*Language selection. data-native-*Cross-platform capability and visibility behavior.
Pages are routes. Components declare default-valued props and may hold state. Layouts provide shared slots. Mount components with data-component; fill default or named slots with data-slot.
Interpolation is HTML-escaped. Use server {#if} and {#each} for SSR data. Use data-show for reactive client visibility.
@click and other events execute in the reactive scope. Data attributes opt into forms, i18n, themes, realtime, uploader, browser, and mobile behavior. Consult the exact package page because availability varies.
form[data-schema] connects descriptors to client and server validation. Translation keys use {t:key}. Theme toggles use data-wire-theme-toggle. Realtime pages opt into a named room.
Text interpolation is escaped by default. Do not construct trusted HTML from user input. Server-only refinements must be repeated at the authoritative mutation boundary.
view, not JSX or hooks.This documentation repository contains no public license file, and the packages are unavailable from the public npm registry. No open-source license or redistribution right should be inferred.
Approved preview users must follow the private/commercial terms supplied by WorkRoot. Contact WorkRoot before copying, redistributing, or using WRNexusJS in production.
Released 2026-07-12 in this documentation repository. Twenty-five installed packages are aligned to this version. See the changelog, upgrade guide, and package references.
Roadmap items are direction, not delivery commitments. Dates require explicit owner approval.
This build-time index is local and sends no query to a third party. Use your browser’s find command to filter this compact index.
Get started · Tutorial · Architecture · .wrn language · Packages · Examples · Roadmap · Changelog · Security · Support · Search
Project structure · Routing · Pages and components · Server data · API routes · Middleware · Forms and validation · Authentication · Authorization · Application security · Database · Uploads · Realtime · Pub/sub · Queues · Testing · Workspaces and gateway · Deployment · Configuration and profiles · Internationalization and themes · Mobile · Observability · Upgrading · Troubleshooting
@wrnexus/ai · @wrnexus/authz · @wrnexus/compiler · @wrnexus/core · @wrnexus/csr · @wrnexus/db · @wrnexus/dev-server · @wrnexus/encryption · @wrnexus/i18n · @wrnexus/jwt · @wrnexus/mobile · @wrnexus/native · @wrnexus/oauth · @wrnexus/pubsub · @wrnexus/queue · @wrnexus/reactive · @wrnexus/router · @wrnexus/ssr · @wrnexus/styles · @wrnexus/test · @wrnexus/tracking · @wrnexus/ui · @wrnexus/uploader · @wrnexus/validation · @wrnexus/cli
WRNexusJS provides primitives for CSP, CSRF, Trusted Types, sessions, validation, authorization, encryption, upload restrictions, request limits, and WebSocket-origin checks. Applications remain responsible for correct configuration, business authorization, secrets, dependencies, data protection, and operations.
Only the current private-preview release 0.2.15 is documented here. A formal old-release support window is not yet published.
Use WorkRoot’s approved private contact path at workroot.in. Do not publish exploit details or secrets. Include affected version, impact, reproduction, and a safe contact method. Response targets, encryption key, bounty, audit, and certification are not currently claimed.
Use restrictive CSP and permissions policies, HSTS only on HTTPS production origins, MIME sniffing protection, restrictive referrers, explicit CORS, secure cookies, CSRF validation, request limits, and origin checks. See application security.
Only confirmed public properties are listed; no customer or traffic claims are made.
Creator/company site demonstrating a public WRNexusJS deployment. Exact deployed version and infrastructure notes await owner confirmation.
This documentation portal, built and verified against WRNexusJS 0.2.15 on Bun.
Screenshots are intentionally deferred until approved assets and alt text are available.
WRNexusJS has no public Discord, public issue tracker, or guaranteed community support channel listed by this repository. Preview access and support begin through WorkRoot’s public contact path.
Include WRNexusJS version, Bun version, OS, a minimal reproduction, expected and actual behavior, and sanitized logs. Never include registry tokens, credentials, session cookies, or private data.
Support scope, service levels, and commercial terms require owner confirmation.
This tutorial connects the installed 0.2.15 APIs into one design. Snippets are limited to declarations and README patterns verified in the installed packages; a CI-compiled standalone fixture remains on the roadmap.
A .wrn page renders tasks from an SSR API binding. A shared validation schema protects mutations. Session middleware identifies users, authorization policies gate updates, and a realtime room broadcasts changes.
import { v, parseBody } from "@wrnexus/validation";
+const task = v.object({ title: v.string().trim().min(3).max(120) });
+export const POST = async (ctx) => {
+ const parsed = await parseBody(task, ctx.req);
+ if (!parsed.ok) return parsed.response;
+ return Response.json({ ok: true, task: parsed.value }, { status: 201 });
+};page Tasks {
+ ssr { api tasks GET /api/tasks { return tasks } }
+ view {
+ <main><h1>Tasks</h1><ul>
+ {#each tasks as task}<li>{task.title}</li>{:empty}<li>No tasks yet.</li>{/each}
+ </ul></main>
+ }
+}Follow the focused database, authentication, authorization, realtime, and upload guides.
${esc(s).replaceAll("<", "<").replaceAll(">", ">")}WRNexusJS v${version}
WRNexusJS is an SSR-first, Bun-native full-stack framework. Build typed pages, APIs, validated forms, realtime rooms, secure sessions, workspaces, and optional mobile experiences with the .wrn component language.
Packages require approved private-registry access. No public installation command is currently available.
Useful HTML is rendered first; reactive scopes hydrate only where declared.
.wrn componentsPages, layouts, props, state, events, server loops, and directives live in a focused language.
The runtime is Bun. Node compatibility is not claimed.
Database queries and shared validation connect server routes to forms.
CSP, CSRF, sessions, authorization, encryption, and safe output are framework primitives.
Rooms, Redis pub/sub, and multi-app gateways support live and isolated applications.
Public creator/company site and approved WRNexusJS production showcase.
This documentation application runs WRNexusJS ${version}.
| Capability | Status | Details |
|---|---|---|
| SSR, routing, compiler, APIs | Preview | Installed in ${version}; public support policy pending. |
| Mobile/native | Experimental | Capacitor compatibility and native generation have platform limitations. |
| Durable queues | Experimental | Production durability requires an appropriate driver strategy. |
WRNexusJS ${version} packages are not available from the public npm registry. Installation requires approval and private registry credentials supplied by WorkRoot. Never paste registry tokens into source control, issue reports, or support messages.
Access approval, response time, licensing terms, and support level remain owner-controlled. This site does not collect access requests directly.
This path creates a server-rendered page, validated API route, middleware, and realtime next step. It requires approved registry access and Bun 1.3.x; this site was verified with Bun 1.3.14.
Use an ssr API binding and a server {#each} block. See Server data for the complete verified pattern.
Next: deployment, database, authentication, and workspaces.
This tutorial connects the installed ${version} APIs into one design. Snippets are limited to declarations and README patterns verified in the installed packages; a CI-compiled standalone fixture remains on the roadmap.
A .wrn page renders tasks from an SSR API binding. A shared validation schema protects mutations. Session middleware identifies users, authorization policies gate updates, and a realtime room broadcasts changes.
Follow the focused database, authentication, authorization, realtime, and upload guides.
WRNexusJS is Bun-native and SSR-first. File discovery maps pages and API handlers; middleware enriches or short-circuits a request; the compiler turns .wrn declarations into server render functions and small feature runtimes.
core owns contexts, middleware, sessions and rooms; router discovers routes; compiler parses .wrn; ssr renders documents; csr supplies browser runtimes; dev-server and cli orchestrate development and builds.
Validation happens at trust boundaries. Session authentication establishes identity; authorization makes resource decisions. CSP, Trusted Types, CSRF, upload checks, WebSocket origins, request limits, and output escaping are layered controls—not substitutes for application policy.
Rooms are process-local unless connected through pub/sub. Redis-backed pub/sub distributes events. Queue durability depends on the selected driver and must be evaluated explicitly.
The gateway can dispatch multiple applications while preserving route, component, asset, config, and session boundaries. Validate host routing and isolation before production.
wrnexus build . produces dist/server.js and hashed/static assets. Run the server with Bun, apply migrations before traffic, terminate TLS at a trusted edge, and forward only expected proxy headers.
Mobile compatibility bridges SSR-safe Capacitor capabilities; native route generation is experimental and is not general web portability. Test each target platform.
app/routes.gen.ts, .wrnexus/, and dist/ are generated. The runtime is Bun-only. Preview packages are private. Historical compatibility and long-term support policy are not yet published.
.wrn languagePages are routes. Components declare default-valued props and may hold state. Layouts provide shared slots. Mount components with data-component; fill default or named slots with data-slot.
Interpolation is HTML-escaped. Use server {#if} and {#each} for SSR data. Use data-show for reactive client visibility.
@click and other events execute in the reactive scope. Data attributes opt into forms, i18n, themes, realtime, uploader, browser, and mobile behavior. Consult the exact package page because availability varies.
form[data-schema] connects descriptors to client and server validation. Translation keys use {t:key}. Theme toggles use data-wire-theme-toggle. Realtime pages opt into a named room.
Text interpolation is escaped by default. Do not construct trusted HTML from user input. Server-only refinements must be repeated at the authoritative mutation boundary.
view, not JSX or hooks.${text}
This guide describes installed ${version} capabilities. Follow linked package declarations for exact signatures; undocumented behavior is not guaranteed.
Examples are tied to installed ${version} package documentation. The focused snippets in guides are source-verified; standalone runnable projects and CI compilation are tracked as remaining work.
Only confirmed public properties are listed; no customer or traffic claims are made.
Creator/company site demonstrating a public WRNexusJS deployment. Exact deployed version and infrastructure notes await owner confirmation.
This documentation portal, built and verified against WRNexusJS ${version} on Bun.
Screenshots are intentionally deferred until approved assets and alt text are available.
No comparative speed claims are published. A valid baseline must record scripts, commit, Bun/framework versions, hardware, OS, warmup, samples, workload, raw results, median, percentiles, memory, HTML size, browser JavaScript size, and run date.
The roadmap starts with WRNexusJS-only measurements before any maintained equivalent-workload comparison.
Roadmap items are direction, not delivery commitments. Dates require explicit owner approval.
Documentation application aligned to all 25 installed packages, with generated README and TypeScript declaration references. This portal release establishes truthful private-preview access messaging and expanded framework navigation.
Keep all @wrnexus/* packages on the same release and run the installed CLI update workflow. No older framework release history is present in this repository.
The packages use semantic-looking versions, but a formal compatibility and old-release support policy has not been approved. Preview consumers should treat minor releases as potentially requiring migration review.
Released 2026-07-12 in this documentation repository. Twenty-five installed packages are aligned to this version. See the changelog, upgrade guide, and package references.
WRNexusJS provides primitives for CSP, CSRF, Trusted Types, sessions, validation, authorization, encryption, upload restrictions, request limits, and WebSocket-origin checks. Applications remain responsible for correct configuration, business authorization, secrets, dependencies, data protection, and operations.
Only the current private-preview release ${version} is documented here. A formal old-release support window is not yet published.
Use WorkRoot’s approved private contact path at workroot.in. Do not publish exploit details or secrets. Include affected version, impact, reproduction, and a safe contact method. Response targets, encryption key, bounty, audit, and certification are not currently claimed.
Use restrictive CSP and permissions policies, HSTS only on HTTPS production origins, MIME sniffing protection, restrictive referrers, explicit CORS, secure cookies, CSRF validation, request limits, and origin checks. See application security.
WRNexusJS has no public Discord, public issue tracker, or guaranteed community support channel listed by this repository. Preview access and support begin through WorkRoot’s public contact path.
Include WRNexusJS version, Bun version, OS, a minimal reproduction, expected and actual behavior, and sanitized logs. Never include registry tokens, credentials, session cookies, or private data.
Support scope, service levels, and commercial terms require owner confirmation.
This documentation repository contains no public license file, and the packages are unavailable from the public npm registry. No open-source license or redistribution right should be inferred.
Approved preview users must follow the private/commercial terms supplied by WorkRoot. Contact WorkRoot before copying, redistributing, or using WRNexusJS in production.
This build-time index is local and sends no query to a third party. Use your browser’s find command to filter this compact index.
${navigation.map(([href, label]) => `${label}`).join(" · ")}
${Object.entries( + guides, + ) + .map(([slug, [title]]) => `${title}`) + .join(" · ")}
${Object.keys(pkg.dependencies) + .concat(Object.keys(pkg.devDependencies)) + .filter((name) => name.startsWith("@wrnexus/")) + .map((name) => `${name}`) + .join(" · ")}
The address may be outdated or misspelled. No private or duplicate route is exposed here.