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 🙏

© 2025 – Pkg Stats / Ryan Hefner

use-react-signal

v1.0.0

Published

Replace useState with useSignal and forget about performance issues

Readme

use-react-signal

Replace useState with useSignal and forget about performance issues.

npm install use-react-signal

Activate the plugin to optimise all application components to become observers. No explicit observation or memo components needed.

import babelPlugin from "use-react-signal/babel-plugin";
import swcPlugin from "use-react-signal/swc-plugin";

The useSignal hook has the same signature as useState. The difference is that the state is a signal. You access and observe the value with .value.

import { useSignal } from "use-react-signal";

function Counter() {
  const [count, setCount] = useSignal(0);

  return (
    <button onClick={() => setCount((current) => current + 1)}>
      Count {count.value}
    </button>
  );
}

Why?

The primary reason developers leans on state management beyond useState is because of its performance characteristics. With shallow value comparison React quickly hits performance issues, especially using context.

By simply making all components observers using the plugin and replacing useState with useSignal, your React components will optimally reconcile from contexts and props passing out of the box.

The library is designed to showcase how React itself could provide such a primitive natively.

Component behavior

By default useState causes all nested components to reconcile. With context useState will cause all consuming components and their nested components to reconcile.

With use-react-signal your components do not reconcile by default. They rather observe by default. That means exposing a signal as a prop or on a context will not cause the component to reconcile, only accessing the signal value will.

Effects and Computed

Other reactive solutions also includes their own observable effects and computed. This is not strictly necessary for React. Since signal values can still be shallow compared, just like useState, you on useEffect and useMemo as normal. Linters and typing works as normal

function Counter() {
  const [count, setCount] = useSignal(0);

  const doubled = useMemo(() => count.value * 2, [count.value]);
}