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

@siddheshtawde/why-did-it-render

v1.0.0

Published

A tiny dev-only React hook that logs exactly which props changed and caused a re-render — no heavy profiler required.

Readme

why-did-it-render

A tiny, dev-only React hook that tells you exactly which prop changed and caused a re-render — without pulling in a heavy profiler or wrapping your component tree.

npm install why-did-it-render

Usage

import { useWhyDidYouUpdate } from 'why-did-it-render';

function ExpensiveList({ items, onSelect, filter }) {
  useWhyDidYouUpdate('ExpensiveList', { items, onSelect, filter });

  return <ul>{/* ... */}</ul>;
}

That's it — one line, no HOC, no wrapper component. On every re-render after the first, it logs a collapsed console group showing exactly which props changed and their before/after values.

Options

useWhyDidYouUpdate('MyComponent', props, {
  // Skip props that legitimately change every render (e.g. inline callbacks)
  ignore: ['onClick'],

  // Force logging even in production (default: dev-only)
  enabled: true,

  // Flag props that changed by reference but are deep-equal —
  // usually caused by inline objects/arrays/functions (default: true)
  detectReferenceOnlyChanges: true,
});

What it catches

  • Real prop changes — the value actually changed, logged with before → after.
  • Reference-only changes — the value is deep-equal but a new object/array/function reference (a huge source of unnecessary re-renders from inline literals), flagged separately so you know it's safe to useMemo/useCallback away.

Production safety

The hook is a no-op when NODE_ENV === 'production' unless you explicitly pass enabled: true. Combined with tree-shaking and its ~1.5KB size, it's safe to leave the import in your codebase.

License

This project is licensed under the MIT License