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

swint-pipe

v1.0.12

Published

Pipeline logic flow for Swint

Downloads

220

Readme

swint-pipe

Greenkeeper badge Pipeline logic flow for Swint

Warning: This is not the final draft yet, so do not use this until its official version is launched

Installation

$ npm install --save swint-pipe

Edge

  • Atomic task(can be synchronous or asynchronous) defined by function.
  • Usage
var edge1 = Pipe.Edge(function(system, input, output) {
		db.fetch({
			// ...
		}, function(err, res) {
			output(/* ... */);
		});
	}); // asynchronous task

var edge2 = Pipe.Edge(function(system, input) {
		return input * 2;
	}); // synchronous task

edge1.input(1); // When edge is the input of whole system, the data flows to the `input` of the main function.
edge2.output(system, 'edge2'); // When edge is the output of whole system, the data flows to `system.out()`.

System

  • Defines the data flow using connect() and branch().
  • Handles the error using error().
  • Usage
var system = Pipe.System({
		foo: 'bar' // Global variable throughout the system
	});

system.connect(edge1, edge2); // `edge2` will wait for `edge1` to be finished
system.connect(edge2, [edge3, edge4]); // `edge3` and `edge4` will be fired right after `edge2` is finished
system.connect([edge3, edge4], edge5); // `edge5` will wait for both `edge3` and `edge4` to be finished
system.connect(edge5, edge6, function(before, after) {
	after(before * 2);
}); // can morph the pipelined data on connection
system.branch(edge6, [edge7, edge8, edge9], function(before, after) {
	switch(before.type) {
		case 'A':
			after(0, 'type A'); // `'type A'` will be passed to `edge7`(`0`th edge on the array), while `edge8` and `edge9` outputs `undefined`.
			break;
		case 'B':
			after(1, 'type B');
			break;
		case 'C':
			after(2, 'type C');
			break;
	}
}); // can branch between edges

system.end(function(output) {
	// ...
}); // executed when the whole system is ended

var edge1 = Pipe.Edge(function(system, input, output) {
		db.fetch({
			// ...
		}, function(err, res) {
			if(err) {
				system.throw('MyError', 'something happened'); // throws error to the system
				return;
			}
			// ...
		});
	});
system.error(function(type, err) {
	// handling the thrown error
});

system.start(); // actually starts the system