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

@ciplnew/bugtracking-react

v1.0.0

Published

Report React exceptions to BugTrack (AppRadar)

Readme

BugTrack React package

Report React exceptions to BugTrack (AppRadar) — same ingest model as the Node (@ciplnew/bugtracking) and Laravel packages.

Dashboard: https://appradar.colanapps.in/login

Install

npm install @ciplnew/bugtracking-react

Setup

  1. Log in at https://appradar.colanapps.in/login
  2. Create a project — copy the project token
  3. Add env vars in your React app:

Vite (.env):

VITE_BUGTRACK_ENABLED=true
VITE_BUGTRACK_URL=https://appradar.colanapps.in/api/v1/ingest
VITE_BUGTRACK_KEY=your-project-token
VITE_BUGTRACK_ENVIRONMENT=production

Create React App:

REACT_APP_BUGTRACK_ENABLED=true
REACT_APP_BUGTRACK_URL=https://appradar.colanapps.in/api/v1/ingest
REACT_APP_BUGTRACK_KEY=your-project-token
REACT_APP_BUGTRACK_ENVIRONMENT=production
  1. Wire in main.jsx / index.js:
import React from 'react';
import ReactDOM from 'react-dom/client';
import {
  init,
  captureWindowErrors,
  BugTrackErrorBoundary,
} from '@ciplnew/bugtracking-react';
import App from './App';

init({
  enabled: true,
  url: import.meta.env.VITE_BUGTRACK_URL,
  key: import.meta.env.VITE_BUGTRACK_KEY,
  environment: import.meta.env.VITE_BUGTRACK_ENVIRONMENT || 'production',
});

captureWindowErrors();

ReactDOM.createRoot(document.getElementById('root')).render(
  <BugTrackErrorBoundary fallback={<p>Something went wrong.</p>}>
    <App />
  </BugTrackErrorBoundary>
);

Manual report

import { report } from '@ciplnew/bugtracking-react';

try {
  // ...
} catch (err) {
  await report(err, { user: { id: user.id, email: user.email } });
  throw err;
}

Test

Error Boundaries catch render errors (not click-handler throws). Temporary test component:

function Boom() {
  throw new Error('My first BugTrack React error');
}

// render <Boom /> once inside App to trigger the boundary

Or report from a click handler manually:

import { report } from '@ciplnew/bugtracking-react';

<button
  type="button"
  onClick={() => report(new Error('My first BugTrack React error'))}
>
  Report test error
</button>

Then check the project in AppRadar.

What is reported

| Event | Reported? | |-------|-----------| | React render crash (Error Boundary) | Yes | | window.onerror / unhandled promise | Yes (if captureWindowErrors()) | | Manual report(err) | Yes | | Client HTTP status below 500 on Error | No (same as Node/Laravel) |

Options

| Option | Vite env | CRA env | Default | |--------|----------|---------|---------| | enabled | VITE_BUGTRACK_ENABLED | REACT_APP_BUGTRACK_ENABLED | false | | url | VITE_BUGTRACK_URL | REACT_APP_BUGTRACK_URL | — | | key | VITE_BUGTRACK_KEY | REACT_APP_BUGTRACK_KEY | — | | environment | VITE_BUGTRACK_ENVIRONMENT | REACT_APP_BUGTRACK_ENVIRONMENT | production | | timeoutMs | VITE_BUGTRACK_TIMEOUT_MS | REACT_APP_BUGTRACK_TIMEOUT_MS | 3000 |