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

@traceora/react

v0.4.8

Published

React instrumentation for Traceora

Readme

   

Connects React's lifecycle, your network requests, and unhandled errors into a single, comprehensive timeline — with a beautiful floating DevTools overlay.


📥 Installation

npm install @traceora/react @traceora/core

Tip: Also install @traceora/vite-plugin to instrument named function components with block bodies.


✨ Exports

| Export | Type | Description | |---|---|---| | <TraceoraProvider> | Component | Initializes the core engine, instruments fetch/XHR/History API, catches errors, shares the EventEmitter via React Context. | | <TraceoraErrorBoundary> | Component | Intercepts React render crashes → logs them to the timeline → shows a fallback UI. | | <TraceoraDevtools /> | Component | Floating, real-time visual timeline for development. Drop it in and go. | | useTrace() | Hook | Start an interaction trace. Its fetch() method propagates the trace ID to a request. | | useComponentTrace() | Hook | Tracks component mount & render. The Vite plugin injects it into supported named function components. |


🔧 Usage

1. Wrap your application

import {
  TraceoraProvider,
  TraceoraErrorBoundary,
  TraceoraDevtools,
} from '@traceora/react';

function App() {
  return (
    <TraceoraProvider>
      <TraceoraErrorBoundary>
        <YourApp />
        <TraceoraDevtools /> {/* Floating timeline overlay */}
      </TraceoraErrorBoundary>
    </TraceoraProvider>
  );
}

2. Trace interactions manually

import { useTrace } from '@traceora/react';

export function UserProfile() {
  const startTrace = useTrace();

  const handleSave = () => {
    // Links this click + any subsequent API calls under one Trace ID
    const trace = startTrace('Save_Profile');

    // Use the trace handle to correlate this request with the interaction.
    void trace.fetch('/api/save', { method: 'POST' });
  };

  return <button onClick={handleSave}>Save</button>;
}

Instrumentation is enabled in development by default. Set config={{ enabled: true }} to opt in elsewhere. Event history is capped at 1,000 by default. Request bodies and headers are excluded unless captureRequestBodies or captureRequestHeaders is enabled; inspect captured data carefully before enabling either option.


🔗 Related Packages

| Package | Role | |---|---| | @traceora/core | The underlying event engine | | @traceora/vite-plugin | Build-time instrumentation for supported named function components | | @traceora/next | Next.js-specific integration |