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

wo-library

v5.0.13

Published

A component library smooth on the edges

Readme

wo-library

React components with minimum styling, to be used along with any other design system.

Optimizations

Providers

  • When using useMethods from the react-use library,

    • To create dispatcher methods, memoize the state argument before passing it to the function by wrapping in a useMemo or else the provider would return new state and methods everytime, causing extra re-renders.

    • Wrap the returned methods object in another useMemo making sure that it isn’t treated as a new variable even when the state changes.

  • Create two providers, one with the state values and the others with the dispatcher/methods values. Since the methods are fixed, this way any components consuming only the methods would not be re-rendered even if the state of the provider changes.