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

@errpulse/react

v0.1.4

Published

ErrPulse React frontend SDK — catch every frontend error automatically

Readme

@errpulse/react

Frontend error monitoring SDK for React. Part of ErrPulse — the error monitoring tool that runs with one command.

Installation

npm install @errpulse/react

Quick Start

import { ErrPulseProvider } from "@errpulse/react";

function App() {
  return (
    <ErrPulseProvider endpoint="http://localhost:3800" projectId="my-web-app">
      <YourApp />
    </ErrPulseProvider>
  );
}

That's it. Errors, failed requests, and React crashes are captured automatically.

Manual Capture

import { useErrPulse } from "@errpulse/react";

function CheckoutButton() {
  const { captureError, captureMessage } = useErrPulse();

  const handleClick = async () => {
    try {
      await processPayment();
      captureMessage("Payment successful", "info");
    } catch (err) {
      captureError(err, { step: "payment" });
    }
  };

  return <button onClick={handleClick}>Checkout</button>;
}

What Gets Captured

| Error Type | How | | ---------------------------- | ----------------------------------------- | | JavaScript runtime errors | window.onerror | | Unhandled promise rejections | window.onunhandledrejection | | React component crashes | Error Boundary | | Failed fetch/XHR requests | fetch() + XMLHttpRequest interceptors | | console.error calls | Monkey-patch | | Resource failures (img, css) | Capture-phase error listener | | All HTTP requests | Fetch interceptor |

Provider Props

| Prop | Type | Default | Description | | ----------------------- | ----------- | ------------ | ------------------------------------------- | | endpoint | string | required | ErrPulse server URL | | projectId | string | undefined | Project identifier for multi-project setups | | captureConsoleErrors | boolean | true | Capture console.error calls | | captureFetch | boolean | true | Intercept and track fetch requests | | captureXHR | boolean | true | Intercept and track XMLHttpRequest calls | | captureResourceErrors | boolean | true | Capture failed img/script/css loads | | errorBoundaryFallback | ReactNode | undefined | Fallback UI for React crashes |

Error Correlation

The SDK automatically injects an X-ErrPulse-Correlation-ID header into every fetch request. When paired with @errpulse/node on the backend, the dashboard shows the full chain: user action -> frontend request -> backend error.

Documentation

License

MIT