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

streamlets

v0.5.1

Published

protocol and utilities for light-weight data streams

Downloads

584

Readme

Streamlets

npm i streamlets

tests security Language grade: JavaScript coverage version docs

Streamlet is a protocol for handling streams of data / events.

  • ↕️ It allows for handling pullables (i.e. iterables), listenables (i.e. observables) and anything in between.
  • ⛓️ It allows for handling synchronous and asynchronous data sources.
  • ⏯️ It enables pausing / resuming streams.
  • 📦 It allows pretty light-weight primitives and tools.

The streamlets package includes typings and tools built around this protocol.

import { pipe, interval, tap, observe } from 'streamlets'

const obs = 
  pipe(
    interval(1000),
    tap(console.log),
    observe,
  )


setTimeout(() => obs.stop(), 2000)
setTimeout(() => obs.start(), 4000)

// > 0
// > 1
// ... paused for two seconds, no logs ...
// > 2
// > 3
// > ...

👉 Check out the wiki for installation and usage guides.

Prior Work

If you find this useful, you most probably want to use RxJS. This is an experimental work. If you are into these kinds of experiments, checkout the callbag standard as well. The main differences between streamlets and aforementioned libraries are:

  • ↕️ Streamlets and callbags handle both pullables and listenables, and anything in between. RxJS does not.
  • ⏯️ Streamlets support pausing / resuming by default. This can be added to callbags as well, not supported by the standard itself. RxJS does not support this.
  • 🚧 Streamlets can handle backpressure in a more nuanced way, since sinks can communicate to sources their data needs, and can pause/resume them.
  • 📦 Streamlets fall between Callbags and RxJS operators and utilities in terms of bundle size consumption, leaning more towards the more light-weight side. A simple app would be ~500B with Callbags, ~1KB with Streamlets and ~4KB with RxJS.
  • 🚀 Streamlets are as fast (in some cases marginally faster) than Callbags, and noticably faster than RxJS. Note that performance of FRP libraries is generally not the bottle neck in apps that use them, since they are used to handle async operations which are typically way costlier.
  • 🧠 Streamlets use less memory than both Callbags and RxJS.

Acknowledgement

The streamlet protocol is heavily influenced by the callbag standard. A lot of code and utilities built around callbags were directly adopted into utilities for streamlets, including (but not limited to):