6 Commits

Include renames

Author	SHA1	Message	Date
Clintchiz	e372ae571a	chore: harden release checks and package coverage	2026-08-24 11:36:13 +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
ClintchizandClaude Opus 5	442a3106ed	test(islands): guard zero-JS routes and single-React bundling ... Two guards protect the core promise: a route with no islands emits no assets at all, and a page with several islands keeps React in one shared chunk. buildIslands now writes a generated entry per island instead of passing component sources directly. Two islands sharing a source deduped to a single entrypoint, and output order is not guaranteed to match input order, so island names could bind to the wrong bundle. Island modules are excluded from the editor compiler bundle: it globs packages/compiler/src, and island-bundle.ts calls Bun.build while island-codegen.ts imports @wrnexus/core — neither belongs in a Node-only VS Code artifact. Integration assertions share one build. bun test interferes with Bun.build's module reads after several build calls in one process, while the same calls succeed repeatedly outside the runner; production is unaffected. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-08-18 15:50:26 +05:30
Clintchiz	4cebacadfe	release: WRNexusJS 0.8.3	2026-08-03 19:47:30 +05:30
Clintchiz	586a6db8ff	release: WRNexusJS 0.8.0	2026-08-02 23:18:51 +05:30
Clintchiz	07d8fb59d6	release: WRNexusJS 0.3.0	2026-07-22 17:29:08 +05:30