npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@abbacchio/browser-transport

v0.3.0

Published

OTLP-native browser and React logging client for Abbacchio - intercept console.log and send via OpenTelemetry

Readme

@abbacchio/browser-transport

OTLP-native browser and React logging client for Abbacchio. Intercept console.log, capture network requests, Web Vitals, errors, and performance metrics — all sent via OpenTelemetry protocol.

Installation

npm install @abbacchio/browser-transport
# or
pnpm add @abbacchio/browser-transport
# or
yarn add @abbacchio/browser-transport

Quick Start

Option 1: Auto-capture (one line)

import '@abbacchio/browser-transport/auto'

// All console.log calls now go to Abbacchio!
console.log('This is captured!')
console.error('Errors too!')

Configure via global variable:

<script>
  window.__ABBACCHIO_CONFIG__ = {
    endpoint: 'http://localhost:4002',
    serviceName: 'my-app',
  }
</script>
<script type="module">
  import '@abbacchio/browser-transport/auto'
</script>

Option 2: Manual console interception

import { interceptConsole, stopInterceptConsole } from '@abbacchio/browser-transport'

interceptConsole({
  endpoint: 'http://localhost:4002',
  serviceName: 'my-frontend',
  appName: 'my-app',
})

console.log('Captured!')
console.warn('Warning captured!')
console.error('Error captured!')

stopInterceptConsole()

Option 3: Structured Logger

import { createLogger } from '@abbacchio/browser-transport'

const log = createLogger({
  endpoint: 'http://localhost:4002',
  serviceName: 'my-app',
  name: 'my-service',
})

log.info('User logged in', { userId: 123 })
log.warn('Rate limit approaching', { current: 95, max: 100 })
log.error('Failed to fetch', { endpoint: '/api/users', status: 500 })

// Create child logger with additional context
const requestLog = log.child({ requestId: 'abc-123' })
requestLog.info('Processing request')

Option 4: React Provider

import { AbbacchioProvider, useLogger } from '@abbacchio/browser-transport/react'

function App() {
  return (
    <AbbacchioProvider
      endpoint="http://localhost:4002"
      serviceName="my-react-app"
      captureConsole
      captureWebVitals
    >
      <MyApp />
    </AbbacchioProvider>
  )
}

function MyComponent() {
  const log = useLogger()
  return <button onClick={() => log.info('clicked')}>Click me</button>
}

Web Vitals

Capture Core Web Vitals (LCP, INP, CLS, FCP, TTFB) using Google's web-vitals library. Each vital is reported as both a log entry and an OTLP metric gauge.

Via Logger

import { createLogger } from '@abbacchio/browser-transport'

const log = createLogger({
  endpoint: 'http://localhost:4002',
  serviceName: 'my-app',
  captureWebVitals: true,
})

Via React Provider

<AbbacchioProvider
  endpoint="http://localhost:4002"
  serviceName="my-app"
  captureWebVitals
>
  <App />
</AbbacchioProvider>

Standalone

import { startWebVitalsCapture, stopWebVitalsCapture } from '@abbacchio/browser-transport'

startWebVitalsCapture(
  { captureLCP: true, captureINP: true, captureCLS: true },
  (logEntry) => console.log(logEntry),
  (metric) => console.log(metric),
)

Options

interface WebVitalsCaptureOptions {
  captureLCP?: boolean     // Largest Contentful Paint (default: true)
  captureINP?: boolean     // Interaction to Next Paint (default: true)
  captureCLS?: boolean     // Cumulative Layout Shift (default: true)
  captureFCP?: boolean     // First Contentful Paint (default: true)
  captureTTFB?: boolean    // Time to First Byte (default: true)
  reportAsMetrics?: boolean // Send as OTLP metrics too (default: true)
  goodLevel?: number       // Log level for "good" ratings (default: 30/info)
  needsImprovementLevel?: number // Log level for "needs improvement" (default: 40/warn)
  poorLevel?: number       // Log level for "poor" ratings (default: 50/error)
}

Output

Log entries include the vital name, value, rating, and metadata:

LCP 3060ms (poor)      → level: error
FCP 800ms (good)       → level: info
CLS 0.150 (needs-improvement) → level: warn
INP 120ms (good)       → level: info
TTFB 450ms (good)      → level: info

OTLP metrics are sent as gauges: web_vital.lcp, web_vital.inp, web_vital.cls, web_vital.fcp, web_vital.ttfb — each with a rating attribute.

Network Capture

Automatically capture HTTP requests and WebSockets.

Enabling at Creation

const log = createLogger({
  endpoint: 'http://localhost:4002',
  serviceName: 'my-app',
  captureFetch: true,
  captureXhr: true,
  captureWebSockets: true,
  includeBody: false,
  ignoreNetworkUrls: ['/analytics', /\.png$/],
})

Enabling at Runtime

log.enableNetworkCapture({
  captureFetch: true,
  captureXhr: true,
  captureWebSockets: true,
})

log.disableNetworkCapture()

Performance Capture

Capture main-thread jank (long tasks > 50ms) and slow event handlers via PerformanceObserver.

import { startPerfCapture, stopPerfCapture } from '@abbacchio/browser-transport'

