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 🙏

© 2024 – Pkg Stats / Ryan Hefner

use-callback-stable

v1.0.2

Published

A faster, friendlier, and safer useCallback

Downloads

843

Readme

useCallbackStable

A friendlier, faster, and safer alternative to useCallback. It returns a stable function reference without needing a dependency array.

  • Memory Safe: Old closures are not retained, preventing potential memory leaks.
  • No Dependency Array Required: Simplifies code by eliminating the need for dependency arrays.
  • Versatile: The callback can even be passed outside of React components.

Installation

npm install use-callback-stable
yarn add use-callback-stable

Basic Usage

import React, { useState } from 'react';
import { useCallbackStable } from 'use-callback-stable';

const MyComponent = () => {
    const [count, setCount] = useState(0);

    const incrementState = useCallbackStable(() => {
        // You will always have the current value of variables.
        setCount(count + 1);
    });

    return (
        <div>
            <p>{count}</p>
            <button onClick={incrementState}>Increment State</button>
        </div>
    );
};

With useCallbackStable, you can be confident that your callback always has access to the latest state and props, and you won’t need to worry about dependency arrays or stale closures.

Memory Safety

In JavaScript, as long as a function is in memory, all the variables in its containing closure are also retained. This means that using useCallback and useEffect can inadvertently create memory leaks because they hold onto the entire state of your component at the time they were created. This problem can be compounded by memoized data and other callbacks.

By using useCallbackStable, you avoid retaining old closures, as it always references the latest version of your callback function. This leads to improved memory usage and prevents potential memory leaks.

For further details, see this article: React Closures and Memory Leaks.

Stable References

Because useCallback returns a new function reference whenever its dependency array changes, child components may re-render unnecessarily or trigger unwanted side effects.

With useCallbackStable, you get a single function reference that remains stable throughout the life of your component. It will always call the most recent version of your function, using your variables in their latest state. This helps prevent unnecessary re-renders and side effects in child components that depend on the callback.

How It Works

import { useCallback, useRef } from 'react';

function useCallbackStable<T extends any[], U>(callback: (...args: T) => U): (...args: T) => U {
    const callbackRef = useRef(callback);

    // Update the ref to the latest callback on each render
    callbackRef.current = callback;

    // Return a stable callback function
    return useCallback((...args: T) => {
        return callbackRef.current(...args);
    }, []);
}