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

merror

v0.1.1

Published

MError: VError with error levels

Downloads

16

Readme

MError

MError: VError with error levels

Build Status

The purpose of this module

VError is a really awesome NPM module. MError inherits from VError and adds some nice APIs that make it a bit nicer to work with (for me anyway, use it or don't).

API

The main API is documented by the VError module, so we will only go into detail on what is added.

MError.setupLevels(levels, defaultLevel)

You call this once to set up error log levels (in order of severity) that MError should be aware of, and to pass the default level that each error will carry until changed.

Example:

MError.setupLevels(['warning', 'error', 'fatal'], 'error');

error.getLevel()

Returns the current level of the error.

Example:

var error = new MError('Ouch');
console.log(error.getLevel()); // outputs: error

error.setLevel(level)

Changes the error level to any of the levels configured through MError.setupLevels.

Example:

var error = new MError('Ouch');
error.setLevel('fatal');

error.incLevel(level)

Changes the level to what is passed, but only if it's an increase in severity.

var error = new MError('Ouch');
error.incLevel('fatal');

error.decLevel(level)

Changes the level to what is passed, but only if it's a decrease in severity.

var error = new MError('Ouch');
error.decLevel('error');

Chaining

The constructor does not require the "new" keyword to function. This fact, combined with function chaining, allows for one-liner patterns like this:

function statMyFile(cb) {
	fs.stat(someFile, function (error, stats) {
		if (error) {
			return cb(MError(error, 'Stat failed').setLevel('fatal'));
		}

		return cb(null, stats);
	});
});