@reticlehq/browser 2.13.1 → 3.1.0

package/dist/observers/network.d.ts

@@ -1,41 +1,17 @@
-import type { Emit, Teardown } from './types.js';
-import { redactUrl, netUrlFields } from './network-redact.js';
+import { type Emit, type Teardown } from './types.js';
+import { redactUrl, netUrlFields } from './net-detail/network-redact.js';
 export { redactUrl, netUrlFields };
-/** Config for the network observer. Body capture is OFF by default and dev-only opt-in. */
-/**
- * Reinterpret a completed request's fields from its response.
- *
- * The seam exists so this observer stays ignorant of desktop IPC. A Tauri `invoke` arrives here as an
- * ordinary fetch to an `ipc://` protocol, and the header that says whether the Rust command
- * succeeded means nothing to a network observer — so the knowledge lives in the IPC observer and is
- * passed IN, rather than this module importing it. Returns undefined to leave the record untouched.
- */
 type NetResponseReinterpreter = (url: string, header: (name: string) => string | null) => Record<string, unknown> | undefined;
 interface NetworkOptions {
-    /** Capture request/response bodies (text-like content only, redacted, per-body capped). */
     captureBodies?: boolean;
-    /** Optional hook that reinterprets a completed request — see NetResponseReinterpreter. */
+    captureErrorBodies?: boolean;
     reinterpret?: NetResponseReinterpreter;
-    /**
-     * Requests Reticle itself makes, which must never reach the app's evidence.
-     *
-     * Same seam and same reason as `reinterpret`: this observer knows nothing about desktop IPC, and
-     * the SDK's own Tauri screenshot travels as an ordinary fetch through this very patch. Passed in
-     * rather than imported, so the knowledge stays in the IPC observer.
-     */
     ignore?: (url: string) => boolean;
 }
-/** Pure: the first real app-code frame in a stack string, capped. Exported for unit testing. */
 export declare function firstAppFrame(stack: string | undefined): string | undefined;
-/** The timing fields we lift from a resource entry — TTFB is the perf signal a duration alone hides. */
 interface NetTiming {
     ttfbMs?: number;
     transferSize?: number;
 }
-/**
- * Pure: derive TTFB + transfer size from a PerformanceResourceTiming entry. TTFB = responseStart -
- * requestStart; cross-origin responses zero those (Timing-Allow-Origin), so we omit rather than report a
- * bogus 0. Exported for unit testing (jsdom doesn't post real resource entries).
- */
 export declare function extractTiming(entry: PerformanceResourceTiming | undefined): NetTiming;
 export declare function installNetwork(emit: Emit, opts?: NetworkOptions): Teardown;