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

@kipkap/debug-bar-plugin-react-renders

v0.3.0

Published

Debug-bar plugin: per-component React render counts with on-page highlighting.

Readme

@kipkap/debug-bar-plugin-react-renders

Debug-bar plugin that counts React re-renders per component and highlights them on the page (react-scan style), built on bippy.

npm i @kipkap/debug-bar-plugin-react-renders

Install the hook first — this is the #1 gotcha

React only reports renders if a DevTools hook exists before react-dom loads. Because import statements are hoisted, calling installReactRenderHook() in the same file as your app runs after react-dom is already imported — too late.

So make it the very first import of your entry, via the side-effect subpath:

// main.tsx / app.jsx — the FIRST line, before any React import
import '@kipkap/debug-bar-plugin-react-renders/install';

import { createRoot } from 'react-dom/client';
// ... the rest of your app

Inertia (Laravel): in resources/js/app.jsx, put it above @inertiajs/react:

import '@kipkap/debug-bar-plugin-react-renders/install'; // must be first
import { createInertiaApp } from '@inertiajs/react';
import { createRoot } from 'react-dom/client';

Verify: in the browser console, window.__REACT_DEVTOOLS_GLOBAL_HOOK__.renderers.size should be ≥ 1. If it's 0, the hook is still loading too late.

Add the plugin to the bar

import { DebugBar } from '@kipkap/debug-bar-react';
import { reactRendersPlugin } from '@kipkap/debug-bar-plugin-react-renders';

<DebugBar theme="dark" plugins={[reactRendersPlugin()]} />;

Full docs in the repo.

MIT © Dries Heyninck