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

@whatitbroke/react

v1.0.4

Published

React adapter, Error Boundary, hook rule analyzer, and component tree inspector for WhatItBroke

Readme

@whatitbroke/react

React Adapter, Error Boundary, Component Render Path Tracer, and Hook Rules Analyzer

npm version License: MIT

@whatitbroke/react provides seamless error capture and root-cause analysis for React 18 & 19 applications, including component render hierarchy reconstruction and conditional hook violation detection.


Installation

npm install @whatitbroke/react @whatitbroke/core @whatitbroke/shared

Features

  • <WhatItBrokeBoundary>: Drop-in React Error Boundary component with customizable fallback UI and interactive developer overlay.
  • Component Render Path: Parses React's componentStack into a chronological root-to-leaf path (e.g. App ──► Dashboard ──► UserProfile).
  • Hook Rules Detector: Statically diagnoses conditional useState/useEffect calls, hook count mismatches, and missing dependency arrays.
  • Async Race Detection: Detects when components attempt to render data before asynchronous useQuery or fetch calls have completed.

Usage

1. Wrap Your Application with <WhatItBrokeBoundary>

import React from 'react';
import ReactDOM from 'react-dom/client';
import { WhatItBrokeBoundary } from '@whatitbroke/react';
import App from './App';

ReactDOM.createRoot(document.getElementById('root')!).render(
  <React.StrictMode>
    <WhatItBrokeBoundary
      showOverlay={process.env.NODE_ENV === 'development'}
      fallback={<div>An unexpected error occurred. Our team has been notified.</div>}
      onError={(report) => {
        console.error('WhatItBroke Report:', report);
      }}
    >
      <App />
    </WhatItBrokeBoundary>
  </React.StrictMode>
);

2. Hook Rules Violation Detection

When React throws Rendered fewer hooks than expected, WhatItBroke isolates the exact conditional branch causing the discrepancy:

// ❌ Dangerous: Hooks inside conditions
function Profile({ user }) {
  if (!user) return <Loading />;
  
  // WhatItBroke detects this conditional hook violation and provides the fix!
  const [data, setData] = useState(null);
  ...
}

3. Programmatic React Adapter

import { ReactAdapter } from '@whatitbroke/react';
import { WhatItBrokeCore } from '@whatitbroke/core';

const core = new WhatItBrokeCore();
const adapter = new ReactAdapter(core);

// Analyze React error with componentStack:
const report = await adapter.handleReactError(error, {
  componentStack: errorInfo.componentStack
});

console.log(report.context.executionPath);
// ['App', 'Dashboard', 'UserProfile']

Zero-Bloat Guarantee

@whatitbroke/react contains zero Vue, Angular, or backend Node.js code. It adds less than 8 kB to your frontend bundle and has react as an optional peerDependency.

License

MIT © WhatItBroke Team