@gjsify/gtk-host 0.43.0 → 0.45.0

package/lib/types/testing/gate.d.mts

@@ -1,2 +1,25 @@
+import { type Runtime } from '@gjsify/unit';
 import type { DiagnosticsGate } from '../conformance/diagnostics.js';
 export declare const gated: (gate: DiagnosticsGate, name: string, body: () => Promise<void>) => Promise<void>;
+/**
+ * The runtimes that can host GTK — and an IDENTITY list on purpose.
+ *
+ * These suites need a reachable GTK, not a particular interpreter, so the
+ * expressive form would be a capability (`@gjsify/unit` splits `'Display'` from
+ * `'Gl'` for exactly that reason). It is not used here, and the reason is the
+ * failure mode rather than taste.
+ *
+ * A capability can only be PROBED — nothing about `(os, env)` answers "is the Gtk
+ * typelib reachable from this process", and `@gjsify/unit` is Tier 1 and must not
+ * import `gi://` to find out. A probe that answers "no" makes the whole suite STAND
+ * DOWN, and `requireAxes` cannot catch that: it only holds axes the host MATCHES.
+ * So a container that lost its GTK would run zero tests and report success — the
+ * green-that-checked-nothing shape, arriving through the very gate meant to widen
+ * coverage. Measured once already: gated on `'Gjs'` alone, this suite built for the
+ * node target exited 0 having run 0 tests from 0 gates, 9 stood down.
+ *
+ * Named identities instead mean the suite RUNS wherever it was built, and a missing
+ * GTK dies loudly at `Gtk.init()` in the first line of each suite. Louder beats
+ * more expressive when the quiet failure is a pass.
+ */
+export declare const GTK_HOSTS: Runtime[];

package/lib/types/types.d.ts

@@ -117,12 +117,29 @@ export type ChildPolicy = {
     remove: string;
     wrap: 'list-box-row' | 'flow-box-child' | null;
 }
-/** `Adw.HeaderBar`, `Adw.ToolbarView`, `Adw.ActionRow`: named attachment points. */
+/**
+ * `Adw.HeaderBar`, `Adw.ToolbarView`, `Adw.ActionRow`: named attachment points.
+ *
+ * `remove` is OPTIONAL because a slot can be backed two ways and only one of them
+ * needs it. A `set_`-prefixed slot is emptied by writing `null` back through the
+ * same setter (`detachChild` already does exactly that, via `setterSlotOf`), so a
+ * policy whose slots are ALL setters never reaches a remove method — and
+ * `Adw.NavigationSplitView` / `Adw.OverlaySplitView` have none to name: measured on
+ * libadwaita 1.9.3, their only `remove*` methods are `GtkWidget`'s
+ * (`remove_controller`, `remove_css_class`, …). Declaring `remove: 'remove'` there
+ * would be a claim `descriptorProblems()` correctly rejects.
+ *
+ * An ADDER-backed slot (`add_top_bar`, `pack_start`) is the opposite: nothing takes
+ * a child back out of it but a remove method, so `remove` is REQUIRED the moment one
+ * slot does not start with `set_`. That rule is machine-checked in `policyProblems()`
+ * rather than left to this comment — optional in the type and unchecked would turn
+ * `Adw.ToolbarView` losing its `remove` into a `TypeError` deep inside an unmount.
+ */
  | {
     kind: 'slotted';
     slots: Record<string, string>;
     defaultSlot: string;
-    remove: string;
+    remove?: string;
 }
 /**
  * `Gtk.Stack`, `Adw.NavigationView`: children addressed by name/tag.
@@ -150,14 +167,14 @@ export type ChildPolicy = {
  * Generated, not curated: the tag exists, its placement rule does not.
  *
  * The generated table adds every concrete GtkWidget descendant the GIR
- * describes — 164 of them — while the curated table measures placement for a
+ * describes, plus the placement carriers, while the curated table measures placement for a
  * fraction. Guessing an adder for the rest would be the worst of the three
  * options: `add` and `append` and `set_child` all exist somewhere in GTK, and
  * calling the wrong one is a warning at exit 0.
  *
  * So the honest state is spelled out. Such a widget can be CREATED and given
  * properties and handlers; inserting a child raises a named error that says
- * which tag needs a curated policy. A leaf widget — most of the 164 — needs
+ * which tag needs a curated policy. A leaf widget — most of the table — needs
  * nothing more.
  */
  | {

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@gjsify/gtk-host",
-    "version": "0.43.0",
+    "version": "0.45.0",
     "description": "Framework-agnostic GTK4/Adwaita host: the element model UI-framework renderers bind to",
     "type": "module",
     "module": "lib/esm/index.js",
@@ -10,6 +10,14 @@
             "types": "./lib/types/index.d.ts",
             "default": "./lib/esm/index.js"
         },
