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

react-instance-hook

v1.0.2

Published

React hook for creating instance variables within a functional component.

Downloads

5

Readme

react-instance-hook

Build Status

A React Hook that provides a simple way to avoid out-of-date state values in memoized functions

Provides an object that can be used to store instance variables.

Usage

import useInstance from "react-instance-hook";

// ...
const [instance: Object, updateInstance: Function] = useInstance(initialInstanceState: Object);
// OR
const [instance: Object, updateInstance: Function] = useInstance(() => Object);

Why use this?

When using useMemo or useCallback the state values from useState are captured and therefore could be out of date.

For example

function MyComponent() {
  const [value, setValue] = useState(2);
  const double = useCallback(() => setValue(value * 2), []);
  return <Widget value={value} setValue={setValue} double={double} />;
}

The above memoizes the double callback using the useCallback hook to avoid causing the Widget to re-render every time MyComponent rerenders. But there is a bug in this code! When Widget calls double it will always return 4. This is because the initial value of 2 is captured in the closure passed to useCallback.

To workaround this problem we can create an instance object and as the object reference is captured the problem goes away:

function MyComponent() {
  const [{ instance }] = useState({ instance: { value: 2 } });
  const double = useCallback(() => (instance.value = instance.value * 2), []);
  return <Widget value={instance.value} setValue={setValue} double={double} />;
}

But wait! This also has a bug. The widget does not receive the doubled value. This is because no state has changed and so the component does not rerender.
useInstance provides a function you can call to force an update to occur.

function MyComponent() {
  const [instance, update] = useInstance({ value: 2 });
  const double = useCallback(() => update((instance.value *= 2)), []);
  return <Widget value={instance.value} setValue={setValue} double={double} />;
}

Note that the update call does nothing with the value passed to it. The following would be equivalent:

const double = useCallback(() => {
  instance.value *= 2;
  update();
}, []);

Caution

I have been playing with hooks in anger only a short time. This could well be an anti-pattern! Use your judgement and please do read the source code in index.js to understand how it works.