startPerfCapture(
  {
    captureLongTasks: true,
    captureSlowEvents: true,
    captureMemory: true,
    slowEventThresholdMs: 100,
    memoryCaptureIntervalMs: 10000,
  },
  (entry) => console.log(entry),
)

Memory Profiler

Install an opt-in, bounded memory profiler for long-running browser investigations. Installation exposes a stopped console API; it does not create a sampling timer until start() is called.

import { installMemoryProfiler } from '@abbacchio/browser-transport'

installMemoryProfiler({
  domSelectors: {
    virtualRows: '[data-virtual-row-key]',
    editors: '.monaco-editor',
  },
  collectValues: () => ({
    framesReceived: applicationDiagnostics.framesReceived,
  }),
})

__abbacchioMemory.start({
  intervalMs: 30_000,
  maxSamples: 1_440,
  label: 'baseline-idle',
})

Use mark(label) or sample(label) for checkpoints, getSamples() and status() for inspection, and download() for a JSONL export. Samples contain only copied JSON values and the retained history is capped by maxSamples.

The global and downloaded filename prefix are configurable:

installMemoryProfiler({
  globalName: '__myAppMemory',
  filenamePrefix: 'my-app-memory',
  hot: import.meta.hot,
})

To keep a run after the tab closes, forward samples to Abbacchio as gauge metrics. Every point is tagged with the run's sessionId, so a run can be queried back out of the metrics table:

import { toMemoryProfilerMetrics } from '@abbacchio/browser-transport'

installMemoryProfiler({
  onSample: (sample) => {
    for (const point of toMemoryProfilerMetrics(sample, { prefix: 'client.memory' })) {
      client.addMetric({ ...point, type: 'gauge' })
    }
  },
})

See the browser memory profiling guide for a complete investigation workflow, sample format, interpretation guidance, persistence and SQL query recipes, and JSONL analysis examples.

Error Capture

Capture uncaught exceptions and unhandled promise rejections.

import { startErrorCapture, stopErrorCapture } from '@abbacchio/browser-transport'

startErrorCapture(
  {
    captureErrors: true,
    captureUnhandledRejections: true,
  },
  (entry) => console.log(entry),
)

OTLP Metrics & Traces

The client supports sending custom metrics and traces via the OTLP protocol.

Metrics

import { createLogger } from '@abbacchio/browser-transport'

const log = createLogger({ endpoint: 'http://localhost:4002', serviceName: 'my-app' })

log.metric({
  name: 'page_load_time',
  value: 1200,
  type: 'gauge',
  unit: 'ms',
  attributes: { route: '/dashboard' },
})

Traces

const span = log.startSpan('fetch-users', { route: '/api/users' })
try {
  const users = await fetchUsers()
  span.end('OK')
} catch (err) {
  span.end('ERROR')
}

API Reference

createLogger(options)

interface LoggerOptions {
  endpoint?: string       // OTLP server URL (default: 'http://localhost:4002')
  serviceName?: string    // OTLP service.name attribute (default: 'default')
  name?: string           // Logger name (default: 'app')
  enabled?: boolean       // Send logs (default: true)
  level?: number | 'trace' | 'debug' | 'info' | 'warn' | 'error' | 'fatal'
  batchSize?: number      // Logs per batch (default: 1000)
  flushInterval?: number  // Ms between flushes (default: 2000)
  includeUrl?: boolean    // Include page URL (default: false)

  // Web Vitals
  captureWebVitals?: boolean  // Capture LCP, INP, CLS, FCP, TTFB (default: false)
  webVitalsOptions?: WebVitalsCaptureOptions

  // Network Capture
  captureFetch?: boolean
  captureXhr?: boolean
  captureWebSockets?: boolean
  includeBody?: boolean
  includeHeaders?: boolean
  ignoreNetworkUrls?: (string | RegExp)[]
}

AbbacchioProvider (React)

<AbbacchioProvider
  endpoint="http://localhost:4002"
  serviceName="my-app"
  captureConsole={true}
  captureWebVitals={true}
  webVitalsOptions={{ captureLCP: true, captureINP: true }}
>
  {children}
</AbbacchioProvider>

useLogger() / useAbbacchio() (React Hooks)

const log = useLogger()
const { info, warn, error, metric, startSpan } = useAbbacchio()

Disabling in Production

const log = createLogger({
  serviceName: 'my-app',
  enabled: process.env.NODE_ENV !== 'production',
})

// Or toggle at runtime
const client = createClient({ enabled: false })
client.enable()
client.disable()

Log Levels

Compatible with Pino log levels:

| Level | Number | |-------|--------| | trace | 10 | | debug | 20 | | info | 30 | | warn | 40 | | error | 50 | | fatal | 60 |

Filtering captured console output

interceptConsole and AbbacchioProvider accept a level that sets the floor for what is sent to the server. console.debug maps to 20, console.log / console.info to 30, console.warn to 40 and console.error to 50, so level: 'info' keeps milestones and failures while dropping debug noise. Omit it to capture every level.

Passthrough to the browser console is never suppressed by level — the developer still sees everything locally.

Because interceptConsole merges options while capture is active, the floor can be retuned at runtime without remounting anything:

interceptConsole({ level: 'debug' }) // temporarily capture debug noise
interceptConsole({ level: 'info' })  // back to the shipping floor

License

MIT