ClintchizandClaude Opus 5
c7ab605e85
Section, SectionHeader and PublicPageShell move onto wire-* classes with local style blocks, variants as data attributes. SectionHeader loses 38 utility lines, and Section stops spending one line per variant and colour pairing: tinted and solid now select on two attributes. PageHeader was already on the convention and only needed the audit. examples/basic-app/app/pages/layout.wrn composes the whole set into one page. Building it surfaced a library-wide bug. Ten custom properties were referenced by components and defined by nothing: --wire-color-focus, --wire-color-surface-soft, --wire-color-on-danger, --wire-color-surface-subtle and the input-* family, plus hover and contrast for every semantic colour except primary and secondary. An undefined custom property does not warn, it resolves to nothing, so focus rings drew with no colour and every soft surface rendered transparent -- 27 components referenced surface-soft alone. They are derived in the theme now, and a test checks every token a component references against the rendered theme CSS rather than the source, since most are generated. The semantic spread also had to move ahead of the primary and secondary entries so the palette keeps winning for those two. Known and unresolved: LayoutSplitter emits its sizeChange output and the component does fire it, but a parent binding on the tag is not invoked. The tour page therefore points at the handle aria-valuenow rather than wiring a handler that would never update. Outputs work elsewhere, so this is narrower than an outputs-are-broken problem and needs its own investigation. 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