create-foldkit-app 0.22.1 → 0.23.0

package/README.md

@@ -39,7 +39,7 @@ The CLI prompts you for a project name, starter example, and package manager. Pa
 | `generative-art`         | Perlin-noise flow field with evolving particle trails, mouse vortex, and high-frequency Messages       |
 | `auth`                   | Authentication with Submodels, OutMessage, and protected routes                                        |
 | `shopping-cart`          | Complex state management with nested Models and routing                                                |
-| `checkout-machine`       | Experimental state machine checkout with guarded branches and edge Commands                            |
+| `state-machine`          | Experimental state machine checkout with guarded branches and edge Commands                            |
 | `pixel-art`              | Pixel editor with undo/redo, UI components, and localStorage persistence                               |
 | `websocket-chat`         | Managed resources with WebSocket integration                                                           |
 | `managed-resource-layer` | Layer-backed ManagedResource lifecycle with an Effect service                                          |

package/dist/examples.js

@@ -19,7 +19,7 @@ export const EXAMPLE_VALUES = [
     'generative-art',
     'auth',
     'shopping-cart',
-    'checkout-machine',
+    'state-machine',
     'pixel-art',
     'websocket-chat',
     'managed-resource-layer',
@@ -131,8 +131,8 @@ export const examples = [
         description: 'Complex state management with nested models and routing',
     },
     {
-        value: 'checkout-machine',
-        title: 'checkout-machine',
+        value: 'state-machine',
+        title: 'state-machine',
         description: 'Checkout workflow powered by the experimental state machine module with guarded branches and edge Commands',
     },
     {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-foldkit-app",
-  "version": "0.22.1",
+  "version": "0.23.0",
   "description": "Create Foldkit applications",
   "type": "module",
   "main": "./dist/index.js",
@@ -12,15 +12,15 @@
     "templates"
   ],
   "dependencies": {
-    "@effect/platform-node": "4.0.0-beta.101",
-    "@effect/platform-node-shared": "4.0.0-beta.101",
+    "@effect/platform-node": "4.0.0-beta.102",
+    "@effect/platform-node-shared": "4.0.0-beta.102",
     "chalk": "^5.6.2",
-    "effect": "4.0.0-beta.101",
+    "effect": "4.0.0-beta.102",
     "rimraf": "^6.1.3",
     "typescript": "^6.0.3"
   },
   "devDependencies": {
-    "@effect/vitest": "4.0.0-beta.101",
+    "@effect/vitest": "4.0.0-beta.102",
     "@types/node": "^25.9.3",
     "vitest": "^4.1.9"
   },

package/templates/base/AGENTS.md

@@ -52,7 +52,7 @@ Use `evo()` from `foldkit/struct` for immutable model updates. Never spread or `
 
 ### View
 
-Bind the `html` factory inside each view function with `const h = html<Message>()` (never at module level), then reach for `h.div`, `h.OnClick`, etc. off the returned record. Use `empty` (not `null`) for conditional rendering, `M.value().pipe(M.tagsExhaustive({...}))` for discriminated unions, and `Array.match` for lists that may be empty.
+Every view receives `h`, the typed Html builder, as its last parameter (`view: (model, h) => ...`; `Submodel.defineView` passes the child's own). Never construct a builder; reach for `h.div`, `h.OnClick`, etc. off the parameter, and give extracted view helpers an `h: HtmlBuilder<Message>` last parameter that callers thread through. Only where no builder is in scope, typically module scope, use `inertHtml` from `foldkit/html`, aliased `ih` so the two builders stay distinguishable. Use `h.empty` (not `null`) for conditional rendering, `M.value().pipe(M.tagsExhaustive({...}))` for discriminated unions, and `Array.match` for lists that may be empty.
 
 Keys are for mapped list items only: key each row by a stable Model identifier (`h.keyed('li')(item.id, [], [...])`), never by array position, and never derive a key from displayed data. Never key branches; the build gives each view function's output its own identity, so branch switches replace DOM automatically. When switching an inline same-tag ternary must reset DOM state, extract each arm into its own named view function.
 
@@ -84,7 +84,7 @@ Name each test file for its test style, beside the code under test: `story.test.
 - Use `Option` instead of `null` or `undefined`. Prefix Option-typed values with `maybe*`. Match with `Option.match`; don't unwrap with `Option.map(...)` + `Option.getOrElse(...)` when you can just match.
 - Use Effect modules over native methods in `pipe` chains (`Array.map`, `String.startsWith`, `Array.findFirst`). Native methods are fine when calling directly on a named variable.
 - Never cast Schema values with `as Type`. Use the callable constructor: `SucceededLogin({ sessionId })`, not `{ _tag: 'SucceededLogin', sessionId } as Message`.
-- Always `Array.isEmptyArray` / `Array.isNonEmptyArray` (not `.length === 0`). Use `Array.match` when handling both empty and non-empty cases.
+- Always `Array.isArrayEmpty` / `Array.isArrayNonEmpty` (not `.length === 0` / `.length > 0`). Use `Array.match` when handling both empty and non-empty cases.
 - Never use `for` loops or `let` for iteration. Reach for `Array.map`, `Array.filterMap`, `Array.makeBy`, `Array.reduce`.
 - Never use `T[]`. Always `Array<T>` or `ReadonlyArray<T>`.
 - Always use `Effect.Match`, never `switch`.