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

@lerix-dev/lerix-react

v1.2.0

Published

Error tracking and Web Push notifications for React apps, backed by the Lerix platform.

Readme

@lerix-dev/lerix-react

Error tracking and Web Push notifications for React apps, backed by the Lerix platform. Built on the framework-agnostic @lerix-dev/lerix-core package.

Building a Next.js app? Use @lerix-dev/lerix-nextjs instead — it wraps this package with a provider pre-configured for the App Router and Pages Router, and pre-marked 'use client' so it works out of the box in Server Components.

Install

npm install @lerix-dev/lerix-react

Setup

1. Register the SDK

Wrap your app in LerixProvider, and LerixErrorBoundary to catch render errors:

import { LerixErrorBoundary, LerixProvider } from '@lerix-dev/lerix-react'

createRoot(document.getElementById('root')!).render(
  <LerixProvider
    options={{
      apiKey: 'your-api-key',
      projectId: 'your-project-id',
      debugMode: true,
    }}
  >
    <LerixErrorBoundary fallback={<p>Something went wrong.</p>}>
      <App />
    </LerixErrorBoundary>
  </LerixProvider>,
)

Registration with the backend runs once, on mount — safe even under React 18 StrictMode's double-effect-invocation in development, since Lerix.initialize() is re-entrant-safe.

LerixErrorBoundary only catches errors thrown during rendering (React's error boundary contract) — uncaught errors everywhere else (event handlers, async code, promise rejections) are still captured automatically via global handlers LerixProvider installs.

2. Report errors

import { useLerix } from '@lerix-dev/lerix-react'

function MyComponent() {
  const lerix = useLerix()

  const onSomethingFailed = () => {
    lerix.throwError('Something went wrong')
  }
}

Filtering errors

options also takes ignoreErrors and beforeSend, applied to every report (including LerixErrorBoundary). ignoreErrors runs first: a string drops any error whose message contains it (case-insensitive), a RegExp drops any messageit matches (empty strings are skipped). beforeSend gets a LerixErrorEvent and returns it (optionally modified) to send, or null to drop it; if it throws, the original is sent.

<LerixProvider
  options={{
    apiKey: 'your-api-key',
    projectId: 'your-project-id',
    ignoreErrors: ['ResizeObserver loop', /^ChunkLoadError/],
    beforeSend: (event) => (event.message.includes('extension://') ? null : event),
  }}
>

3. Push notifications

Copy the service worker into your app's public folder:

cp node_modules/@lerix-dev/lerix-core/sw/lerix-sw.js your-app/public/lerix-sw.js

Generate a Web Push key from the dashboard: Notifications → Settings → Web Push → Generate keys.

import { useLerixNotifications } from '@lerix-dev/lerix-react'

function MyComponent() {
  const notifications = useLerixNotifications()

  useEffect(() => {
    notifications.setOnNotificationReceived((payload) => {
      console.log(payload.title, payload.body)
    })
  }, [])

  const enablePush = async () => {
    await notifications.subscribe()
  }
}

API

| Export | Description | |---|---| | LerixProvider | Registers the SDK at mount. Wrap your app once, near the root. | | LerixErrorBoundary | Catches React render-tree errors and reports them. | | useLerix() | Returns the Lerix facade — throwError, getUserId, setUser/clearUser, reRegisterUser, etc. | | useLerixNotifications() | Returns the notifications API — subscribe, checkPermissionStatus, getRegisteredTokenId, topics, etc. |

Requirements

  • React 18+