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

state-watch

v0.0.7

Published

this is a state management control system to help you forget about redux complexity

Downloads

11

Readme

SMC

Why SMC?

No more worries about seting up redux or any other complicated, heavy package. With SMC you only need useSegment hook or new Segment() and that's it!

Example with useSegment

  1. Initiate Segment in Component1
  const defaultForSegment1 = {
    name: "Segment1",
    defaultValue: {
      val1: "test1",
      val2: "test2",
      val3: { nestedVal: "nested value", test: "cool1", secondNested: { val4: "test4" } },
    },
  };

  const segment = useSegment(defaultForSegment1);
  1. Connect to Segment1 in Component2

    const segment = useSegment({ name: "Segment1"});

  2. useSegment methods (details are WIP):

    • update
    • watch
    • get
    • segmentValue
    • delete

Example with new Segment()

  1. Initiate Segment in .ts file
  //init schema fro the segment

  type Segment1 = {
    test1: string;
    test2: string;
  };

  //Init Segment
  const testSegment = new Segment<Segment1>("test segment", { test1: "test1", test2: "test2" });

  //get all values
  function getAll() {
    return testSegment.getValues();
  }

  //init generric setter
  function segment1Setter(key: Paths<Segment1>, value: Segment1[keyof Segment1]) {
    testSegment.update({ [key]: value });
  }

  //init generric getter
  function segment1Getter(key: Paths<Segment1>): Segment1[keyof Segment1] {
    return testSegment.get(key);
  }

  //init watcher for spesific value
  function whatchFor(params: Parameters<typeof testSegment.watch>[0]) {
    testSegment.watch(params);
  }

  export { segment1Setter, segment1Getter, whatchFor, getAll };

Session and Local Storage

  1. Ability to persist segment value state to localStorage or sessionStorage

    You can now optionally persist your segment state by passing a saveTo option when initializing a segment via useSegment.

  const segment = useSegment({
   name: "Segment1",
   defaultValue: {
     val1: "value",
     val2: "value",
   },
   options: {
     saveTo: "localStorage", // or "sessionStorage"
   },
  });

Coming Soon

Ability to persist partial segment value state to localStorage or sessionStorage