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

mycro-error

v0.2.2

Published

error handling service for mycro apps

Downloads

1

Readme

mycro-error

a mycro hook that provides an error service with utility error handling methods.

Install

install

npm install --save mycro-error

add to hooks

// in config/hooks.js
module.exports = {
    // ..
    'services',
    'mycro-error',
    // ..
}

Getting Started

Add a custom notifier. By default, the only notifier enabled is a logger notifier

// hooks/bugsnag.js
var bugsnag = require('bugsnag');

module.exports = function(done) {
    let mycro = this;
    bugsnag.register(/* stuff */);
    mycro.services.error.addNotifier(bugsnag.notify);
    done();
}

Handle an error

let errorService = mycro.services.error;
// ..
if (err) {
    errorService.notify(err);
}

Intercept an error

// default functionality
somethingAsync(errorService.intercept(function(err, val) {
    // if an error occurred, all notifiers will be called with the
    // error, and the error will be available for additional handling here
}));

// prevent the callback from executing
somethingAsync(errorService.intercept(true, function(val) {
    // if an error occurred, all notifiers will be called with the
    // error, and this callback will never be called.
}));

Add a custom error response handler

errorService.responseHandler = function(res, error) {
    // inspect the error or serialize it
    res.json(500, {errors: [error]});
}

Intercept a response handler

async.waterfall([
    function findData(fn) {
        // ..
    },

    function processData(data, fn) {
        // ..
    }
], errorService.interceptResponse(res, function(data) {
    res.json(200, {data: data});
}));

Define your applications errors in a config file

// in config/errors.js
module.exports = {
    badRequest: {
        status: 400,
        title: 'Bad Request'
    },
    query: {
        status: 500,
        title: 'Database Query Error'
    }
}

Convert errors into defined errors

Posts.find({ published: true }, function(err, posts) {
    if (err) {
        err = errorService.get('query', err.message);
        console.log(err); // { status: 500, title: 'Database Query Error', detail: 'ECONNECT'}
    }
});

Or, better yet, wrap your callbacks

joi.validate(req.body, schema, errorService.wrap('badRequest', function(err, data) {
    if (err) {
        console.log(err); // { status: 400, title: 'Bad Request', detail: 'Child \'attr\' fails because \'attr\' is required'}
    }
}));

And, you can even call your notifiers with the raw error first

Posts.find({ published: true }, errorService.wrap(true, 'query', function(err, posts) {
    if (err) {
        console.log(err); // { status: 500, title: 'Database Query Error', detail: 'ECONNECT'}
    }
}));

Testing

run the test suite

npm test

Contributing

  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request

License

Copyright (c) 2016 Chris Ludden. Licensed under the MIT License