Browser Types

Import these from @blyp/core/client:

import type {
  ClientLogger,
  ClientLoggerConfig,
  ClientLogEvent,
  ClientLogLevel,
  ClientLogBrowserContext,
  ClientLogDeviceContext,
  ClientLogPageContext,
  RemoteDeliveryConfig,
  RemoteDeliveryRetryContext,
  RemoteDeliverySuccessContext,
  RemoteDeliveryFailureContext,
  RemoteDeliveryDropContext,
  ParseErrorOptions,
  BlypErrorLike,
  BlypErrorCode,
} from "@blyp/core/client";

Expo-specific mobile types live under @blyp/core/expo:

import type {
  ExpoLogger,
  ExpoLoggerConfig,
  ClientLogDeviceContext,
  RemoteDeliveryConfig,
} from "@blyp/core/expo";

Main interfaces

• ClientLogger: browser logger with info, warning, error, critical, success, debug, table, child
• ClientLoggerConfig: endpoint, headers, credentials, localConsole, remoteSync, metadata, delivery
• ClientLogEvent: normalized payload sent to the backend ingestion endpoint
• ClientLogBrowserContext: user agent, language, and platform info
• ClientLogDeviceContext: mobile/device metadata, including Expo network details when available
• ClientLogPageContext: current URL, pathname, search, hash, title, and referrer
• RemoteDeliveryConfig: retry/queue policy plus onRetry, onSuccess, onFailure, and onDrop
• RemoteDeliveryRetryContext, RemoteDeliverySuccessContext, RemoteDeliveryFailureContext, RemoteDeliveryDropContext: callback payloads for delivery lifecycle hooks
• ParseErrorOptions: logger, logLevel, and fallbackStatus
• ExpoLogger / ExpoLoggerConfig: mobile logger surface for Expo apps using absolute remote delivery

Example

const config: ClientLoggerConfig = {
  endpoint: "/inngest",
  localConsole: true,
  remoteSync: true,
  delivery: {
    maxRetries: 3,
    retryDelayMs: 5000,
    maxQueueSize: 100,
  },
  metadata: {
    app: "dashboard",
  },
};