kopular 0.21.1 → 0.21.2

package/LLM.md

@@ -169,6 +169,28 @@ FormField<string> email = new FormField<string>("", (string v) => Validators.Ema
 `{ get; }`) — `extern class` supports a plain field declaration for exactly this case,
 not just get/set accessor pairs.
 
+`Computed1`/`Computed2`/`Resource<T>` (needs `kopscript >= 0.24.0` for `extern enum`,
+which `AsyncStatus` requires):
+
+```ks
+extern class Computed1<A, R> {
+  constructor(state<A> source, (A) => R compute);
+  state<R> Value;
+} from "kopular/computed";
+extern class Computed2<A, B, R> {
+  constructor(state<A> a, state<B> b, (A, B) => R compute);
+  state<R> Value;
+} from "kopular/computed";
+
+extern enum AsyncStatus { Loading, Success, Failure } from "kopular/resource";
+extern class Resource<T> {
+  constructor(task<T> operation);
+  state<AsyncStatus> Status;
+  state<T?> Data;
+  state<string?> Error;
+} from "kopular/resource";
+```
+
 You also need your own ambient DOM `extern` block (`document`, `Element`, `Event`, ...) —
 Kopular's own copy in `dom.ks` isn't reachable across the package boundary; redeclare the
 handful of members you actually use. See KopularDemo's `src/kopular_bindings.ks` for a

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "kopular",
-  "version": "0.21.1",
+  "version": "0.21.2",
   "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",
@@ -62,7 +62,7 @@
     "@types/jsdom": "^30.0.0",
     "@types/node": "^20.14.0",
     "jsdom": "^25.0.1",
-    "kopscript": "^0.23.0",
+    "kopscript": "^0.24.0",
     "typescript": "^5.5.0",
     "vitest": "^4.1.11"
   },