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

use-only-change-effect

v1.0.4

Published

You want to use a useEffect every time some value or values are changed but you don't want it to be called on initial render? use-only-change-effect got you covered!

Readme

:dizzy: use-only-change-effect

You want to use a useEffect every time some value or values are changed but you don't want it to be called on initial render? use-only-change-effect got you covered!

Motivation

React hooks are great, we can use useEffects to run callbacks after the components mounts, when it unmounts and when some values are changed.

But the thing with useEffects that depend on some values in their dependencies array is that they run also after the initial render, even if the value in the dependencies array doesn't change, (well, it "changes" from undefined to its current value).

In the good(?) old days of class components, we had the "componentWillReceiveProps" method that got called on every prop change but not on initial render, but only when new props were received (changed). Many times we want this behavior with hooks too.

So here comes "useOnlyChangeEffect" that will act like the useEffect we all love but will run only when the value actually changes.

Installation

npm install --save use-only-change-effect

or

yarn add use-only-change-effect

Usage

import useOnlyChangeEffect from 'use-only-change-effect';


const MyComponent = ({ value }) => {
    
    // this console.log will run only when the "value" prop changes, and not on initial render too.
    useOnlyChangeEffect(() => {
        console.log('I got called!')
    }, [value])

    return null
}