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

@adamringhede/signal

v1.0.3

Published

A reactive primitive for updating state in an application.

Downloads

9

Readme

Signal

A reactive primitive for updating state in an application.

Signals represent state which can be derived using computations. These computations will hold on to the last computed value until signals it depend on change value. Signals and the reuslt of computations are functions that can be called to return their current value.

Effects can be used to subscribe to signals or computations and be triggered automatically whenever signals it or any of its upstream computations depend on change value.

The syntax is inspired by Angular Signals.

Install

npm i @adamringhede/signal

Usage

Creating signals

Signals are created using the signal<T>(value: T) function. This returns a function.

Reading signals

The value from a signal can be extrated by invoking the signal function.

const amount = signal(5)
amount() // 5

Updating signals

The signal can

const amount = signal(5)
amount.set(10)
amount() // 10

The signal can also be updated with regards to its current value using the .update(updateFn: (value) => T) method.

const amount = signal(5)
amount.update(value => value + 1)
amount() // 6

If the signal contains an object that you just want to update, you can use the .mutate(mutateFn: (value) => void) method to change the value. Note that this will not trigger effects to be called.

const amount = signal({a: 1})
amount.update(value => value.a += 1)
amount().a // 2

Computations

You can apply computations on one or more signals or even other computations by using the compute(fn: () => void) function. The computation will hold on to the most recently computed value.

Effects

You can trigger any kind of side effect whenever any upstream signal changes value. This is illustrated in the code below.

const a = signal(1)
const b = signal(2)
const c = computed(() => a() + b())

let effectResult: number[] = []
const e = effect(() => effectResult.push(c()))

expect(effectResult).toEqual([3])

a.set(3)
b.set(4)
expect(effectResult).toEqual([3,5,7])

e.destroy()

Remember to destroy effects when you want it to stop reacting to changes in signals.