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

@pack/errors-react

v0.1.1

Published

Pack error tracking for React

Downloads

304

Readme

@pack/errors-react

React bindings for Pack error tracking.

Install

npm install @pack/errors-react

Exports

  • usePackErrorTrack(isPreview?: boolean, errorTracking?, sessionId?)
  • PackErrorBoundary (errorTracking?, sessionId?, fallback? props)

Usage

import { PackErrorBoundary, usePackErrorTrack } from '@pack/errors-react';

const errorTracking = {
  dsn: 'https://[email protected]/ingest/PROJECT_ID',
};

function ErrorTracking({ isPreview, sessionId }: { isPreview: boolean; sessionId?: string }) {
  usePackErrorTrack(isPreview, errorTracking, sessionId);
  return null;
}

export function App({ isPreview, sessionId }: { isPreview: boolean; sessionId?: string }) {
  return (
    <>
      <ErrorTracking isPreview={isPreview} sessionId={sessionId} />
      <PackErrorBoundary
        errorTracking={errorTracking}
        sessionId={sessionId}
        fallback={<div>Something went wrong.</div>}
      >
        <Routes />
      </PackErrorBoundary>
    </>
  );
}

Runtime config

Provide tracking config directly to the hook and boundary:

  • dsn: https://PUBLIC_KEY@host/ingest/PROJECT_ID
  • sessionId (optional): server session id for client/server correlation. If omitted, the client attempts to read session_id from the __pack cookie.

Behavior

  • Tracks three client-side error types:
    • uncaught (window error)
    • unhandledrejection (window unhandledrejection)
    • react (PackErrorBoundary)
  • No events are sent when:
    • isPreview is true
    • errorTracking?.dsn is missing
  • Dedupes repeated errors per pathname and limits event volume:
    • max 10 errors per page
    • max 50 errors per session (sessionStorage)
  • Uses keepalive: true for background-safe event delivery.

Error boundary fallback

fallback may be:

  • a React node, or
  • a function receiving { error, resetError }

Example:

<PackErrorBoundary
  errorTracking={errorTracking}
  fallback={({ error, resetError }) => (
    <div>
      <p>{error.message}</p>
      <button onClick={resetError}>Try again</button>
    </div>
  )}
>
  <Routes />
</PackErrorBoundary>

Development

yarn
yarn build