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

mopup

v1.0.1

Published

Exception handling functions for prototyping

Downloads

3

Readme

mopup

This is a set of functions that you can use in prototyping. It uses the uncaughtException handler mechanism to handle purposely thrown exceptions that include a function for "mopping up".
It's a sort of crude way to allow throwing exceptions from anywhere (including callbacks).

Yes, I know ...

Yes, I know all about the uncaughtException handler being disavowed by Felix, and how you can't guarantee that your program will be in any particular state, and how you should NEVER EVER EVER use it to recover from errors.

So ...

THIS IS NOT FOR PRODUCTION SOFTWARE. ONLY USE IT FOR PROTOTYPING AND PROOF-OF-CONCEPT WORK. DO NOT USE THIS FOR ANYTHING TRULY IMPORTANT.

Okay? Okay. Good.

Now then, here's how it works. You throw an exception from anywhere you want, as long as you include a function that will clean up after yourself. The function is attached to the Error object before it's thrown.

When the exception is caught by the uncaughtException handler (included), it's examined and if said callback is present, it calls that and then just returns without exiting the program.

If there is no handler attached, the program exits.

Functions included

mopup = require("mopup");

mopup.fail(message, cleanup_function);
mopup.fail_if(condition, cleanup_function);
mopup.fail_if(condition, message, cleanup_function);
mopup.die_if(condition)
mopup.die_if(condition, message)

If you want to use my other totally wrong-headed, fool-hearty module called "g", you can simplify things a bit:

require("g")("mopup");

fail(message, cleanup_function);
fail_if(condition, cleanup_function);
fail_if(condition, message, cleanup_function);
die_if(condition)
die_if(condition, message)

Example

require("g")("mopup");

function http_handler(req, res) {

	var mop = function() {
		res.end("fail");
	}

	req.headers.forEach(function(h) {
		fail_if(h == "foo", "DANGER: FOO HEADER DETECTED", mop);
	});

	res.end("okay");

}

Disclaimer

SO THIS IS NOT FOR PRODUCTION SOFTWARE. ONLY USE IT FOR PROTOTYPING AND PROOF-OF-CONCEPTS WORK. DO NOT USE THIS FOR ANYTHING TRULY IMPORTANT.