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

react-state-logger

v0.1.0

Published

Lightweight React debugging hooks to log state changes, re-renders, and prop updates

Readme

React State Logger

A lightweight debugging utility for React to log:

  • 🟢 State changes
  • 🔁 Component re-renders
  • 🔍 Prop updates

Get structured logs instead of scattered console.log calls.


🚀 Installation

npm install react-state-logger

📦 Usage

Log State Changes

import { useStateTracker } from "react-state-logger"

const [count, setCount] = useStateTracker(0, "count")

Log Component Renders

import { useRenderTracker } from "react-state-logger"

useRenderTracker("App")

Log Prop Changes

import { useWhyDidYouUpdate } from "react-state-logger"

function Child({ value }) {
  useWhyDidYouUpdate("Child", { value })

  return <div>{value}</div>
}

🧪 Example

import {
  useStateTracker,
  useRenderTracker,
  useWhyDidYouUpdate
} from "react-state-logger"

function Child({ value }) {
  useWhyDidYouUpdate("Child", { value })
  return <div>{value}</div>
}

function App() {
  const [count, setCount] = useStateTracker(0, "count")

  useRenderTracker("App")

  return (
    <div>
      <button onClick={() => setCount(count + 1)}>
        {count}
      </button>

      <Child value={count} />
    </div>
  )
}

🧠 Why Use This?

Instead of:

console.log(state)

You get:

  • previous vs next values
  • render counts
  • prop differences
  • structured logs

⚠️ Notes

  • Works only in development mode
  • Uses shallow comparison

📄 License

MIT