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

@getlogflow/browser

v0.1.0

Published

Browser SDK for LogFlow — auto-capture JS errors and unhandled rejections

Downloads

39

Readme

@getlogflow/browser

Browser SDK for LogFlow — automatically captures JavaScript errors, unhandled promise rejections, and lets you send custom log events from your frontend.

Install

npm install @getlogflow/browser

Quick start

import { LogFlowBrowser } from '@getlogflow/browser'

const logger = new LogFlowBrowser({
  apiKey: 'lf_your_api_key',
  service: 'my-frontend',
  environment: 'production',
  release: '1.2.3',           // optional: app version or git SHA
})

// That's it — window.onerror and unhandledrejection are captured automatically.

// Manual logging:
logger.info('Page loaded', { route: '/dashboard' })
logger.error('Payment failed', { userId: '123', amount: 99 })

Via <script> tag (CDN)

<script src="https://unpkg.com/@getlogflow/browser/dist/index.global.js"></script>
<script>
  const logger = new LogFlowBrowser.LogFlowBrowser({
    apiKey: 'lf_your_api_key',
    service: 'my-frontend',
  })
</script>

Options

| Option | Type | Default | Description | |--------|------|---------|-------------| | apiKey | string | required | Your LogFlow project API key | | service | string | "browser" | Service name shown in LogFlow | | baseUrl | string | "https://api.getlogflow.com" | API endpoint override | | captureErrors | boolean | true | Auto-capture window.onerror | | captureUnhandled | boolean | true | Auto-capture unhandledrejection | | captureConsoleErrors | boolean | false | Intercept console.error calls | | ignoreErrors | (string \| RegExp)[] | [] | Patterns to ignore | | maxErrorsPerMinute | number | 20 | Rate limit for auto-captured errors | | environment | string | — | Added to every log's metadata | | release | string | — | App version / git SHA | | onError | (err: Error) => void | — | Called when SDK fails to send |

Auto-captured metadata

Every error captured automatically includes:

  • url — current page URL
  • userAgent — browser user agent
  • filename, lineno, colno — error source location
  • stack — full stack trace
  • type"uncaught_error" | "unhandled_rejection" | "console_error"
  • environment, release — if provided in options

React example

// app/error-boundary.tsx
import { LogFlowBrowser } from '@getlogflow/browser'

const logger = new LogFlowBrowser({
  apiKey: process.env.NEXT_PUBLIC_LOGFLOW_API_KEY!,
  service: 'web',
  environment: process.env.NODE_ENV,
})

export function reportError(error: Error, context?: Record<string, unknown>) {
  logger.error(error.message, { stack: error.stack, ...context })
}

Page unload

The SDK uses fetch with keepalive: true on pagehide and visibilitychange, so queued logs are flushed even when the user closes the tab.

License

MIT