@gjsify/adwaita-gobject-native 0.64.1-next.247 → 0.64.1-next.249

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 (2) hide show
  1. package/README.md +14 -5
  2. package/package.json +6 -6
package/README.md CHANGED
@@ -106,13 +106,22 @@ first use. `construct` alone touches no engine for plain `READWRITE` properties,
106
106
  that reports a cost of zero and is wrong. Numbers for both hosts:
107
107
  `docs/reports/2026-10-15-adr-0110-gates.md`.
108
108
 
109
+ ## This engine is the Android DEFAULT, and still the app's call
110
+
111
+ Since 2026-10-15 (ADR 0110 § 1) a NativeScript Android build runs on this engine unless the app
112
+ says otherwise with `usePureJsGObjectEngine()` from `@gjsify/adwaita-core`. What did NOT change is
113
+ who builds it: `@gjsify/adwaita-nativescript`'s `createGObject(door, …)` still does not reach for
114
+ `requireGi` itself, and the reason is in a comment at that call — the line is evaluated at module
115
+ load, so a `requireGi` that throws would take the app down at startup, and this package is
116
+ Android-only tier 3 while the port is tier 2 and installable in a browser. So `useRealGObjectEngine`
117
+ stays an app-code call; the default only decides what happens when the app made NO call, and on
118
+ Android that is a loud refusal rather than a quiet pure-JS fallback.
119
+
109
120
  ## What is NOT measured
110
121
 
111
- Nothing here has run on Android. `@gjsify/adwaita-nativescript`'s `createGObject(door)` does not
112
- pass this engine yet, and the reason is in a comment at that call: the line is evaluated at module
113
- load, so a `requireGi` that throws on NativeScript's V8 would take an app down at startup, and
114
- whether node-gi loads there at all is ADR 0105's own open question. The evidence for everything
115
- above is node-gi on Linux.
122
+ Everything above was measured with node-gi on Linux and on an `x86_64` Android emulator
123
+ (`docs/reports/2026-10-15-node-gi-set-emit-perf.md` § "Confirmed on the emulator"). No arm64
124
+ release build has been timed for cold start; that needs a device and is still open.
116
125
 
117
126
  ## Runtimes
118
127
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@gjsify/adwaita-gobject-native",
3
- "version": "0.64.1-next.247",
3
+ "version": "0.64.1-next.249",
4
4
  "description": "Real GObject behind @gjsify/adwaita-core's GObject subset — a GObjectEngine whose property store and signal bus are a live GObject reached through node-gi (ADR 0105)",
5
5
  "type": "module",
6
6
  "module": "lib/esm/index.js",
@@ -38,13 +38,13 @@
38
38
  "adwaita"
39
39
  ],
40
40
  "dependencies": {
41
- "@gjsify/adwaita-core": "0.64.1-next.247"
41
+ "@gjsify/adwaita-core": "0.64.1-next.249"
42
42
  },
43
43
  "devDependencies": {
44
- "@gjsify/app-settings": "0.64.1-next.247",
45
- "@gjsify/cli": "0.64.1-next.247",
44
+ "@gjsify/app-settings": "0.64.1-next.249",
45
+ "@gjsify/cli": "0.64.1-next.249",
46
46
  "@gjsify/node-gi": "file:../../node-gi/node-gi",
47
- "@gjsify/unit": "0.64.1-next.247",
47
+ "@gjsify/unit": "0.64.1-next.249",
48
48
  "@types/node": "^25.9.2",
49
49
  "typescript": "^6.0.3"
50
50
  },
@@ -70,5 +70,5 @@
70
70
  "url": "https://github.com/gjsify/gjsify/issues"
71
71
  },
72
72
  "homepage": "https://github.com/gjsify/gjsify/tree/main/packages/nativescript-bridge/gobject#readme",
73
- "gitHead": "0865008d02b3a10af8152061095378aabe6b9d5d"
73
+ "gitHead": "2e501133bfbe80e44506deef30e911e0c551502f"
74
74
  }