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

reactive-state-tree

v0.3.3

Published

A partially global state management that doesn't require optimisation.

Readme

Reactive State Tree

A partially global state management that doesn't require optimisation.

Motivation

State management is hard, especially if a state effects multiple components which are in seperate branch of the component tree. Using Context Api in this scenario requires lots of optimisations with useRef, useCallback etc. and of course their deps needs to be managed. This library provides as clean as possible api without dealing with this overhead.

How to use

Installation

npm install reactive-state-tree

or

yarn add reactive-state-tree

Usage

Create a state tree

// state.js
import { createReactiveContext } from 'reactive-state-tree';

// The api returns tuple instead of object to make it easy to rename
const [Context, Provider, useRootState, useSelector] = createReactiveContext({
  count: 1,
  query: '',
});

export { Context, Provider, useRootState, useSelector };

Place the provider in component tree.

// App.js
import React from 'react';
import { Counter, Input, Root } from './components';

const App = () => {
  <Provider>
    <Root />
    <Counter />
    <Input />
  </Provider>;
};

Access the state via hooks exposed by the state

// components.js
import React from 'react';
import { useSelector, useRoot } from './state';

export const Counter = () => {
  const [count, setCount] = useSelector('count');

  const handleIncrement = () => setCount(count => count + 1);
  const handleDecrement = () => setCount(count => count - 1);

  return (
    <div>
      <label>Count: {count}</label>
      <button onClick={handleIncrement}>Inc</button>
      <button onClick={handleDecrement}>Dec</button>
    </div>
  );
};

export const Input = () => {
  const [query, setQuery] = useSelector('query');

  const handleUpdate = e => setQuery(e.target.value);

  return (
    <div>
      <label>Query: {count}</label>
      <input onChange={handleUpdate} value={query} />
    </div>
  );
};

export const Root = () => {
  const [rootState, setRootStae] = useRoot();

  const initialState = React.useRef(rootState);

  const handleReset = () => setRootState(initialState.current);

  return (
    <div>
      <pre>{JSON.stringify(rootState)}</pre>
      <button onClick={handleReset}>Reset</button>
    </div>
  );
};

So what is the catch? Same thing can be achieved by using useState hook. Not really, this example shows the most basic usa case. Please check the examples below.

Examples

More examples are coming...

API Reference

| Api | Params | Description | | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------- | | Provider | initialState | Provider | | Context | none | Context | | useRoot | none | Hook returns a tuple with root state and root state updater like React.useState | | useSelector | key: string (key of the given state), condition: callback function takes state and returns boolean, based on returned boolean the state will be updated or not | Hook returns a tuple with root state and root state updater like React.useState |

Planned Features

  • Compostion api which will provide create another state tree by using other state trees.
  • Dev tool, will help to track changes and exlore states.
  • map api, will allow to use mapped value directly from the state

Contribution

This project 100% open to any kind of contribution.