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

mz-shared-state

v1.0.4

Published

```terminal > npm install mz-shared-state ```

Downloads

530

Readme

Global State Management Made Easy

Let's be honest, React's state management is pretty shit. From writing a complicated provider to wrapping our component inside that provider component is not the cleanest way to do it. It creates a dependency of the state with the structure. If I want to make the context available to a new component tommorow, It requires me to update the structure to accomodate the component inside the provider and we dont wanna do that. Don't worry, there is a simpler way.

Installation

> npm install mz-shared-state

Usage

Let's say we want to share a counter between two components. We will first create a central provider and instantiate our shared state.

//countStateProvider.js
import SharedState from "mz-shared-state";


let countState = new SharedState(0);


export default countState;

We now want to share this instance of shared state between components or code files.

//Component1.jsx
import countState from "./countStateProvider.js";
import { useState, useEffect } from "react";

export default function Component1() {
  const [localCount, setLocalCount] = useState(null);

  useEffect(() => {
    let unsubscribe = countState.subscribe(setLocalCount);

    //cleanup during unmounting
    return () => unsubscribe();
  }, []);

  function increment() {
    countState.publish(localCount + 1);
  }

  return (
    <>
      <p>{localCount}</p>
      <button onClick={increment}>+</button>
    </>
  );
}
//App.jsx
import Component1 from "./Component1";

function App() {
  return (
    <>
      <Component1></Component1>
      <Component1></Component1>
    </>
  );
}

export default App;

alt text