@hanzo/ui 8.1.17 → 8.1.18

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (7) hide show
  1. package/dist/backends/gui/screen.cjs +11 -6
  2. package/dist/backends/gui/screen.d.ts +11 -6
  3. package/dist/backends/gui/screen.d.ts.map +1 -1
  4. package/dist/backends/gui/screen.js +11 -6
  5. package/dist/backends/gui/screen.js.map +1 -1
  6. package/dist/gallery.html +1 -1
  7. package/package.json +1 -1
package/dist/backends/gui/screen.cjs CHANGED
@@ -26,12 +26,17 @@ const jsx_runtime_1 = require("react/jsx-runtime");
26
26
  * clip built in, and a caller cannot forget a thing it does not have to write.
27
27
  *
28
28
  * WHY NOT CSS GRID, which expresses this as one line — `grid-template-rows: auto
29
- * 1fr auto` — with no escape hatch at all: because this package's premise is that
30
- * one import runs on web AND native, and React Native lays out through Yoga,
31
- * which implements flexbox and has no grid. That is not a gap a fork can close;
32
- * Yoga is the native runtime's engine. Grid is right where the target is a
33
- * browser, and `Grid` exists for that. A shell has to work on both, so it is
34
- * flexbox on the inside and neither caller has to know.
29
+ * 1fr auto` — with no escape hatch at all: because React Native lays out through
30
+ * Yoga, and Yoga ships flexbox only. That is a gap a fork CAN close — Yoga is
31
+ * open-source C++, and an experimental patch adds a real `YGDisplayGrid`
32
+ * (GridLayout.cpp, AutoPlacement.h, TrackSizing.h) with working iOS and Android
33
+ * builds, native layout rather than a webview. It is not closed here yet: the
34
+ * patch wants React Native 0.83-rc and an Expo canary, and taking it means this
35
+ * fork carries a C++ layout-engine patch rebased on every upgrade.
36
+ *
37
+ * So the reason is a pin, not a law, and `Screen` is what the shell looks like
38
+ * either way — a caller writes the same two components whether the inside is
39
+ * flexbox today or grid later. `Grid` already exists for web-only surfaces.
35
40
  */
36
41
  const gui_1 = require("@hanzo/gui");
37
42
  const slot_1 = require("./slot.cjs");
package/dist/backends/gui/screen.d.ts CHANGED
@@ -21,12 +21,17 @@
21
21
  * clip built in, and a caller cannot forget a thing it does not have to write.
22
22
  *
23
23
  * WHY NOT CSS GRID, which expresses this as one line — `grid-template-rows: auto
24
- * 1fr auto` — with no escape hatch at all: because this package's premise is that
25
- * one import runs on web AND native, and React Native lays out through Yoga,
26
- * which implements flexbox and has no grid. That is not a gap a fork can close;
27
- * Yoga is the native runtime's engine. Grid is right where the target is a
28
- * browser, and `Grid` exists for that. A shell has to work on both, so it is
29
- * flexbox on the inside and neither caller has to know.
24
+ * 1fr auto` — with no escape hatch at all: because React Native lays out through
25
+ * Yoga, and Yoga ships flexbox only. That is a gap a fork CAN close — Yoga is
26
+ * open-source C++, and an experimental patch adds a real `YGDisplayGrid`
27
+ * (GridLayout.cpp, AutoPlacement.h, TrackSizing.h) with working iOS and Android
28
+ * builds, native layout rather than a webview. It is not closed here yet: the
29
+ * patch wants React Native 0.83-rc and an Expo canary, and taking it means this
30
+ * fork carries a C++ layout-engine patch rebased on every upgrade.
31
+ *
32
+ * So the reason is a pin, not a law, and `Screen` is what the shell looks like
33
+ * either way — a caller writes the same two components whether the inside is
34
+ * flexbox today or grid later. `Grid` already exists for web-only surfaces.
30
35
  */
31
36
  import { type YStackProps } from '@hanzo/gui';
