@scalebun/react-native 1.2.3 → 1.3.0

package/dist/scalebun.full.js

@@ -14031,6 +14031,12 @@ var SHAPE = {
     }
   },
   captureInteractionHeatmap: bool(true),
+  // Opt-in: intercept console.* and ship the lines to the Diagnose → Logs lane in SaaS
+  // mode. OFF by default — console output can carry PII/secrets and adds ingest volume,
+  // so capturing it is the host's explicit choice, not a silent default. When true and a
+  // clientKey is present, the bootstrapper arms the console integration (previously only
+  // reachable through the desktop-debug tooling, so stock SaaS apps captured nothing).
+  captureConsoleLogs: bool(false),
   ota: {
     kind: "obj",
     opt: true,
@@ -15283,6 +15289,9 @@ function uninstallAlertInstrumentation() {
   installed = false;
 }
 
+// lib/module/bootstrap/SDKBootstrapper.js
+init_consoleIntegration();
+
 // lib/module/features/session/BackendSessionAdapter.js
 init_internalLogger();
 
@@ -16795,6 +16804,9 @@ var SDKBootstrapper = class {
             }
           });
           sessionManager.setBackendTransport(backendAdapter);
+          if (this.config.clientKey && this.config.captureConsoleLogs) {
+            installConsoleIntegration();
+          }
           backendAdapter.recoverPersistedFrames().catch(() => {
           });
           if (this.config.clientKey) {
@@ -16981,6 +16993,7 @@ var SDKBootstrapper = class {
     this._deepLinkUnsubscribe?.();
     this._deepLinkUnsubscribe = null;
     uninstallAlertInstrumentation();
+    uninstallConsoleIntegration();
     this.featureRegistry.teardownAll();
   }
 };
@@ -20321,8 +20334,29 @@ var ScaleBunFacade = class {
       }
     });
   }
-  /** Log a message (convenience wrapper over track) */
+  /**
+   * Log a message. Delivered to BOTH lanes:
+   *  - the Diagnose → Logs lane (tagged `source: 'sdk'`), so an explicit `log()` call shows
+   *    up where a developer looks for logs. The method name promised this, but it previously
+   *    only emitted a `$log` analytics EVENT and never reached the Logs page.
+   *  - the analytics `$log` event (unchanged), so anything already built on it keeps working.
+   * `queueLog` self-gates on `clientKey`, so the Logs-lane write is a no-op outside SaaS mode.
+   */
   log(level, message, data) {
+    try {
+      const transport = SessionManager.getExistingInstance()?.getBackendTransport();
+      transport?.queueLog({
+        level,
+        message,
+        source: "sdk",
+        platform: "js",
+        timestamp: (/* @__PURE__ */ new Date()).toISOString(),
+        ...data ? {
+          metadata: data
+        } : {}
+      });
+    } catch {
+    }
     return this.track("$log", {
       level,
       message,