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 🙏

© 2024 – Pkg Stats / Ryan Hefner

react-tagged-state

v2.1.0

Published

⚛️ Experimental reactive and atomic state manager

Downloads

401

Readme

React Tagged State

NPM version Package size typescript NPM license NPM total downloads NPM monthly downloads

⚛️ Global atomic state manager

React Tagged State uses signals API as SolidJS and S.js but without automatic deps tracking.

Basic Usage

import {
  createSignal,
  useSelector,
} from 'react-tagged-state';

// create a signal
const counter = createSignal(0);

const Counter = () => {
  // read value
  const count = useSelector(counter);

  return (
    <button
      onClick={() => {
        // update value
        counter((value) => value + 1)
      }}
    >
      {count}
    </button>
  );
};

API Overview

Signal

Signal is a value container. And also is just a function. You can read value by calling signal without arguments and write value by calling signal with next value. Simple.

import { createSignal } from 'react-tagged-state';

// create a signal
const counter = createSignal(0);

// read
const value = counter();

// write with value
counter(10);

// write with function
counter((count) => count + 1);

Event

Event is a "write-only" signal. You can't read value, but you can dispatch next value.

import { createEvent } from 'react-tagged-state';

// create an event
const reset = createEvent();

// dispatch
reset();

React & Hooks

useSelector bind signals with component. This is all what you need to sync signals with yuor components. You can use signals or selectors like you do in redux, of course.

Signal:

import {
  createSignal,
  useSelector,
} from 'react-tagged-state';

const counter = createSignal(0);

const Counter = () => {
  const count = useSelector(counter);

  return (
    <button
      onClick={() =>
        counter((value) => value + 1)
      }
    >
      {count}
    </button>
  );
};

Component will be re-rendered on signal's value change.

Selector:

import {
  createSignal,
  useSelector,
} from 'react-tagged-state';

const items = createSignal<
  Partial<
    Record<string, { id: string; title: string }>
  >
>({ id: { id: '0', title: 'title' } });

const Item = ({ itemId }: { itemId: string }) => {
  const item = useSelector(() => items()[itemId]);

  if (!item) {
    return null;
  }

  return <div>{item.title}</div>;
};

Component will be re-rendered on selected value change.

Signal's Selector:

import {
  createSignal,
  useSelector,
} from 'react-tagged-state';

const items = createSignal<
  Partial<
    Record<string, { id: string; title: string }>
  >
>({ id: { id: '0', title: 'title' } });

const Item = ({ itemId }: { itemId: string }) => {
  const item = useSelector(items, () => items[itemId]);

  if (!item) {
    return null;
  }

  return <div>{item.title}</div>;
};

Component will be re-rendered on selected value change. This variant subscribes only to provided signal's changes. You should prefer this way if selector read value from single signal.

Subscription

Signals and events have on method. You can use this method to subscribe to signals and events outside your components or in useEffect.

import {
  createSignal,
  subscribe,
} from 'react-tagged-state';

const counter = createSignal(0);

const unsubscribe = counter.on(
  (value) => {
    console.log(value);
  },
);

Callback will be called on signal's value change or event's dispatch.

Example

Open CodeSandbox

Performance

See results on js-framework-benchmark.