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

hapi-boombox

v8.1.0

Published

Boom error wrapper

Downloads

24

Readme

Hapi-Boombox Build Status

Hapi error conversion and logging

What

Boombox logs errors and is able to transform errors. Current version targets hapi 16.

How

Provide Boombox with custom errors (see here for an example) when registering and it will convert errors with messages that match a key in errors and will return a new Boom error.

    const Errors = require('./test/config/errors.json'); //Look here for an example!
    await server.register({
        plugin: require('hapi-boombox'),
        options: { errors: Errors }
    }, callback);

E.g. you return new Error('RESOURCE_NOT_FOUND') and the config states that this should return a Boom.notFound (404). Boombox will do that for you instead of returning an internal server error. Look at the test example to see what the config night look like.

Boombox also provides a server and request method (server.boombox(), request.boombox()) so you can transform your errors on the go. Returns undefined when matching fails.

    const matched = server.boombox(new Error('RESOURCE_NOT_FOUND'));
    /*
    * matched
    *{
    *    message: 'Custom error message for RESOURCE_NOT_FOUND',
    *    type: 'notFound'
    *}
    */

You can disable the logging part by setting disableLog to true.

    const Errors = require('./test/config/errors.json'); //Look here for an example!
    await server.register({
        plugin: require('hapi-boombox'),
        options: { errors: Errors, disableLog: true }
    }, callback);

Logging

Boombox will do a request.log with hapi-boombox and error as tags and the result as data.

  • error the output of the error
  • stack the stacktrace
  • request additional info about the request
    • path, query, method, payload, headers, request.info, credentials
      • credentials: if present this will be an object that includes 2 properties from request.auth.credentials.
        • id.
        • These are properties required by the author for his project. If you want more or something customizable make an issue or PR.

Test

100% test coverage! Also look in the tests for more examples.

Notes

Personally I use this in a hapi server to use generic keys as errors in my code but to give the end user a decent error message and to easily match errors with the right error code. Maybe in the future this can also return localized errors.