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

rekt

v1.3.6

Published

Easy to use custom errors and handlers.

Downloads

11

Readme

Rekt

This should work on browser as well but hasn't been tested well enough to ensure. I'd love any feedback though!

Usage

/* For a preinstantiated instance */
var rekt = require('rekt').rekt; // Changes to this instance will persist when required elsewhere.

/* For a when you want to initialize a local rekt instance */
var Rekt = require('rekt').Rekt;

/* Changes to one instance will not affect the other. */
var rekt1 = new Rekt();
var rekt2 = new Rekt();

Creating new Errors

var rekt = require('rekt').rekt;

rekt.createError({
    name: 'NewError', // must be included, will throw error if not included.
    status: 400 // defaults to 500
});

throw new rekt.NewError('This is the message that will show up');

Setting and Using handlers

var rekt = require('rekt').rekt;

// Name must a string and must be be an existing error.
// the callback will receive the error object
rekt.setHandler('ErrorName', function(err) {
    console.log(err);
    // etc...
});

/**
 * rekt.handle('ErrorName') takes the name of an error and calls the
 * callback associated with that errorname.
 */

var err = new rekt.ErrorName('This is false');
rekt.assert(false, err, rekt.handle('ErrorName'));

Assert

var rekt = require('rekt').rekt;

// will throw AssertError with provided message.
rekt.assert(false, 'This statement is false'); 

// will call the callback with the error object.
rekt.assert(false, 'This statement is false', function(err) {
    console.log(err);
    // etc...
});

// Will throw the given error.
rekt.createError({ name: 'NewError', status: 500 });
var err = new rekt.NewError('New Error Message');
rekt.assert(false, NewError)

// Will pass the given error to the callback
rekt.createError({ name: 'NewError', status: 500 });
var err = new rekt.NewError('New Error Message');
rekt.assert(false, NewError, function(err) {
    console.log(err.name); // would be 'NewError';
    // etc...
});