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

react-use-batched-state

v1.0.5

Published

React hook similar to `setState` but allowing for batched updates

Readme

react-use-batched-state

A hook that allows for batched updates in react.

Install

npm i react-use-batched-state

There are umd and es versions if you need.

Usage

Use it instead of React.useState wherever you need to batch updates (see the example). Typescript support is available. This package requires Promise to be available globally, it is not bundled as it's very much likely you already have one.

Motivation

In certain cases (generally, in effects) state updates initiated by React.useState setters are not batched, which leads to rerender for each setter call. Consider the following example:

import React, { useState, useCallback } from 'react';

export default function BatchedUpdateTest() {
  const [a, setA] = useState(0);
  const [b, setB] = useState(0);

  console.log(`render: a = ${a}, b = ${b}`);

  const setUpdate = useCallback(function setUpdate() {
    setTimeout(
      function (x) {
        setA(x);
        setB(x)
      },
      500,
      Math.random()
    );
  }, []);

  return (
    <button onClick={setUpdate}>set update</button>
  );
}

If we click on the button, we will see the console prints next two lines:

render: a = 0.8447694095332172, b = 0
render: a = 0.8447694095332172, b = 0.8447694095332172

Solution

react-use-batched-state supposed to solve the problem. You can use it in place of React.useState wherever you want updates to batch:

import React, { useCallback } from 'react';
import useBatchedState from 'react-use-batched-state';

export default function BatchedUpdateTest() {
  const [a, setA] = useBatchedState(0);
  const [b, setB] = useBatchedState(0);

  console.log(`render: a = ${a}, b = ${b}`);

  const setUpdate = useCallback(function setUpdate() {
    setTimeout(
      function (x) {
        setA(x);
        setB(x)
      },
      500,
      Math.random()
    );
  }, []);

  return (
    <button onClick={setUpdate}>set update</button>
  );
}

If we click the button now, the output would be

render: a = 0.8447694095332172, b = 0.8447694095332172

How it works

Internally it uses unstable_batchedUpdates from react-dom (which is not so unstable).

Requirements

This package requires Promise to be available globally, it is not bundled as it's very much likely you already have one.