+        "./style": {
+            "types": "./lib/types/style/index.d.ts",
+            "default": "./lib/esm/style/index.js"
+        },
+        "./list": {
+            "types": "./lib/types/list/index.d.ts",
+            "default": "./lib/esm/list/index.js"
+        },
         "./vue": {
             "types": "./lib/types/adapters/vue.d.ts",
             "default": "./lib/esm/adapters/vue.js"
@@ -63,9 +71,11 @@
         "build:gjsify": "gjsify build --library 'src/**/*.{ts,js}' --exclude 'src/**/*.spec.{mts,ts}' 'src/test.{mts,ts}'",
         "build:types": "gjsify tsc",
         "build:test": "gjsify run build:test:gjs",
+        "build:test:node": "gjsify build src/test.mts --app node --outfile dist/test.node.mjs --define '__VUE_OPTIONS_API__=false' --define '__VUE_PROD_DEVTOOLS__=false' --define '__VUE_PROD_HYDRATION_MISMATCH_DETAILS__=false' --define 'process.env.NODE_ENV=\"production\"' --exclude-globals navigator",
         "build:test:gjs": "gjsify build src/test.mts --app gjs --outfile test.gjs.mjs --define '__VUE_OPTIONS_API__=false' --define '__VUE_PROD_DEVTOOLS__=false' --define '__VUE_PROD_HYDRATION_MISMATCH_DETAILS__=false' --define 'process.env.NODE_ENV=\"production\"' --exclude-globals navigator",
         "test": "gjsify run build:gjsify && gjsify run build:test && gjsify run test:gjs",
         "test:gjs": "gjsify run test.gjs.mjs",
+        "test:gjs-on-node": "gjsify run build:gjsify && gjsify run build:test:node && NODE_GI_NATIVE=${NODE_GI_NATIVE:-prebuild} node dist/test.node.mjs",
         "generate": "gjsify build src/generator/main.mts --app gjs --outfile tmp/generate.gjs.mjs && gjsify run tmp/generate.gjs.mjs -- --out src/generated && gjsify format src/generated"
     },
     "keywords": [
@@ -88,8 +98,8 @@
     "peerDependencies": {
         "@vue/runtime-core": "^3.5.0",
         "solid-js": "^1.9.0",
-        "react": "^18.3.1",
-        "react-reconciler": "^0.29.2"
+        "react": "^19.2.0",
+        "react-reconciler": "^0.33.0"
     },
     "peerDependenciesMeta": {
         "@vue/runtime-core": {
@@ -106,28 +116,32 @@
         }
     },
     "devDependencies": {
-        "@gjsify/cli": "^0.43.0",
+        "@gjsify/cli": "^0.45.0",
         "@vue/runtime-core": "^3.5.0",
         "solid-js": "^1.9.0",
-        "@gjsify/unit": "^0.43.0",
+        "@gjsify/unit": "^0.45.0",
         "@types/node": "^25.9.2",
         "typescript": "^6.0.3",
-        "@gjsify/domparser": "^0.43.0",
+        "@gjsify/domparser": "^0.45.0",
+        "@gjsify/node-gi": "file:../../node-gi/node-gi",
         "vue": "^3.5.41",
         "vue-tsc": "^3.3.11",
-        "react": "^18.3.1",
-        "react-reconciler": "^0.29.2",
-        "@types/react": "^18.3.12",
-        "@types/react-reconciler": "^0.28.9"
+        "react": "^19.2.0",
+        "react-reconciler": "^0.33.0",
+        "@types/react": "^19.2.2",
+        "@types/react-reconciler": "^0.33.0"
     },
     "gjsify": {
         "runtimes": {
             "gjs": "polyfill",
-            "node": "none",
+            "node": "polyfill",
             "browser": "none",
             "nativescript": "none"
         },
-        "tier": 3
+        "tier": 3,
+        "widgetVocabulary": {
+            "role": "reference"
+        }
     },
     "license": "MIT",
     "repository": {