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

async-iterator-demuxer

v1.0.0

Published

Create multiple async iterators of a single async-iterator/iterable.

Downloads

6

Readme

async-iterator-demuxer

Create multiple async iterators of a single async-iterator/iterable.

Allow multiple consumers of a single async iterator instance.

var demuxed= new AsyncIteratorDemuxer(async function*(){
	console.log("begin")
	yield 6
	yield 9
	return 42
})
async function readAll(iter, fn){
	for await(var el of iter){
		console.log(fn(el))
	}
}
readAll(demuxed, i=> i)
readAll(demuxed, i=> 3)
// prints: "begin", 6, 24, 9, 36
// note that "begin" is only printed once.

Warning

No effort is made to insure each reader gets consistent results.

The first active reader has special importance. It's reads are signalled to the other readers. This means:

  1. the first active reader will definitely get all reads
  2. the maximum take rate is governed by the first reader
  3. other readers will miss data if they are not iterating as fast as the first reader
  4. as a general rule, if you can ask for the next element in less time than the period between events, you should never miss any events.

Alternative implementation strategies for he future might be:

  1. advance only after all readers have read the current value
  2. buffer some historical set of reads for slower readers
  3. optional read-ahead buffering