@livx.cc/appwrap 0.39.4 → 0.39.5

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@livx.cc/appwrap",
-  "version": "0.39.4",
+  "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/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));
+}