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

usable

v0.0.3

Published

simple "reverse-connect.js" contorl flow library

Downloads

2

Readme

simple "reverse-connect.js" contorl flow library

usable

install

npm install usable

installation

var usable = require ('usable') ();

each middleware binds on filter and executes in insertion order

context-safeness

each call of each passed to usable function is context safe, so you can use it with more complicated modules, such as ORM or redis.

but, unfortunalty, this techniqueue limits number of callback arguments up to 7, so be careful.

dependency

only dependensy of usable is sift module, that used for mongodb-like filtering

if you totally sure, that you no need this functionality, feel free to remove sift from node_modules, it will not break other kind of filters.

usage

functional filter

usable (function filter (o) {
	return o.val < 0.5;
}, function middleware (o, next) {
	o.val = Math.round (val);
	next ();
});

usable ({
	o: Math.random()
}, function (err, o) {
	console.log (o.a);
});

object filter

monogdb-like api

usable.use ({
	a: {$exists:true}
}, function (o, next) {
	if (!o.a) {
		next (new Error ("error!"));
	} else {
		next ();
	}
});

usable ({
	a: "value"
}, function (err, o) {
	if (err) {
		console.error (err);
	} else {
		console.log (o.a)
	}
});

string and RegExp filters

if a string is a only one argument to usable instance, then it compiles to regexp and behave like regexp

usable.use ("foo", function (text, next) {
	console.log (text);
	next ();
});

usable ("bar foobaz", function (err, text) {
	console.log (text);
});

more

when you instantiate usable function, you can pass it optional global handlers. each global handler will be called in order of add and runs each time

var usable = require ('usable') (function (next) {
	// some code here
	next ();
}, function (next) {
	// some other code here
	next ();
});

var usable = require ('usable') ([function (next) {
	// some code here
	next ();
}, function (next) {
	// some other code here
	next ();
}])

of course, it's not only one way to use multiple global handlers. just call use with array of functions

usable.use ([function..., function...]);

but, if you add some filter before array of functions, it's ok too:

usable.use (function..., [function..., function...]);