kopular 0.11.1 → 0.11.3

package/LLM.md

@@ -425,6 +425,34 @@ class CounterService {
 }
 ```
 
+## Common mistakes (seeded from real generation failures)
+
+- **`Router.Param` is a plain `string`, not `state<T>` — don't `Subscribe()` to it.** A
+  `state<T>`-based design for it was tried and genuinely crashes: `Navigate()` sets `Param`
+  *before* the newly-matched page finishes mounting, so a page `Subscribe`-ing to it fires
+  while its own `Update()` still has no `ParentElement` to `replaceChild` into. `Render()`
+  already re-reads the fresh `Param` on every navigation with no extra step — just read
+  `this.Nav.Param` directly inside `Render()`.
+- **Deploying a `Router`-based app needs SPA/history-fallback configured on the actual host**
+  — this bit the real `KopularDemo` production site (worked when navigated to via a link,
+  404'd on a direct refresh) before its Cloudflare Workers config had
+  `not_found_handling: "single-page-application"` set. Don't assume `ks build`/`npm run
+  build` alone is enough for a routed app to work on refresh at a non-root path — see
+  "Router" above for the exact config.
+- **Cross-package consumption always goes through `extern`, never `using`.** `using
+  "kopular/component"` doesn't compile — `using` only resolves relative same-project paths.
+  Redeclare the members you need as `extern ... from "kopular/component"` instead (see
+  "Consuming Kopular from your own KopScript project" above) even though it looks like it
+  should "just work" the way an npm `import` would.
+- **A template's `*if`/`*for` and the hand-written `If()`/`.ForEach()` helpers are two
+  independent mechanisms, not the same thing wired two ways** — a template never needs
+  `directives.ks`'s `If()` imported or called; `*if`/`*for` compile to real `if`/`for`
+  directly. Don't mix a template with a hand-written-`Render()` helper call.
+- **No two-way binding, anywhere.** Wiring a template's `[value]` or a hand-written
+  `.Value` to a real `<input>` back and forth always needs an explicit
+  `addEventListener("input", ...)` — there's no `[(ngModel)]`-equivalent to reach for in
+  either authoring style.
+
 ## Does not exist
 
 DI container/injector · decorators (`@Injectable`, `@Component`, ...) · a runtime
@@ -432,5 +460,9 @@ template engine or interpreted expression language — templates compile to the
 imperative `Render()` code as the hand-written form, checked at compile time, not
 interpreted at runtime (see "Templates" above) · two-way binding (`[(ngModel)]`) ·
 vdom diffing / reconciliation beyond a single component's own re-render · pipes ·
-animations · forms/validation module · typed/generic HTTP responses (`Http` returns raw
-text — see above) · a CLI/scaffolding tool (`ng generate`-equivalent) · SSR.
+animations · typed/generic HTTP responses (`Http` returns raw text — see above) · SSR.
+
+(`FormField<T>`/`Validators` and `kp new` — see "FormField<T> / Validators" and "Starting
+a new project" above — are real, shipped features; they used to be listed here as gaps
+before those landed and this list wasn't updated at the time. Leaving this parenthetical
+rather than quietly deleting it, as a reminder to keep this list in sync going forward.)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "kopular",
-  "version": "0.11.1",
+  "version": "0.11.3",
   "description": "Kopular: a small component framework for KopScript — components, reactive state, constructor-injected services, routing, real compiled templates, and HTTP, with no DI container",
   "type": "module",
   "license": "MIT",