@hanzo/ui 8.25.3 → 8.25.5

package/dist/gallery.html

@@ -1,4 +1,4 @@
-<!doctype html><html lang="en" class="t_dark"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>@hanzo/ui 8.25.3</title><style>/* @hanzo/ui — generated by scripts/gen-css.mjs. Do not edit. */
+<!doctype html><html lang="en" class="t_dark"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>@hanzo/ui 8.25.5</title><style>/* @hanzo/ui — generated by scripts/gen-css.mjs. Do not edit. */
 :root { --hanzo-ui-styles: 1; }
 /* Hanzo Design System — the entry point. Import THIS one file.
  *

package/dist/next.cjs

@@ -36,6 +36,11 @@ const { join } = require('node:path')
  * The registry is named separately because it is the one module react-native-web
  * does not answer to under the same path — an `Image` reaches for
  * `@react-native/assets-registry/registry` and finds nothing.
+ *
+ * Both are module specifiers, resolved from the app. Turbopack reads an absolute
+ * path as a relative one and reports it back with a `./` in front, so the app is
+ * the one that has to see `react-native-web` — every web app on this stack
+ * declares it, the same way it declares react-dom.
  */
 const ALIAS = {
   'react-native': 'react-native-web',

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hanzo/ui",
-  "version": "8.25.3",
+  "version": "8.25.5",
   "type": "module",
   "description": "Hanzo UI — the one canonical Hanzo component library, on @hanzo/gui + @hanzo/design. ONE substrate: every component renders through @hanzo/gui primitives, so the same import works on web, native (expo) and desktop (Tauri). Self-contained (theme.css), presentational, host-agnostic, clean-room.",
   "exports": {