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

blooper

v0.0.3

Published

Handle all your errors in one place.

Downloads

3

Readme

Blooper

If you've written Node, you've written this:

doSomething((error, data) => {
	if (error) {
		// handle error
	} else {
		// handle data
	}
});

With Blooper, you write one error handler, and your code looks like this:

doSomething((error, data) => {
	blooper.handle(error).then(() => {
		// handle data
	});
});

This makes it easy to surface errors in the UI, log them and continue, or crash when appropriate.

Usage

There are three things to know:

  • To initialize Blooper, require it and pass it an error handler.
  • The returned object has a handle method which will resolve a promise if the error is falsy, or else handle the error.
  • There is also an attempt method that wraps try-catch (see below).
let response;

const http = require('http'),
	blooper = require('blooper')((error, status = 500) => {
		// Put your error handling logic here
		console.error(error);
		response.writeHead(status, 'text/html; charset=UTF-8');
		response.end(error.stack || error);
	});

http.createServer((req, res) => {

	response = res;

	doSomething((err, data) => {
		blooper.handle(err).then(() => {
			// use data
		});
	});

	// You can wrap try/catch too!
	// By default, Blooper will catch using your error handler
	blooper.attempt(() => {
		doSomethingDangerous();
	});

	// Or you can pass a custom catcher
	blooper.attempt(() => {
		doSomethingDangerous();
	}, err => {
		// handle error here
	});

}).listen(3000);

Using Blooper where you don't have a res object

The above examples only work because Blooper is configured in the same file that accepts requests. In order to use Blooper in other modules in your app, you need to give it access to the res object (assuming your error handler sends responses sometimes). For that, you have two options:

Attach Blooper to the request

Most apps pass around the request object already, so you can stick Blooper on there.

let response;

const http = require('http'),
	blooper = require('blooper')((error, status = 500) => {
		// Put your error handling logic here
		console.error(error);
		response.writeHead(status, 'text/html; charset=UTF-8');
		response.end(error.stack || error);
	}),
	doSomething = require('./doSomething');

http.createServer((req, res) => {

	response = res;

	req.blooper = blooper;

	doSomething(req);

}).listen(3000);

Make Blooper global

Globals are generally a last resort, but I'll let you make an exception for Blooper, since it's really intended to be global in nature - its use is to replace language constructs, after all.

let response;

const http = require('http'),
	blooper = require('blooper')((error, status = 500) => {
		// Put your error handling logic here
		console.error(error);
		response.writeHead(status, 'text/html; charset=UTF-8');
		response.end(error.stack || error);
	});

// This makes the global.handle method available in all modules
global.handle = blooper.handle;

http.createServer((req, res) => {

	// ...

}).listen(3000);