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

shenanigans

v1.0.2

Published

A sane way to do errors in a node app

Downloads

4

Readme

shenanigans

A sane way to do errors in a node app.

How you ask?

Well requiring custom errors isn’t too fun so this module takes your error message of shenanigans syntax, parses it, and returns an object with some much friendlier properties.

const Shenanigans = require('./shenanigans')

try {
  throw new Error('403: Not allowed to access resource (Try logging in)')
}
catch (error) {
  const info = Shenanigans.parse(error)
  console.log(info) // => { statusCode: 403, message: 'Not allowed to access resource', hint: 'Try logging in' }
}

And for some real fun if you are using HTTP status codes

const Shenanigans = require('./shenanigans')

try {
  throw new Error(404)
}
catch (error) {
  const info = Shenanigans.parse(error)
  console.log(info) // => { statusCode: 404, message: 'Not Found' }
}

Syntax

${status code}: ${message} (${hint})

Where status code is a number.

API

Shenanigans.parse(message[, options])

Parses the message and returns an info object.

Options are booleans which enable/disable features, they are all true by default and they include:

  • statusCode: Parse the HTTP status code
  • hint: Parse the hint
  • assertion: Enable the assertion error special case