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

signal-async

v0.2.0

Published

distinct utilities for signaling data in async contexts

Downloads

13

Readme

signal-async

NPM Version

distinct utilities for signaling in async contexts.

Installation

npm install signal-async

Usage

Dirty

Dirty signals are signals that can be marked and listened to. They trigger active listeners when they are emitted to.

import { dirty } from 'signal-async';

const { emit, signal } = dirty();

signal().then(() => {
	console.log('signal received');
});

emit();

However, if a signal is emitted before a listener is attached, the listener will not be triggered.

emit();

signal().then(() => {
	console.log('signal received'); // not triggered
});

Events

Events build on top of dirty signals. They allow for enqueuing data in a FILO queue and applying async iteration over the queue.

import { event } from 'signal-async';

const { iterator, enqueue } = event<number>();

enqueue(1);
enqueue(2);

for await (const item of iterator) {
	console.log(item);	// 1, 2
}

State

State allows for listening for a certain value, perfect for waiting for a 'ready' state or transmitting IO between async contexts.

import { state } from 'signal-async';

const { waitFor, set } = state<number>(1);

waitFor(2).then(() => console.log("this will print!"));

set(2);

Unlike dirty, this works even if the value is set before the listener is attached.

set(2);

waitFor(2).then(() => console.log("this will print!"));