B1: qualify each generated __wrn_api_check_* assertion name with a short hash of the page's path (relative to app/, for reproducibility across checkouts) so two pages declaring a same-named block no longer collide with an identical type alias (TS2300). B2: skip assertion emission for any block that is not client-mode, or that has zero declared request fields. ssr sectioned blocks can never declare a request and always fell back to Record<string, never>, whose keyof is `string` -- making the key-exactness arm of AssertAssignable evaluate to false unconditionally (TS2344) on every ssr sectioned block regardless of correctness. Chose to skip both non-client blocks and zero-field client blocks, since neither has anything meaningful to assert type-safety about. B3: only resolve the endpoint's input (query params / ctx.req.json()) when the endpoint declares an input schema. Previously the router-set fix accidentally read the request body unconditionally, so a handler with no input schema that parses the request itself hit ERR_BODY_ALREADY_USED. B4: run response/error bodies in client-mode api blocks through eraseFunctionTypes, matching every other browser-bound body in client-codegen.ts, so a TypeScript-only construct inside one (e.g. an annotated locally-declared function) doesn't reach the .mjs artifact. B5: only exclude "api" from state/prop destructuring in the generated browser module when the page actually has client-mode api blocks (i.e. there is a real `api` binding to shadow). Previously "api" was always excluded, so a page with `state api` and no api blocks got an undeclared `api` reference (ReferenceError) in client code. B6: prefix each emitted assertion with `export`, so it isn't flagged as an unused local under a downstream project's noUnusedLocals (TS6196). B7: wrnexusCallApi now resolves with undefined for an ok 204/205 response, or an ok response with an empty/unparseable body, instead of rejecting with "Response was not valid JSON" -- matching the spec's failure table (error path only for non-2xx, network failure, or an actually unparseable body on a non-empty response). Regenerated examples/basic-app's generated types and editor bundles to match. Confirmed the example's type gate still fails when an unaccepted field is added to a request body, and passes cleanly otherwise. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
basic-app
The reference app for WrNexus. Demonstrates every MVP feature.
app/
pages/index.wrn -> GET / (SSR + two counter components w/ props)
pages/about.wrn -> GET /about (pure SSR, zero JS)
pages/reactive.wrn -> GET /reactive (reactive directives, no component)
pages/hello.wrn -> GET /hello (.wrn language, compiled reactive page)
api/hello.ts -> GET /api/hello
api/echo.ts -> GET|POST /api/echo
middleware/auth.ts -> runs first (alphabetical)
middleware/logger.ts -> runs second
realtime/chat.ts -> ws /realtime/chat
components/counter.wrn -> server-rendered component: data-component="counter"
styles/global.css -> global stylesheet -> /__wrnexus/styles.css (every page)
public/
favicon.ico -> framework default if this file is absent
robots.txt -> GET /robots.txt
site.webmanifest -> GET /site.webmanifest
wrnexus.config.ts -> global SEO + head injection + CSS processor + security/CORS config
wrnexus.config.ts shows global SEO defaults, how to use a CSS framework via CDN
(head), or a real Tailwind/PostCSS build (styles.process). It also enables
example CORS origins and documents the default security headers. To use an npm
framework, @import it in app/styles/global.css.
app/pages/hello.wrn demonstrates a page-level .wrn seo block plus direct
.wrn access to cookies, session, and the CSR localStorage snapshot.
Run from the repo root:
bun install
bun run dev # serves this app at http://localhost:3000