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

@webreflection/signal

v2.1.2

Published

A minimalistic signals implementation

Downloads

1,397

Readme

@webreflection/signal

Coverage Status build status

Social Media Photo by Louis Reed on Unsplash

A minimalistic signals implementation, derived from the post Signals: the nitty-gritty, which size, once minified and brotlied, is 528 bytes.

  • no automatic effect disposal except when an outer effect has inner effects and the outer effect dispose() is invoked
  • computed are lazily initialied but updated per each signal change they depend on, unless a batch operation is updating all inner signals at once
  • no fancy features from other libraries

For anything more complex please check usignal out.

exports

  • signal(value) to create a new signal with a reactive .value
  • computed(fn[, initialValue]) to create a computed signal with a read-only .value
  • effect(fn) to create an effect and return a dispose function
  • batch(fn) to update multiple signals at once and invoke related effects once
  • untracked(fn) to make a callback that can read some signals without subscription to them
  • Signal to compare via instanceof Signal instances
  • Computed to compare via instanceof Computed instances

Computed accepts an initial value to pass to the callback. The callback will keep receiving the previous value on each new invoke.

example

// import {signal, effect} from 'https://unpkg.com/@webreflection/signal';
// const {signal, effect} = require('@webreflection/signal');
import {signal, effect} from '@webreflection/signal';

const single = signal(1);
const double = signal(10);
const triple = signal(100);

const dispose1 = effect(() => {
  console.log(`
  #1 effect
    single: ${single}
    double: ${double}
  `);
});

const dispose2 = effect(() => {
  console.log(`
  #2 effect
    double: ${double}
    triple: ${triple}
  `);
});

++double.value;
// logs single 1, double 11
// logs double 11, triple 100

dispose2();

++double.value;
// logs single 1, double 11