@livx.cc/appwrap 0.39.3 → 0.39.5

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@livx.cc/appwrap",
-  "version": "0.39.3",
+  "version": "0.39.5",
   "description": "Wrap any PWA into a native app with native capabilities (appwrap runtime + @livx.cc/native-kit).",
   "license": "MIT",
   "author": "Elya Livshitz",

package/runtime/app/shell/devmenu.ts

@@ -5,9 +5,10 @@ import { SHELL_BUILD, reloadWebView, getReportedWebVersion } from './handlers';
 
 /**
  * Shake-to-open developer menu (enabled in prod too, gated by `SHELL_CONFIG.devMenu`).
- * A shake raises a native action sheet → "App Info" shows non-sensitive diagnostics
- * (ids, versions, loader, remote host) including the running webapp's version vs. the
- * latest deployed — so you can tell at a glance whether the device got the update.
+ * A shake raises a native action sheet with: "App Info" — non-sensitive diagnostics (ids, versions,
+ * loader, remote host) including the running webapp's version vs. the latest deployed, so you can tell
+ * at a glance whether the device got the update; "Reload"; and "Toggle Debug" — a generic hook that
+ * dispatches the `appwrap:toggleDebug` DOM event so the web app can flip its OWN debug UI.
  * The web version status is reported via the always-on `app.reportWebVersion` handler
  * (in handlers.ts) — independent of this menu — and read here when the menu is shown.
  */
@@ -120,10 +121,11 @@ async function showDevMenu(): Promise<void> {
       title: SHELL_CONFIG.name,
       message: 'Developer menu',
       cancelButtonText: 'Cancel',
-      actions: ['App Info', 'Reload'],
+      actions: ['App Info', 'Reload', 'Toggle Debug'],
     });
     if (action === 'App Info') await showInfo();
     else if (action === 'Reload') reloadWebView();
+    else if (action === 'Toggle Debug') toggleWebDebug();
   } finally {
     menuOpen = false;
   }
@@ -152,6 +154,15 @@ async function showInfo(): Promise<void> {
   Dialogs.alert({ title: 'App Info', message: lines.join('\n'), okButtonText: 'Close' });
 }
 
+/** Generic dev hook: dispatch a DOM event the running web app can listen for to flip its OWN debug UI
+ * (`window.addEventListener('appwrap:toggleDebug', …)`). No-op for apps that don't listen — the shell
+ * has no app-specific debug state of its own, so it just relays the intent. */
+function toggleWebDebug(): void {
+  bridge
+    .evalJs("window.dispatchEvent(new CustomEvent('appwrap:toggleDebug'))")
+    .catch((e) => console.log('[appwrap] toggleDebug dispatch failed:', e));
+}
+
 /** Read the running page's embedded version directly from the WebView: `window.__APP_VERSION__`,
  * then a `<meta name="app-version">` fallback. '' if neither is present (or eval fails). */
 async function readPageVersion(): Promise<string> {

package/src/cli.ts

@@ -20,6 +20,7 @@ import type * as CapManifest from '../../../runtime/app/shell/capabilities.manif
 // Config shape lives in its own import-safe module so a `appwrap.config.ts` file can import the
 // type + `defineConfig` helper without pulling in (and running) the CLI dispatch.
 import type { AppwrapConfig } from './config';
+import { unknownConfigKeys } from './config';
 import {
   androidScreenOrientation,
   applyBuildNumberFlag,
@@ -377,6 +378,15 @@ async function loadConfig(cwd: string, flags: Record<string, string>): Promise<A
   }
   const cfg = await readConfigFile(configPath);
 
+  // Warn (never fail) on keys this appwrap doesn't recognize. A config authored for a NEWER appwrap
+  // silently no-ops its unknown keys on an older install (e.g. `targetedDevices` before 0.39 → wrong
+  // device family, no error). Turn that silent no-op into a signal.
+  const stray = unknownConfigKeys(cfg as unknown as Record<string, unknown>);
+  if (stray.length) {
+    const ver = pkgVersion(resolve(import.meta.dir, '../package.json'));
+    for (const k of stray) console.warn(`⚠ appwrap: unrecognized config key '${k}' — ignored. If you expect it to apply, your installed @livx.cc/appwrap (${ver}) may predate it — upgrade.`);
+  }
+
   // Manifest as source: the appwrap config wins, the PWA manifest fills the gaps, template default last.
   // (DRY single-source — devs don't re-type identity already declared in the manifest.) See mergeManifest.
   if (cfg.pwaDist) mergeManifest(cfg, loadManifest(cwd, cfg));

package/src/config.ts

@@ -200,3 +200,24 @@ export interface AppwrapConfig {
 export function defineConfig(config: AppwrapConfig): AppwrapConfig {
   return config;
 }
+
+/**
+ * Top-level keys appwrap recognizes — KEEP IN SYNC with `AppwrapConfig` above (top-level only; nested
+ * keys like `push.ios` are not listed). Drives `unknownConfigKeys`, which warns (never fails) on stray
+ * keys at load time. The motivating bug: a config written for a NEWER appwrap silently no-ops its
+ * unknown keys on an OLDER installed version (e.g. `targetedDevices` before 0.39 → a universal build
+ * with no error, then an App Store rejection). A loud warning turns that silent no-op into a signal.
+ */
+export const KNOWN_CONFIG_KEYS: ReadonlySet<string> = new Set([
+  'appBoundDomains', 'backendOrigin', 'backgroundColor', 'backgroundTasks', 'buildNumber', 'debug',
+  'debugLog', 'devMenu', 'edgeToEdge', 'entry', 'icon', 'id', 'loader', 'modules', 'name',
+  'neutralizeServiceWorker', 'openNewWindowsInBrowser', 'orientation', 'overrides', 'permissions',
+  'plugins', 'push', 'pwaDist', 'queryPackages', 'queryUrlSchemes', 'serverUrl', 'statusBarStyle',
+  'storekitConfig', 'targetedDevices', 'teamId', 'themeColor', 'trackingDomains', 'urlScheme',
+  'usesNonExemptEncryption', 'vendorPaths', 'version',
+]);
+
+/** Config keys appwrap doesn't recognize (pure — the caller decides how to surface them). */
+export function unknownConfigKeys(cfg: Record<string, unknown>): string[] {
+  return Object.keys(cfg).filter((k) => !KNOWN_CONFIG_KEYS.has(k));
+}