12 Commits

Include renames

Author	SHA1	Message	Date
ClintchizandClaude Opus 5	55fed2177a	fix(compiler): strip TypeScript from client function bodies ... `wrnexus build` failed on any client function whose body used TypeScript: const requestBody: Record<string, unknown> = {} error: Expected ";" but found ":" Codegen copies a client function's body into the browser module verbatim. It removes the types from the function's *signature*, which is what made this easy to miss -- the emitted module looked transpiled, and only bodies carried types through. The artifact is written as .mjs and read back as plain JavaScript, so the failure surfaced as a syntax error in generated code rather than at the .wrn line responsible. Browser modules are now transpiled before they are written, at all three sites that emit one (the production build and both dev-server paths). Reproduced end to end: a page with an annotated body failed the build with the reported errors, and after the fix builds, ships valid minified JS, and runs -- the handler sets its state correctly in a browser. Note: the same body is also embedded as a string for the CSP-safe fallback interpreter, which still receives it untranspiled. The compiled module shadows the fallback, so this is only reachable in the window before that module loads. Left alone here because stripping it lives in codegen, which also runs under Node in the editor bundle where the Bun transpiler is unavailable. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-08-19 14:03:14 +05:30
ClintchizandClaude Opus 5	17aa3b98eb	feat(islands): wire islands end to end ... The island pieces existed but nothing connected .wrn compilation to island emission. Now: - codegen emits a data-wrn-island placeholder for component tags bound to .tsx imports, keeping .wrn components on the normal mount path - the dev pipeline and static build resolve island imports, thread the names into codegen, and build the bundles - collectScripts adds /__wrnexus/islands.js only when island markup is present, so island-free pages still ship nothing - island routes classify as static-interactive via hasIslands Three bugs found by driving a real page in the browser: 1. The mount runtime was never built anywhere, so the bootstrap 404'd and no island mounted. 2. Building the runtime separately from the islands gave each its own copy of React: "Cannot read properties of null (reading 'useState')". The runtime is now an entrypoint of the same build so React stays in one shared chunk. The existing single-React test only compared bundles within one build and could not see across build boundaries. 3. Island props arrived as attribute strings, so start={3} was "3" and incrementing produced "31" then "311". Props now follow JSX semantics: {…} parses as JSON, quoted values stay strings, and a runtime expression is a WRN-ISLAND-PROPS build error rather than a silent wrong value. island-codegen.ts no longer imports @wrnexus/core. Compiler modules are bundled into the Node-only VS Code extension, which contains no other packages, so a runtime import of core broke the editor compiler; the two helpers are implemented locally and the core dependency is dropped again. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-08-18 16:16:03 +05:30
Clintchiz	2c960fc1dc	refactor: migrate legacy wire namespace to wrn	2026-08-12 18:51:15 +05:30
Clintchiz	586a6db8ff	release: WRNexusJS 0.8.0	2026-08-02 23:18:51 +05:30
Clintchiz	87507edf59	release: WRNexusJS 0.7.0	2026-08-01 10:04:42 +05:30
Clintchiz	687d345882	release: WRNexusJS 0.6.0	2026-08-01 01:09:58 +05:30
Clintchiz	30e5721e84	release: WRNexusJS 0.4.0	2026-07-27 12:42:18 +05:30
Clintchiz	c81dedff17	release: WRNexusJS 0.3.5	2026-07-24 12:46:44 +05:30
Clintchiz	07d8fb59d6	release: WRNexusJS 0.3.0	2026-07-22 17:29:08 +05:30
Clintchiz	94ae40d8bd	feat: add typed WRN declarations	2026-07-19 18:44:27 +05:30
Clintchiz	9ca1cc6b0f	release: WRNexusJS 0.2.49	2026-07-18 19:33:57 +05:30
Clintchiz	ee98026cc5	first commit	2026-07-12 15:55:18 +05:30