@gjsify/node-gi 0.28.0 → 0.29.0

package/gtk-runtime.js

@@ -113,8 +113,15 @@ export function maybeReexecForGtkRuntime() {
     // re-launched with a Node argv — and `createRequire` there is
     // @gjsify/module's polyfill, which rejects synchronous BUILTIN loads, so even
     // REACHING the child_process require below would throw during module init.
-    // Nothing needs the repair anyway: gjs itself resolves these leaves (its
-    // binary carries the rpath this whole module exists to compensate for).
+    // The re-exec is therefore IMPOSSIBLE here, not merely unnecessary — and the
+    // gap is real: gjs's own rpath covers the GLIB-family leaves it links against,
+    // but MEASURED on the macOS 15.7.8 VM that rpath points at glib's keg ALONE
+    // (`…/opt/glib/lib`), so a bare-leaf `libgtk-4.1.dylib` fails under plain gjs
+    // exactly as it did under node. Repairing it belongs to whoever LAUNCHES the
+    // gjs process, one hop earlier: `buildNativeEnv()` in `@gjsify/cli` puts
+    // `systemGiLibraryDirs()` on the child's `DYLD_FALLBACK_LIBRARY_PATH` (its
+    // `system-gi.ts` is the pinned mirror of this module's `system-gi.js`). A gjs
+    // launched by hand keeps the gap — tracked in `status/open-todos.md`.
     // Same probe index.js uses for RUNTIME — as with the Bun/Deno pair above, the
     // check has to live here too because this runs before that const is defined.
     if (typeof globalThis.imports !== 'undefined' && typeof globalThis.print === 'function') return;
@@ -219,6 +226,15 @@ export function maybeWireGtkWindowingEnv() {
     };
     setIfUnset('GSETTINGS_SCHEMA_DIR', schemaDir);
 
+    // MODULE_FILE is the load-bearing one on BOTH platforms — it is the cache, and the
+    // cache is what names the modules. MODULEDIR only resolves a RELATIVE module path in
+    // that cache, and only where gdk-pixbuf was built relocatable: measured on macOS with
+    // Homebrew's gdk-pixbuf 2.44.7, the string `GDK_PIXBUF_MODULEDIR` is not in the dylib
+    // at all, so the darwin bundle's cache instead names each module `@loader_path/…`
+    // (relative to the image that dlopens it, i.e. the bundle's lib/) and resolves with no
+    // env beyond this file. gvsbuild's win32 build IS relocatable, so MODULEDIR is what
+    // its bare-leaf cache needs — hence both are set, and neither platform depends on the
+    // other's mechanism.
     const loaderCache = join(bundle.dir, 'lib', 'gdk-pixbuf-2.0', '2.10.0', 'loaders.cache');
     if (existsSync(loaderCache)) {
         setIfUnset('GDK_PIXBUF_MODULEDIR', join(bundle.dir, 'lib', 'gdk-pixbuf-2.0', '2.10.0', 'loaders'));

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@gjsify/node-gi",
-  "version": "0.28.0",
+  "version": "0.29.0",
   "description": "GObject-Introspection runtime for Node.js — load gi:// namespaces (GLib/GObject/Gio/…) with GJS-compatible semantics. Vendored + rewritten from node-gtk under MIT.",
   "type": "module",
   "license": "MIT",

package/system-gi.js

@@ -42,6 +42,17 @@
 // `hostTarget()` beside it and the CLI's `resolvePrebuildDirName()` — so the
 // darwin branch is unit-testable from a Linux host and the host values are read
 // only at the outermost call site, as defaults.
+//
+// MIRRORED, DELIBERATELY, in `packages/infra/cli/src/utils/system-gi.ts`. The
+// same loader gap breaks a `gjs` child too (Homebrew's `gjs` has an rpath into
+// GLIB's keg only, so it resolves no other keg's leaves — measured, trace in that
+// file), and `gjsify run/showcase/storybook` must repair it in the env it hands
+// the child. The CLI cannot IMPORT this module: ADR 0005 Decision 2 forbids a
+// Tier-1 package taking a dependency edge on `@gjsify/node-gi`. So the port is
+// pinned by an agreement test — `packages/infra/cli/src/utils/system-gi.spec.ts`
+// imports THIS file by relative path and asserts both implementations return
+// identical arrays for a table of injected inputs. Change one, change both; the
+// eventual lift to a shared package is tracked in `status/open-todos.md`.
 import { statSync } from 'node:fs';
 import { createRequire } from 'node:module';
 import { basename, dirname, join } from 'node:path';