@fusion.dev/helix-core 0.174.0 → 0.176.0

package/custom-elements.json

@@ -27552,7 +27552,7 @@
               }
             }
           ],
-          "description": "Draws an icon that was imported by name, rather than looked up by string.\n\n**`<helix-icon name=\"play\">` looks its glyph up in a registry at runtime.**\nThe registry holds the whole set once `@fusion.dev/helix-headless/icon`\nregisters it, and no bundler can shake a lookup by string, so every consumer\nof any component that renders one ships all of the generated path data: measured at 50,814 bytes raw and 15,010 gzipped for 102 icons, and\ngrowing about 147 gzipped bytes per icon added. A named import ships one path\nand is checked when the package compiles rather than by a name lookup later.\n\nThat element still earns its place as *public* API, where a consumer writes a\nname in markup and a lookup is the only thing that can work, and\n`@fusion.dev/helix-headless/icon/root` names glyphs without registering the\nset. What it should not be is how this library draws its own marks.\n\n**There is no `part` option, and there cannot be.** A part name behind an\ninterpolation is a part the manifest cannot see, so the component's own\nstylesheet matches nothing and the part stops being\nAPI. `Trend` needs one and therefore writes its `<svg>` out with a literal\n`part=\"icon\"`, which is the honest cost: a helper can carry everything except\nthe thing static analysis has to read.\n\n`data-glyph` rather than a class, because the sizing lives in\n`helix/styled/src/shared/glyph/glyph.css` and a component's own `--icon-size`\ndeclarations have to keep working untouched: the variable was read by\n`helix-icon`, and now it is read by the rule that sheet carries. Without it\nevery one of those declarations would go quietly dead and every mark in six\nfamilies would change size."
+          "description": "Draws an icon that was imported by name, rather than looked up by string.\n\n**`<helix-icon name=\"play\">` looks its glyph up in a registry at runtime.**\nThe registry holds the whole set once `@fusion.dev/helix-headless/icon/all`\nregisters it, and no bundler can shake a lookup by string, so every consumer\nof any component that renders one ships all of the generated path data: measured at 50,814 bytes raw and 15,010 gzipped for 102 icons, and\ngrowing about 147 gzipped bytes per icon added. A named import ships one path\nand is checked when the package compiles rather than by a name lookup later.\n\nThat element still earns its place as *public* API, where a consumer writes a\nname in markup and a lookup is the only thing that can work, and\n`@fusion.dev/helix-headless/icon/root` names glyphs without registering the\nset. What it should not be is how this library draws its own marks.\n\n**There is no `part` option, and there cannot be.** A part name behind an\ninterpolation is a part the manifest cannot see, so the component's own\nstylesheet matches nothing and the part stops being\nAPI. `Trend` needs one and therefore writes its `<svg>` out with a literal\n`part=\"icon\"`, which is the honest cost: a helper can carry everything except\nthe thing static analysis has to read.\n\n`data-glyph` rather than a class, because the sizing lives in\n`helix/styled/src/shared/glyph/glyph.css` and a component's own `--icon-size`\ndeclarations have to keep working untouched: the variable was read by\n`helix-icon`, and now it is read by the rule that sheet carries. Without it\nevery one of those declarations would go quietly dead and every mark in six\nfamilies would change size."
         }
       ],
       "exports": [
@@ -33810,7 +33810,7 @@
           "type": {
             "text": "string"
           },
-          "default": "'0.174.0'",
+          "default": "'0.176.0'",
           "description": "The version of the package this file ships in.\n\n**Written by `fusion/scripts/version.mjs`** wherever it writes the package's\n`package.json`, and stamped back into the repository beside it after a\nrelease, so the two never disagree; a spec beside this holds them to it.\nNothing else in the running code knows which release it is."
         }
       ],
@@ -34370,6 +34370,6 @@
   ],
   "helix": {
     "package": "@fusion.dev/helix-core",
-    "version": "0.174.0"
+    "version": "0.176.0"
   }
 }

package/dist/utils/draw-icon/draw-icon.d.ts

@@ -11,7 +11,7 @@ export interface DrawIconOptions {
  * Draws an icon that was imported by name, rather than looked up by string.
  *
  * **`<helix-icon name="play">` looks its glyph up in a registry at runtime.**
- * The registry holds the whole set once `@fusion.dev/helix-headless/icon`
+ * The registry holds the whole set once `@fusion.dev/helix-headless/icon/all`
  * registers it, and no bundler can shake a lookup by string, so every consumer
  * of any component that renders one ships all of the generated path data: measured at 50,814 bytes raw and 15,010 gzipped for 102 icons, and
  * growing about 147 gzipped bytes per icon added. A named import ships one path

package/dist/utils/report-runtime/report-runtime.d.ts

@@ -93,6 +93,8 @@ export type RuntimeKind =
  | 'unlinked-trigger'
 /** A Text is rendered as a label, a deprecated value whose shadow root reaches no control. */
  | 'unreachable-label'
+/** A part with an entry of its own is in the page and its entry was never imported, so it does nothing. */
+ | 'unregistered-part'
 /** A QR code holds a logo at a correction level below `H`, so it may not scan. */
  | 'unscannable-logo'
 /** A virtualized list's box has no height of its own, so its window never settles. */
@@ -101,7 +103,7 @@ export type RuntimeKind =
  | 'untold-toggle'
 /** A slotted trigger is a plain element, which cannot be told it opens something. */
  | 'untold-trigger'
-/** A tooltip wraps its trigger, so its text reaches no screen reader. */
+/** A tooltip wraps a trigger that does not name it, and opened before a reader reached the trigger. */
  | 'wrapped-trigger';
 /** One event: what went wrong, where, and the sentence that says what to do. */
 export interface RuntimeEvent {

package/dist/version.d.ts

@@ -6,4 +6,4 @@
  * release, so the two never disagree; a spec beside this holds them to it.
  * Nothing else in the running code knows which release it is.
  */
-export declare const VERSION = "0.174.0";
+export declare const VERSION = "0.176.0";

package/dist/version.js

@@ -1 +1 @@
-export const VERSION = '0.174.0';
+export const VERSION = '0.176.0';

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@fusion.dev/helix-core",
   "description": "Helix element primitives: base classes, mixins, decorators, utilities.",
-  "version": "0.174.0",
+  "version": "0.176.0",
   "license": "MIT",
   "author": "Ross Sheppard <ross.sheppard@fusion.dev>",
   "repository": {
@@ -62,11 +62,11 @@
   "bugs": "https://github.com/project-fusion/fusion/issues",
   "dependencies": {
     "@floating-ui/dom": "^1.8.0",
-    "@fusion.dev/helix-icons": "0.174.0"
+    "@fusion.dev/helix-icons": "0.176.0"
   },
   "devDependencies": {
-    "@fusion.dev/helix-cem": "0.174.0",
-    "@fusion.dev/helix-testing": "0.174.0",
+    "@fusion.dev/helix-cem": "0.176.0",
+    "@fusion.dev/helix-testing": "0.176.0",
     "@lit-labs/ssr": "^4.1.0",
     "lit": "^3.2.1"
   },