@aparte/core 0.16.4 → 0.16.6

package/dist/types/element-attributes.d.ts

@@ -15,12 +15,18 @@ export type * from '../generated/element-attributes.js';
  * One attribute as a TEMPLATE must write it.
  *
  * A presence attribute becomes `'' | undefined`, never `boolean`, and that is not
- * pedantry — it is the same trap in all three template languages. React, Vue and Svelte
- * all stringify what they set on a custom element, so `disabled={false}` renders
+ * pedantry — it is the same trap in all three template languages. React and Vue
+ * stringify what they set on a custom element, so `disabled={false}` renders
  * `disabled="false"`, and an element that tests `hasAttribute` reads that as ON. The
  * wrapper's own bubble rendering already used the right spelling
  * (`streaming={… ? '' : undefined}`); this makes it the only one that type-checks.
  *
+ * Svelte 5 is the caveat that shaped the SETTERS (#62): it assigns the PROPERTY
+ * whenever the element has a setter for it (`set_custom_element_data` checks
+ * `get_setters(node)`), so an accessor-backed presence attribute receives the `''`
+ * this union promises as a property value. Every presence setter therefore treats
+ * `''` as ON (`presenceOn` in utils/presence.ts) — one spelling, both paths.
+ *
  * `null` is in the union alongside `undefined` because all three treat it as REMOVE,
  * and Vue's own wrapper template writes exactly that (`:streaming="… ? '' : null"`).
  * Leaving it out made the wrapper's own code fail to type-check — the second time the

package/dist/types/element-attributes.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"element-attributes.d.ts","sourceRoot":"","sources":["../../src/types/element-attributes.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;GAWG;AACH,mBAAmB,oCAAoC,CAAC;AAExD;;;;;;;;;;;;;;;;;;;;;;GAsBG;AACH,MAAM,MAAM,eAAe,CAAC,CAAC,IAAI,CAAC,SAAS,OAAO,GAAG,EAAE,GAAG,IAAI,GAAG,SAAS,GACpE,CAAC,SAAS,MAAM,GAAG,MAAM,GAAG,MAAM,GAClC,CAAC,CAAC;AAER,4FAA4F;AAC5F,MAAM,MAAM,mBAAmB,CAAC,CAAC,IAAI;KAAG,CAAC,IAAI,MAAM,CAAC,CAAC,CAAC,EAAE,eAAe,CAAC,WAAW,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC;CAAE,CAAC"}
+{"version":3,"file":"element-attributes.d.ts","sourceRoot":"","sources":["../../src/types/element-attributes.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;GAWG;AACH,mBAAmB,oCAAoC,CAAC;AAExD;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA4BG;AACH,MAAM,MAAM,eAAe,CAAC,CAAC,IAAI,CAAC,SAAS,OAAO,GAAG,EAAE,GAAG,IAAI,GAAG,SAAS,GACpE,CAAC,SAAS,MAAM,GAAG,MAAM,GAAG,MAAM,GAClC,CAAC,CAAC;AAER,4FAA4F;AAC5F,MAAM,MAAM,mBAAmB,CAAC,CAAC,IAAI;KAAG,CAAC,IAAI,MAAM,CAAC,CAAC,CAAC,EAAE,eAAe,CAAC,WAAW,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC;CAAE,CAAC"}

package/dist/utils/presence.d.ts

@@ -0,0 +1,16 @@
+/**
+ * What a presence-attribute SETTER makes of what it was handed (#62).
+ *
+ * The generated attribute types map a presence attribute to `'' | null | undefined`,
+ * because React and Vue stringify what they set on a custom element — so `''` is the
+ * documented spelling for ON. Svelte 5 does not take the attribute path: it assigns
+ * the PROPERTY whenever the element has one, which handed these setters the `''` the
+ * types promised — and `toggleAttribute(name, '')` reads an empty string as falsy, so
+ * the attribute was REMOVED. The opposite of what the template asked for, silently.
+ *
+ * One rule fixes both paths without forking the spelling: on a presence property, an
+ * empty string means ON, exactly as an empty attribute does. Everything else keeps
+ * JavaScript's own truthiness (`false`, `null`, `undefined` → OFF).
+ */
+export declare function presenceOn(value: unknown): boolean;
+//# sourceMappingURL=presence.d.ts.map

package/dist/utils/presence.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"presence.d.ts","sourceRoot":"","sources":["../../src/utils/presence.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;GAaG;AACH,wBAAgB,UAAU,CAAC,KAAK,EAAE,OAAO,GAAG,OAAO,CAElD"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@aparte/core",
-  "version": "0.16.4",
+  "version": "0.16.6",
   "description": "AI chat in Web Components, with the agent loop inside — zero third-party dependencies",
   "type": "module",
   "//sideEffects": "The BROWSER entry defines the custom elements and imports CSS at module scope, so it must never be tree-shaken; the Node entry (`index.node`) and every other module are pure. Listing them explicitly is what lets a bundler drop the rest — the whole package was implicitly side-effectful before, the only one of the 14 without this field.",
@@ -52,7 +52,7 @@
     "node": ">=18"
   },
   "dependencies": {
-    "@aparte/engine": "0.16.4"
+    "@aparte/engine": "0.16.6"
   },
   "devDependencies": {
     "@custom-elements-manifest/analyzer": "^0.11.0",
@@ -66,7 +66,21 @@
     "chat",
     "ai",
     "streaming",
-    "llm"
+    "llm",
+    "chat-ui",
+    "ai-chat",
+    "chatbot",
+    "chat-component",
+    "custom-elements",
+    "framework-agnostic",
+    "react",
+    "vue",
+    "svelte",
+    "angular",
+    "agent",
+    "tool-calling",
+    "human-in-the-loop",
+    "openai"
   ],
   "license": "MIT",
   "repository": {