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

rsignal

v0.0.4

Published

A React lib for controlling app flow

Downloads

5

Readme

[R]eact [Signal]

A React lib for controlling app flow

Installation

with NPM

npm i rsignal --save

with YARN

yarn add rsignal

Motivation

This library is inspired by Redux Saga. rsignal does not require any state management. You can manage the state of application manually. A heart of rsignal is signal.

Creating a signal is very simple

import { signal, delay } from "rsignal";

// create a signal
const greetingSignal = signal();

// handle signal emitting
greetingSignal.onEmit(() => {
  alert(`Hello ${greetingSignal.payload()}`);
});

// emit greetingSignal with payload
greetingSignal("World"); // an alert will shows `Hello World`

let count = 0;
const incrementSignal = signal();

// handle increment
incrementSignal.onEmit(() => {
  alert(count);
});

const increment = () => {
  // emit incrementSignal with update effect
  incrementSignal(() => {
    count++;
    // after exiting the effect, incrementSignal will be emitted
  });
};

const incrementAsync = () => {
  // even we can emit signal with async effect
  incrementSignal(async () => {
    await delay(1000);
    count++;
  });
};

// consume the signal with React component
const CounterApp = () => {
  // the CounterApp will re-render whenever incrementSignal is emitted
  useSignal(incrementSignal);

  return (
    <>
      {/* render latest value of count */}
      <h1>{count}</h1>
      <button onClick={increment}>Increment</button>
      <button onClick={incrementAsync}>Increment Async</button>
    </>
  );
};

Recipes

Using spawn function and its context

A spawn execute an effect and it keeps the execution context alive, by default, the context will be disposed after effect execution is finished

import { spawn, signal, delay } from "rsignal";

const loginSignal = signal();

const loadDataEffect = async (context, url) => {};

const mainEffect = async (context) => {
  const { call, when, race, all } = context;
  // call another effect
  const result = await call(loadDataEffect, "DATA_URL");
  // wait for signal and return its payload
  const payload = await when(loginSignal);
  // racing effects
  const racingResults = await race({
    loadData: fork(loadDataEffect, "DATA_URL"),
    timeout: delay(3000),
  });
  // loadData wins
  if (racingResults.loadData) {
    // receive loadData result
    console.log(racingResults.loadData.payload());
  }
  // timeout wins
  else if (racingResults.timeout) {
    alert("Timeout");
  }
  // run effects in parallel
  const parallelResults = await all({
    data1: fork(loadData, "DAtA_URL_1"),
    data2: fork(loadData, "DAtA_URL_2"),
  });
  console.log(parallelResults.data1.payload());
  console.log(parallelResults.data2.payload());
};

spawn(mainEffect);