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

nofail

v0.3.0

Published

Failover version builder for `fn(array)`. Promise-based.

Downloads

7

Readme

nofail

Failover version builder for fn(array). Promise-based.

Installation

npm i nofail --save

Usage

var nofail = require('nofail');

// assume it is remote endpoint implementation, which is called using HTTP request
function greet (names) {
	// this is 'validation'
	if (_.contains(names, 'Bob')) {
		throw new Error('Sorry Bob!');
	}
	// this is 'batch processing'
	return names.map(function (name) {
		return 'Hi ' + name;
	});
}

function failureHandler (error, item) {
	console.log(item, 'is causing', error.toString(), 'error');
}

var greetFailover = nofail(greet, failureHandler);

greetFailover(['Melissa', 'Bob', 'Jess', 'Peter']).then(console.log)

// Bob is causing Sorry Bob! error
// ['Hi Melissa', 'Hi Jess', 'Hi Peter']

Also, you can pass any number of additional arguments (after array argument). They will be passed to fn on each call.

greetFailover(['Me', 'You'], 'custom1', 12, { any: 'data' }).then(console.log);

Motivation

Assume you are sending batch of items to certain web service (in a single request) and whole call fails. And the reason is that some of items do not pass remote validation. But you still want to make correct items to be accepted, so you are trying failover solution, which will try to send them, dividing initial batch into smaller ones until everything but erroneous is accepted by remote server.

Mechanism

In case of failure, array is divided into two equisized (if possible) ones, then two function calls are made (each on corresponding subarray). If array is not dividable (length is less than 2), then failure handler is called providing an error and failover process ends. In the end, results are combined into single array to make same output as you would expect from initial function. P. S. Failure handler can be omitted (if you do not want to process failures).

License

MIT