@vectoriox/iox-builder 4.22.0 → 4.24.0

package/index.d.ts

@@ -205,8 +205,13 @@ declare const ACTION_TYPE_OPTIONS: {
 declare const EASING_OPTIONS: string[];
 /**
  * A named, reusable collection of CSS style properties stored at the org level.
- * Elements reference a preset by `stylePresetId`. At render time the engine
- * merges `preset.styleProps → element.styleOverrides` so local overrides win.
+ * Elements reference a preset by `stylePresetId` — but a preset is an AUTHORING
+ * convenience only: on save the builder flattens `{...preset.styleProps,
+ * ...node.styleOverrides}` into `node.styleProps`, and the SSR engine never
+ * resolves a preset (it has no `stylePresetId` reader at all). An earlier
+ * version of this comment claimed the engine merges presets at render time —
+ * it does not, which is exactly why a re-theme must travel through design
+ * TOKENS, never through presets. See style-presets.md and the flavors plan §2b.
  */
 interface StylePreset {
     id: string;
@@ -1151,7 +1156,7 @@ declare class StyleRegistryService {
      * (e.g., `{ 'iox-primary-color': '#cb9090' }`).
      * Pass an empty object to clear all tokens.
      */
-    upsertTokens(tokens: Record<string, string>): void;
+    upsertTokens(tokens: Record<string, string>, darkTokens?: Record<string, string>): void;
     remove(nodeId: string): void;
     destroy(): void;
     private compile;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vectoriox/iox-builder",
-  "version": "4.22.0",
+  "version": "4.24.0",
   "peerDependencies": {
     "@angular/common": ">=20.0.0",
     "@angular/core": ">=20.0.0",