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

@barelyhuman/pipe

v0.2.3

Published

A tiny pipe utility

Downloads

12

Readme

@barelyhuman/pipe

A tiny pipe utility

npm

Why?

Tired of copying it around

Highlights

  • Tiny API
  • Clonable
  • Lazy Execution
  • Plugins

Usage

The util was built to abstract async manipulation from the actual flow and make it look cleaner when working with arrays

This is primarily for dealing with nested function calls and hiding the async logic

Eg:

const value = await Promise.all(something.map(id => fetchById(id)))

// Could be written as

// before v0.2.3
const value = await pipe(something)
  .map(id => fetchById(id))
  .to(x => Promise.all(x))
  .run()

// from v0.2.3
const value = await pipe(something)
  .map(id => fetchById(id))
  .run()

// or if you don't like magic then, but at this point
// there's no difference between this and the original
// statement
const value = await pipe(something)
  .to(previous => previous.map(id => fetchById(id)))
  .to(x => Promise.all(x))
  .run()

Clonable

The pipes are clonable and each have their own scope

A very simple example would be

Eg:

const basePipe = pipe(1).to(x => x * 2)
const nextPipe = pipe(basePipe).to(x => x * 3)

const valTwo = await nextPipe.run() // 6
const valOne = await basePipe.run() // 2

Lazy Execution

As shown in the examples the actual execution of the given data isn't started unless .run is triggered. This makes it easier to transfer context around if needed and in a defined sequence, also makes it easier to extend.

Plugins

You can read about them in PLUGINS.md

MIT