browser-debugger-cli/dist/utils/daemonErrors.d.ts

DevTools telemetry in your terminal. For humans and agents. Direct WebSocket to Chrome's debugging port.

/**
 * Shared utilities for handling daemon connection errors in commands.
 *
 * Provides consistent error handling for peek, tail, and other commands
 * that communicate with the daemon via IPC.
 */
/**
 * Options for daemon connection error handling.
 */
export interface DaemonErrorOptions {
    /** Use JSON output format */
    json?: boolean | undefined;
    /** Follow/watch mode (don't exit, show retry message) */
    follow?: boolean | undefined;
    /** Retry interval in milliseconds (for display message) */
    retryIntervalMs?: number | undefined;
    /** Custom exit code (defaults to RESOURCE_NOT_FOUND) */
    exitCode?: number | undefined;
}
/**
 * Result of handling a daemon connection error.
 */
export interface DaemonErrorResult {
    /** Whether the process should exit */
    shouldExit: boolean;
    /** Exit code to use if exiting */
    exitCode?: number;
}
/**
 * Handle daemon connection errors with consistent formatting and behavior.
 *
 * Formats and logs the error appropriately based on output mode.
 * Returns whether the caller should exit and with what code.
 *
 * @param error - Error message to display
 * @param options - Error handling options
 * @returns Result indicating whether to exit
 *
 * @example
 * ```typescript
 * // One-time command
 * const result = handleDaemonConnectionError('Daemon not running', {
 *   json: options.json,
 *   exitCode: EXIT_CODES.RESOURCE_NOT_FOUND
 * });
 * if (result.shouldExit) {
 *   process.exit(result.exitCode);
 * }
 *
 * // Follow mode (retries)
 * handleDaemonConnectionError('Connection lost', {
 *   json: options.json,
 *   follow: true,
 *   retryIntervalMs: 1000
 * });
 * // Returns { shouldExit: false }
 * ```
 */
export declare function handleDaemonConnectionError(error: string, options: DaemonErrorOptions): DaemonErrorResult;
//# sourceMappingURL=daemonErrors.d.ts.map