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

@tater-archives/react-current-ref

v1.0.3

Published

Utilities to simplify using refs to avoid state closure

Downloads

5

Readme

react-current-ref

Utilities to simplify using refs to avoid state closure.

useValueRef

Creates a ref that is always updated whenever the value changes, so it is safe to use in async functions and event listeners that are set once and such.

Note that updating the value WILL NOT cause a re-render, at least for parts of the code using the ref, so any references in the DOM won't update, and passing ref.current as a prop to components will not re-render them. You can pass the ref itself as a prop to provide the up-to-date value, although this still will not cause a re-render.

Example Usage

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

const countRef = useValueRef(count);

// Set a timeout on mount
useEffect(() => {
    setTimeout(() => {
        console.log(countRef.current);
        // Even if count changes, this will print the latest value since it is a ref
    }, 1000);
}, [])

useFunctionRef

Creates a wrapper function that does not change but always calls the latest value of func.

Example Usage

const handleResize = useFunctionRef(event => {
    // ... other code
});

useEffect(() => {
    // Because handleResize always returns the same function, there will only
    // be one DOM operation
    document.addEventListener('resize', handleResize);
    
    // Standard cleanup function
    return () => document.removeEventListener('resize', handleResize);
}, [handleResize]);