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

highland-piper

v1.0.3

Published

Create highland pipelines with abort and finalize logic.

Downloads

3

Readme

highland-piper

Create first class pipelines that enable abort and finalise logic.

Use pure functions to create complex workflows and optimise data processing.

Getting started

transforms only

This is the simplest use case. It mirrors a basic highland pipeline. But it does allow for naming transforms.

Use .add to add a transform. All transforms are highland transforms just like a simple highland _.pipeline(...)

const _ = require('highland');
const piper = require('highland-piper');
const stream = _([ {title: 'The Title'} ]);

const pipeline = piper('title-changer');
pipeline.add('changeTitle', _.doto( obj => obj.title = 'New Title'));
stream.through(pipeline.consumer).each(o => console.log(o.title));

transforms and aborts

Aborts make a pipeline intelligent. You can skip unncessary processing for some objects without losing the data. Any aborted objects will be available for processing that starts after the pipeline ends. Think of it as a smart filter.

Use .abort to add an abort. Aborts take a name and a predicate. The predicate is a function that evaluates to true or false.

const _ = require('highland');
const piper = require('highland-piper');
const stream = _([
  {name: 'John', rating: 1}, 
  {name: 'Tom', rating: 2}, 
  {name: 'Sam', rating: 3} 
]);

const pipeline = piper('experiences');

pipeline
.add('addInfo', _.doto( obj => obj.info = obj.rating > 2 ? 'Experienced' : 'Beginner'))
.abort('ignoreExperienced', obj => /experienced/i.test(obj.info))
.add('assignWork', _.doto( obj => obj.work = 'Do extra work.'));

stream
.through(pipeline.consumer)
.doto(obj => obj.holiday = 'Spain')
.each(o => console.log(o));

Only John & Tom will Do extra work. But they will all John, Tom & Sam holiday in Spain.

finalising

Use .finally to finalise your pipeline. A Transform here applies to all objects including aborted ones. Use it to clean out pipeline specific attributes or properties in your objects.

Also, call .finally once. Any subsequent calls will override the existing transform.

Continuing from the example above.

...
...

pipeline
.add('addInfo', _.doto( obj => obj.info = obj.rating > 2 ? 'Experienced' : 'Beginner'))
.abort('ignoreExperienced', obj => /experienced/i.test(obj.info))
.add('assignWork', _.doto( obj => obj.work = 'Do extra work.'))
.finally(_.doto( obj => delete obj.rating));

stream
.through(pipeline.consumer)
.doto(obj => obj.holiday = 'Spain')
.each(o => console.log(o));

All objects will no longer include obj.rating. After which they will include the holiday property.

Thank yous

Thank you to the highland team for all the hard work!