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

usegetstate

v1.0.3

Published

Pull the state you need

Downloads

6

Readme

usegetstate

usegetstate is a great way to pull the state from a react state hook. It works by storing a ref of the state and exposing a function to get that state. A simple example looks like this

import useGetState from "usegetstate";

const ExampleComponent: React.FC = () => {
  const [count, setCount, getCount] = useGetState(0);

  useEffect(() => {
    const interval = setInterval(() => {
      console.log(getCount());
    }, 1000);
    return () => clearInterval(interval);
  }, []);

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

Motivation

What is the best way to console log count exactly once a second?

const ExampleComponent: React.FC = () => {
  const [count, setCount] = useState(123);

  useEffect(() => {
    const interval = setInterval(() => {
      console.log(count);
    }, 1000);

    return () => clearInterval(interval);
  }, []);

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

Try Number 1

Add it to the useEffect dependency

const ExampleComponent: React.FC = () => {
  const [count, setCount] = useState(123);

  useEffect(() => {
    const interval = setInterval(() => {
      console.log(count);
    }, 1000);

    return () => clearInterval(interval);
  }, [count]); // <-- add count here

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

This sort of works except we recreate the effect when count is changed so we don't actually log every second, we get it one second after the button is clicked then one second on from that.

We can add some extra delta logic to solve this using deltas, but things are getting complicated fast...

Try Number 2

Use Ref

const ExampleComponent: React.FC = () => {
  const countRef = useRef(134);
  const [count, setCount] = useState(countRef.current);

  useEffect(() => {
    const interval = setInterval(() => {
      console.log(countRef.current);
    }, 1000);

    return () => clearInterval(interval);
  }, []);

  useEffect(() => {
    countRef.current = count;
  }, [count]);

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

This works at the cost of adding an extra place to store the data. We will have to keep this in sync from now on and is a little bit ugly.

Enter usegetstate

import useGetState from "usegetstate";

const ExampleComponent: React.FC = () => {
  const [count, setCount, getCount] = useGetState(countRef.current);

  useEffect(() => {
    const interval = setInterval(() => {
      console.log(getCount());
    }, 1000);
    return () => clearInterval(interval);
  }, []);

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

When using getState in your functions you ensure that you are always using the latest version of the state. This makes it super simple to write performant react code.

How often have we done something like this?

import doesSomethingImportant from "real-world-side-effects";

const App: React.FC = () => {
  const [count, setCount, getCount] = useGetState(countRef.current);

  const onClick = () => {
    setCount(count + 1);
    someFunction();
  };

  const someFunction = () => {
    thatOtherFunction();
  };

  const thatOtherFunction = () => {
    doesSomethingImportant(count);
  };

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

usegetstate Solves this too

import useGetState from "usegetstate";
import doesSomethingImportant from "real-world-sideeffects";

const App: React.FC = () => {
  const [count, setCount, getCount] = useGetState(countRef.current);

  const onClick = () => {
    setCount(count + 1);
    someFunction();
  };

  const someFunction = () => {
    thatOtherFunction();
  };

  const thatOtherFunction = () => {
    doesSomethingImportant(getCount());
  };

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