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 🙏

© 2025 – Pkg Stats / Ryan Hefner

super-boom

v0.1.3

Published

A wrapper for Boom that allows to include error code for the frontend

Downloads

15

Readme

About

Super-boom enhance the Hapi.js Boom package by allowing to add parameters in the body of the HTTP answer.

Installation

$ npm install super-boom --save

How to use

In your project file, include the package:

$ Boom = require('super-boom')({ origin: 'server1' }),

where the parameter are the optional default parameters (for now only origin is possible)

Boom.badRequest(httpCode, [message], [customCode], [parameters], [details])

In your code, you can now throw error like this:

$ Boom.customCode(403, 'This property already exist', "CUST_ERR_CODE", ['Some value', 'Blah'], { param1: 'blah', test: 2 }, 'server2');

The body of the HTTP answer should now look like this:

{"statusCode":403,"message":"This property already exist","code":"CUST_ERR_CODE","parameters":["Some value","Blah"], { param1: 'blah', test: 2 }, origin : 'server2' }

Where:

  • httpCode: http code returned by the server
  • message: a meaningful string that explain the problem to your users that only use your API
  • customCode: your application code (which is different from http code) that refer to the exact problem. This code can be plugged in a frontend dictionary.
  • parameters: array of strings to be plugged in the frontend dictionary with the customCode
  • details: an object that can contain anything. Sometimes, you want your API to return additional details that can be used by the frontend.
  • origin: the service or server who emitted the error