@lokascript/framework 7.3.0 → 7.4.0

package/CHANGELOG.md

@@ -7,6 +7,46 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [7.4.0] - 2026-10-21
+
+Content htmx or fixi swaps in runs its hyperscript, as it does on upstream `_hyperscript`: the
+engine has upstream's htmx integration in every bundle, and loading the engine twice no longer
+binds every handler twice. A minor: new behavior and a deprecated option, nothing removed.
+
+### Fixed
+
+- **`@hyperfixi/engine`: content htmx or fixi swaps in runs its hyperscript, and htmx content a
+  script puts in issues its requests.** Upstream `_hyperscript` has this integration in its core
+  runtime and the engine had none: a `_="on click …"` that htmx swapped in did nothing, and an
+  `hx-get` that a script `put` into the page was never wired. The engine now has upstream's
+  integration (0.9.93's `htmx-compat.js`), installed by `boot()` in every bundle, the Vite
+  plugin's included: `htmx:load` (htmx 2) and `htmx:after:process` (htmx 4) process the content,
+  an after-process hook hands what a script inserts to `htmx.process`, and on htmx 4 it
+  registers upstream's `hs-include` extension (`hs-include=":id"` sends element-scoped variables
+  with the request; `htmx.config.extensions = "hs-include"` enables it). Two additions upstream
+  lacks: fixi (`fx:swapped` processes the swapped content), and pages with their own hooks
+  between the two (`htmx.onLoad(el => _hyperscript.process(el))`,
+  `_hyperscript.addAfterProcessHook(el => htmx.process(el))`, the workarounds until now) no longer
+  recurse, where upstream recurses until the stack runs out. The workarounds can be removed. The
+  first vendoring of upstream's suite left out its htmx tests (`integration/htmx.js`,
+  `ext/hs-include.js`), which is how the gap shipped; the gate now runs them and passes all 19
+  (1422/1486). `hyperfixi-hs.js` grows 0.7 KB gzipped, to 34.9 KB.
+- **`@hyperfixi/engine`: loading the engine twice no longer binds every handler twice.** Element
+  state was private to each copy of the engine, so the second copy initialised every element
+  again and one click ran its handler twice. htmx 4's boosted swaps run body scripts again, so
+  boost, then back, did it on a page that loads the engine at the end of its body. The state is
+  now `elt._hyperscript`, where upstream keeps it and a second copy finds it (two more of
+  upstream's tests pass).
+- **Examples: sortable-list's Add Task added a blank task and threw.** Its script read the input
+  with `first #new-item-input`, which is null (`first` of one element), and now reads the element
+  itself. tell-command's code sample shows its `on click`.
+
+### Deprecated
+
+- **`@hyperfixi/vite-plugin`'s `htmx` option does nothing.** It added a listener for htmx 2's
+  event names, which htmx 4 does not fire; the engine's integration covers every bundle. The
+  option is still accepted, so existing configs build.
+
 ## [7.3.0] - 2026-10-21
 
 `@hyperfixi/mcp-server` lists its 14 core tools by default and keeps the other 70 in toolsets

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lokascript/framework",
-  "version": "7.3.0",
+  "version": "7.4.0",
   "description": "Generic framework for building multilingual DSLs with semantic parsing and grammar transformation",
   "type": "module",
   "main": "dist/index.cjs",
@@ -220,7 +220,7 @@
   "author": "LokaScript Contributors",
   "license": "MIT",
   "dependencies": {
-    "@lokascript/intent": "^7.3.0"
+    "@lokascript/intent": "^7.4.0"
   },
   "devDependencies": {
     "@lokascript/domains": "^7.1.0",