react-native-gtkx 0.4.0-alpha.2 → 0.4.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "react-native-gtkx",
-  "version": "0.4.0-alpha.2",
+  "version": "0.4.0",
   "description": "React Native components and APIs for Linux desktop, rendered as native GTK4 widgets via gtkx",
   "license": "MIT",
   "author": "Anton Petrov <anton@itsmepetrov.com>",
@@ -126,14 +126,14 @@
     }
   },
   "dependencies": {
-    "@gtkx/cli": "1.0.0-rc.4",
-    "@gtkx/codegen": "1.0.0-rc.4",
-    "@gtkx/config": "1.0.0-rc.4",
-    "@gtkx/css": "1.0.0-rc.4",
-    "@gtkx/react": "1.0.0-rc.4",
-    "@gtkx/runtime": "1.0.0-rc.4",
-    "@gtkx/testing": "1.0.0-rc.4",
-    "@gtkx/vitest": "1.0.0-rc.4",
+    "@gtkx/cli": "1.2.2",
+    "@gtkx/codegen": "1.2.2",
+    "@gtkx/config": "1.2.2",
+    "@gtkx/css": "1.2.2",
+    "@gtkx/react": "1.2.2",
+    "@gtkx/runtime": "1.2.2",
+    "@gtkx/testing": "1.2.2",
+    "@gtkx/vitest": "1.2.2",
     "@modelcontextprotocol/sdk": "^1.30.0",
     "rolldown": "^1.1.5",
     "yoga-layout": "^3.2.1",

package/dist/gtkx/bridge/use-signal.d.ts

@@ -1,2 +0,0 @@
-import { useSignal as useGtkxSignal } from "@gtkx/react";
-export declare const useSignal: typeof useGtkxSignal;

package/dist/gtkx/bridge/use-signal.js

@@ -1,41 +0,0 @@
-// RC4-WORKAROUND(use-signal-stale-handler): see docs/gtkx-rc4-notes.md
-// @gtkx/react's useSignal documents that "each emission runs the handler from
-// the latest render", and rc.1 delivered that by pinning the handler in a ref
-// of its own. rc.3 routes it through React's useEffectEvent instead, and
-// react-reconciler@0.33.0 only refreshes useEffectEvent in
-// commitBeforeMutationEffects for `case 0` (FunctionComponent) — `case 11`
-// (ForwardRef) and `case 15` (SimpleMemoComponent) fall through unrefreshed.
-// Any useEffectEvent inside a memo or forwardRef component is pinned to its
-// mount closure permanently; this has nothing to do with useSignal
-// specifically (confirmed upstream: gtkx-org/gtkx#467) — plain
-// useEffectEvent called from an Effect fails identically. It reproduced for
-// us because our ScrollView is a forwardRef (components/scroll-view.tsx) with
-// the useSignal calls inside it; tree depth was a coincidence, not the
-// trigger. The consequence is not subtle — the mount-time scroll handler
-// windows a VirtualizedList against the data it saw at mount, so a list
-// whose rows arrive from a fetch renders EMPTY as soon as it is scrolled.
-//
-// Restore the documented contract at the bridge: keep the latest handler in a
-// ref of our own and hand gtkx a stable wrapper (stable so the connection is
-// never re-established, which is what its useEffectEvent was for). The ref is
-// refreshed in an INSERTION effect — the earliest commit phase, ahead of every
-// layout effect, so a signal emitted from one (the list's own scroll
-// corrections) already sees the handler from the render being committed.
-// React fixed the refresh on the 19.3 line (moved into
-// commitMutationEffectsOnFiber, covering `case 0/11/14/15` ahead of child
-// traversal), but there is no stable 0.34.x gtkx release yet and the React
-// canaries pin an exact prerelease peer, so this wrapper stays until a
-// stable React 19.3 ships — not "when useSignal is fixed" (see gtkx#467).
-import { useSignal as useGtkxSignal } from "@gtkx/react";
-import { useCallback, useInsertionEffect, useRef } from "react";
-export const useSignal = (object, signal, handler, options) => {
-    // The handler type is generic in the signal name; the wrapper only forwards
-    // arguments, so it crosses that boundary as an untyped callable.
-    const latest = useRef(() => undefined);
-    useInsertionEffect(() => {
-        latest.current = handler;
-    });
-    const stable = useCallback((...args) => latest.current(...args), []);
-    useGtkxSignal(object, signal, stable, options);
-};
-//# sourceMappingURL=use-signal.js.map

package/dist/gtkx/bridge/use-signal.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"use-signal.js","sourceRoot":"","sources":["../../../src/gtkx/bridge/use-signal.ts"],"names":[],"mappings":"AAAA,uEAAuE;AACvE,8EAA8E;AAC9E,8EAA8E;AAC9E,yEAAyE;AACzE,2DAA2D;AAC3D,2EAA2E;AAC3E,6EAA6E;AAC7E,4EAA4E;AAC5E,mEAAmE;AACnE,+DAA+D;AAC/D,4EAA4E;AAC5E,8EAA8E;AAC9E,uEAAuE;AACvE,yEAAyE;AACzE,wEAAwE;AACxE,0EAA0E;AAC1E,EAAE;AACF,8EAA8E;AAC9E,6EAA6E;AAC7E,8EAA8E;AAC9E,+EAA+E;AAC/E,qEAAqE;AACrE,yEAAyE;AACzE,uDAAuD;AACvD,0EAA0E;AAC1E,2EAA2E;AAC3E,uEAAuE;AACvE,0EAA0E;AAC1E,OAAO,EAAE,SAAS,IAAI,aAAa,EAAE,MAAM,aAAa,CAAA;AACxD,OAAO,EAAE,WAAW,EAAE,kBAAkB,EAAE,MAAM,EAAE,MAAM,OAAO,CAAA;AAI/D,MAAM,CAAC,MAAM,SAAS,GAAyB,CAC7C,MAAM,EACN,MAAM,EACN,OAAO,EACP,OAAO,EACP,EAAE;IACF,4EAA4E;IAC5E,iEAAiE;IACjE,MAAM,MAAM,GAAG,MAAM,CAAa,GAAG,EAAE,CAAC,SAAS,CAAC,CAAA;IAClD,kBAAkB,CAAC,GAAG,EAAE;QACtB,MAAM,CAAC,OAAO,GAAG,OAAgC,CAAA;IACnD,CAAC,CAAC,CAAA;IACF,MAAM,MAAM,GAAG,WAAW,CACxB,CAAC,GAAG,IAAI,EAAE,EAAE,CAAC,MAAM,CAAC,OAAO,CAAC,GAAG,IAAI,CAAC,EACpC,EAAE,CACH,CAAA;IACD,aAAa,CAAC,MAAM,EAAE,MAAM,EAAE,MAAmC,EAAE,OAAO,CAAC,CAAA;AAC7E,CAAC,CAAA","sourcesContent":["// RC4-WORKAROUND(use-signal-stale-handler): see docs/gtkx-rc4-notes.md\n// @gtkx/react's useSignal documents that \"each emission runs the handler from\n// the latest render\", and rc.1 delivered that by pinning the handler in a ref\n// of its own. rc.3 routes it through React's useEffectEvent instead, and\n// react-reconciler@0.33.0 only refreshes useEffectEvent in\n// commitBeforeMutationEffects for `case 0` (FunctionComponent) — `case 11`\n// (ForwardRef) and `case 15` (SimpleMemoComponent) fall through unrefreshed.\n// Any useEffectEvent inside a memo or forwardRef component is pinned to its\n// mount closure permanently; this has nothing to do with useSignal\n// specifically (confirmed upstream: gtkx-org/gtkx#467) — plain\n// useEffectEvent called from an Effect fails identically. It reproduced for\n// us because our ScrollView is a forwardRef (components/scroll-view.tsx) with\n// the useSignal calls inside it; tree depth was a coincidence, not the\n// trigger. The consequence is not subtle — the mount-time scroll handler\n// windows a VirtualizedList against the data it saw at mount, so a list\n// whose rows arrive from a fetch renders EMPTY as soon as it is scrolled.\n//\n// Restore the documented contract at the bridge: keep the latest handler in a\n// ref of our own and hand gtkx a stable wrapper (stable so the connection is\n// never re-established, which is what its useEffectEvent was for). The ref is\n// refreshed in an INSERTION effect — the earliest commit phase, ahead of every\n// layout effect, so a signal emitted from one (the list's own scroll\n// corrections) already sees the handler from the render being committed.\n// React fixed the refresh on the 19.3 line (moved into\n// commitMutationEffectsOnFiber, covering `case 0/11/14/15` ahead of child\n// traversal), but there is no stable 0.34.x gtkx release yet and the React\n// canaries pin an exact prerelease peer, so this wrapper stays until a\n// stable React 19.3 ships — not \"when useSignal is fixed\" (see gtkx#467).\nimport { useSignal as useGtkxSignal } from \"@gtkx/react\"\nimport { useCallback, useInsertionEffect, useRef } from \"react\"\n\ntype AnyHandler = (...args: unknown[]) => unknown\n\nexport const useSignal: typeof useGtkxSignal = (\n  object,\n  signal,\n  handler,\n  options,\n) => {\n  // The handler type is generic in the signal name; the wrapper only forwards\n  // arguments, so it crosses that boundary as an untyped callable.\n  const latest = useRef<AnyHandler>(() => undefined)\n  useInsertionEffect(() => {\n    latest.current = handler as unknown as AnyHandler\n  })\n  const stable = useCallback<AnyHandler>(\n    (...args) => latest.current(...args),\n    [],\n  )\n  useGtkxSignal(object, signal, stable as unknown as typeof handler, options)\n}\n"]}