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

@bugcapsule/react

v0.4.0

Published

React helpers for the BugCapsule web SDK: actions, tracked inputs, state, error boundary and a React Router integration.

Readme

@bugcapsule/react

React hooks and components for @bugcapsule/web.

npm install @bugcapsule/[email protected] @bugcapsule/[email protected]   # same version for both

Requires React 18+. The React Router listener needs React Router 6.4+. Setup guide: docs.bugcapsule.com/web.

import { BugCapsuleErrorBoundary, BugCapsuleCaptureButton } from '@bugcapsule/react';
import { BugCapsuleRouteListener } from '@bugcapsule/react/react-router';

<BrowserRouter>
  <BugCapsuleRouteListener />
  <BugCapsuleErrorBoundary fallback={<Oops />}><Routes>…</Routes></BugCapsuleErrorBoundary>
  <BugCapsuleCaptureButton />
</BrowserRouter>

API

  • useBugCapsuleAction(id, handler): semantic action (recorded, replayed by id).
  • useTrackedInput(id, { sensitive }): ref callback for uncontrolled inputs.
  • useTrackedState(id, initial): controlled value recorded and replayable.
  • useBugCapsuleState(key, value, restore): component/store state in checkpoints.
  • <BugCapsuleErrorBoundary fallback onError>: reports render errors as a failure (capsule) and a handled error event with contexts.react.componentStack; fallback(error, reset, eventId).
  • reactErrorHandler('uncaught' | 'caught' | 'recoverable'): React 19 root callbacks (createRoot(el, { onUncaughtError: reactErrorHandler() })).
  • <BugCapsuleFeedbackWidget theme={…} /> / useFeedbackWidget(options): the opt-in user feedback widget while mounted.
  • <BugCapsuleCaptureButton>: QA capture button (not rendered in production mode).
  • @bugcapsule/react/react-router: <BugCapsuleRouteListener routes={routes} /> records location changes with push/pop/replace (React Router 6.4+, tested with 7) and names pageload/navigation transactions after the matched route pattern (/product/:id; without routes, id-like segments become :id).

Background operation and failed screens

SDK initialization adds no UI. Capture and feedback widgets are explicit opt-ins. Wrap the app (or individual screens) in BugCapsuleErrorBoundary to contain render failures. Without a fallback prop it displays a neutral message and a Try again button, reports the error through the existing background pipeline, and never renders exception details. Retrying remounts the failed children; it does not repair external application state. Supply fallback for localized/branded UI (an explicit null still suppresses it). Global error callbacks report async errors but cannot restore a crashed React tree; use the boundary for that.