32
37
  export interface ScreenProps extends YStackProps {
package/dist/backends/gui/screen.d.ts.map CHANGED
@@ -1 +1 @@
1
- {"version":3,"file":"screen.d.ts","sourceRoot":"","sources":["../../../src/backends/gui/screen.tsx"],"names":[],"mappings":"AAEA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA6BG;AACH,OAAO,EAAU,KAAK,WAAW,EAAE,MAAM,YAAY,CAAA;AAGrD,MAAM,WAAW,WAAY,SAAQ,WAAW;CAAG;AAEnD;;;;GAIG;AACH,QAAA,MAAM,MAAM,GAAI,wBAAwB,WAAW,4CAkBlD,CAAA;AAED,MAAM,WAAW,SAAU,SAAQ,WAAW;IAC5C,6EAA6E;IAC7E,MAAM,CAAC,EAAE,OAAO,CAAA;CACjB;AAED;;;;;;;GAOG;AACH,QAAA,MAAM,IAAI,GAAI,gCAAuC,SAAS,4CAY7D,CAAA;AAED,OAAO,EAAE,MAAM,EAAE,IAAI,EAAE,CAAA"}
1
+ {"version":3,"file":"screen.d.ts","sourceRoot":"","sources":["../../../src/backends/gui/screen.tsx"],"names":[],"mappings":"AAEA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAkCG;AACH,OAAO,EAAU,KAAK,WAAW,EAAE,MAAM,YAAY,CAAA;AAGrD,MAAM,WAAW,WAAY,SAAQ,WAAW;CAAG;AAEnD;;;;GAIG;AACH,QAAA,MAAM,MAAM,GAAI,wBAAwB,WAAW,4CAkBlD,CAAA;AAED,MAAM,WAAW,SAAU,SAAQ,WAAW;IAC5C,6EAA6E;IAC7E,MAAM,CAAC,EAAE,OAAO,CAAA;CACjB;AAED;;;;;;;GAOG;AACH,QAAA,MAAM,IAAI,GAAI,gCAAuC,SAAS,4CAY7D,CAAA;AAED,OAAO,EAAE,MAAM,EAAE,IAAI,EAAE,CAAA"}
package/dist/backends/gui/screen.js CHANGED
@@ -23,12 +23,17 @@ import { jsx as _jsx } from "react/jsx-runtime";
23
23
  * clip built in, and a caller cannot forget a thing it does not have to write.
24
24
  *
25
25
  * WHY NOT CSS GRID, which expresses this as one line — `grid-template-rows: auto
26
- * 1fr auto` — with no escape hatch at all: because this package's premise is that
27
- * one import runs on web AND native, and React Native lays out through Yoga,
28
- * which implements flexbox and has no grid. That is not a gap a fork can close;
29
- * Yoga is the native runtime's engine. Grid is right where the target is a
30
- * browser, and `Grid` exists for that. A shell has to work on both, so it is
31
- * flexbox on the inside and neither caller has to know.
26
+ * 1fr auto` — with no escape hatch at all: because React Native lays out through
27
+ * Yoga, and Yoga ships flexbox only. That is a gap a fork CAN close — Yoga is
28
+ * open-source C++, and an experimental patch adds a real `YGDisplayGrid`
29
+ * (GridLayout.cpp, AutoPlacement.h, TrackSizing.h) with working iOS and Android
30
+ * builds, native layout rather than a webview. It is not closed here yet: the
31
+ * patch wants React Native 0.83-rc and an Expo canary, and taking it means this
32
+ * fork carries a C++ layout-engine patch rebased on every upgrade.
33
+ *
34
+ * So the reason is a pin, not a law, and `Screen` is what the shell looks like
35
+ * either way — a caller writes the same two components whether the inside is
36
+ * flexbox today or grid later. `Grid` already exists for web-only surfaces.
32
37
  */
33
38
  import { YStack } from '@hanzo/gui';
34
39
  import { slot } from './slot.js';
package/dist/backends/gui/screen.js.map CHANGED
@@ -1 +1 @@
1
- {"version":3,"file":"screen.js","sourceRoot":"","sources":["../../../src/backends/gui/screen.tsx"],"names":[],"mappings":"AAAA,YAAY,CAAA;;AAEZ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA6BG;AACH,OAAO,EAAE,MAAM,EAAoB,MAAM,YAAY,CAAA;AACrD,OAAO,EAAE,IAAI,EAAE,MAAM,QAAQ,CAAA;AAI7B;;;;GAIG;AACH,MAAM,MAAM,GAAG,CAAC,EAAE,QAAQ,EAAE,GAAG,KAAK,EAAe,EAAE,EAAE,CAAC,CACtD,KAAC,MAAM,OACD,IAAI,CAAC,QAAQ,CAAC;IAClB,yEAAyE;IACzE,6EAA6E;IAC7E,4EAA4E;IAC5E,wEAAwE;IACxE,0EAA0E;IAC1E,8EAA8E;IAC9E,IAAI,EAAE,CAAC,EACP,SAAS,EAAC,MAAM,EAChB,IAAI,EAAE,CAAC,EACP,KAAK,EAAC,MAAM,EACZ,QAAQ,EAAC,QAAQ,KACb,KAAK,YAER,QAAQ,GACF,CACV,CAAA;AAOD;;;;;;;GAOG;AACH,MAAM,IAAI,GAAG,CAAC,EAAE,QAAQ,EAAE,MAAM,GAAG,IAAI,EAAE,GAAG,KAAK,EAAa,EAAE,EAAE,CAAC,CACjE,KAAC,MAAM,OACD,IAAI,CAAC,MAAM,CAAC,EAChB,IAAI,EAAE,CAAC,EACP,SAAS,EAAE,CAAC,EACZ,IAAI,EAAE,CAAC,EACP,KAAK,EAAC,MAAM,EACZ,SAAS,EAAE,MAAM,CAAC,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,QAAQ,KACjC,KAAK,YAER,QAAQ,GACF,CACV,CAAA;AAED,OAAO,EAAE,MAAM,EAAE,IAAI,EAAE,CAAA"}
1
+ {"version":3,"file":"screen.js","sourceRoot":"","sources":["../../../src/backends/gui/screen.tsx"],"names":[],"mappings":"AAAA,YAAY,CAAA;;AAEZ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAkCG;AACH,OAAO,EAAE,MAAM,EAAoB,MAAM,YAAY,CAAA;AACrD,OAAO,EAAE,IAAI,EAAE,MAAM,QAAQ,CAAA;AAI7B;;;;GAIG;AACH,MAAM,MAAM,GAAG,CAAC,EAAE,QAAQ,EAAE,GAAG,KAAK,EAAe,EAAE,EAAE,CAAC,CACtD,KAAC,MAAM,OACD,IAAI,CAAC,QAAQ,CAAC;IAClB,yEAAyE;IACzE,6EAA6E;IAC7E,4EAA4E;IAC5E,wEAAwE;IACxE,0EAA0E;IAC1E,8EAA8E;IAC9E,IAAI,EAAE,CAAC,EACP,SAAS,EAAC,MAAM,EAChB,IAAI,EAAE,CAAC,EACP,KAAK,EAAC,MAAM,EACZ,QAAQ,EAAC,QAAQ,KACb,KAAK,YAER,QAAQ,GACF,CACV,CAAA;AAOD;;;;;;;GAOG;AACH,MAAM,IAAI,GAAG,CAAC,EAAE,QAAQ,EAAE,MAAM,GAAG,IAAI,EAAE,GAAG,KAAK,EAAa,EAAE,EAAE,CAAC,CACjE,KAAC,MAAM,OACD,IAAI,CAAC,MAAM,CAAC,EAChB,IAAI,EAAE,CAAC,EACP,SAAS,EAAE,CAAC,EACZ,IAAI,EAAE,CAAC,EACP,KAAK,EAAC,MAAM,EACZ,SAAS,EAAE,MAAM,CAAC,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,QAAQ,KACjC,KAAK,YAER,QAAQ,GACF,CACV,CAAA;AAED,OAAO,EAAE,MAAM,EAAE,IAAI,EAAE,CAAA"}
package/dist/gallery.html CHANGED
@@ -1,4 +1,4 @@
1
- <!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.1.17</title><style>/* @hanzo/ui — generated by scripts/gen-css.mjs. Do not edit. */
1
+ <!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.1.18</title><style>/* @hanzo/ui — generated by scripts/gen-css.mjs. Do not edit. */
2
2
  :root { --hanzo-ui-styles: 1; }
3
3
  /* Hanzo Design System — the entry point. Import THIS one file.
4
4
  *
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@hanzo/ui",
3
- "version": "8.1.17",
3
+ "version": "8.1.18",
4
4
  "type": "module",
5
5
  "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.",
6
6
  "exports": {