@livx.cc/native-kit 0.42.0 → 0.43.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@livx.cc/native-kit",
-  "version": "0.42.0",
+  "version": "0.43.0",
   "description": "Isomorphic native-capabilities kit for PWAs \u2014 same API in browser and in an appwrap native shell. Zero dependencies.",
   "license": "MIT",
   "author": "Elya Livshitz",

package/src/core/module-registry.ts

@@ -43,8 +43,14 @@ export class ModuleRegistry {
     return [...new Set([...this.instances.keys(), ...this.factories.keys()])].sort();
   }
 
+  /**
+   * Typed, string-keyed lookup. STRICT by design: the ONLY public signature is keyed to
+   * `keyof KitModuleRegistry`, so `getModule('billing')` is a COMPILE ERROR unless the billing pack's
+   * kit client has been imported (its `declare module` augments the registry) — you get compile-time
+   * verification + autocomplete of exactly the modules you've wired, never a runtime surprise. For a
+   * genuinely dynamic name, use {@link getModuleUnsafe}.
+   */
   getModule<K extends keyof KitModuleRegistry>(name: K): KitModuleRegistry[K];
-  getModule<T = unknown>(name: string): T;
   getModule(name: string): unknown {
     if (this.instances.has(name)) return this.instances.get(name);
     const factory = this.factories.get(name);
@@ -61,4 +67,10 @@ export class ModuleRegistry {
         `Did you list its pack in modulePacks?`
     );
   }
+
+  /** Escape hatch for a genuinely DYNAMIC module name (not a compile-time literal) — bypasses the
+   * keyed check. Prefer {@link getModule}; reach for this only when the name isn't statically known. */
+  getModuleUnsafe<T = unknown>(name: string): T {
+    return (this.getModule as (n: string) => unknown)(name) as T;
+  }
 }