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

slay-error

v1.2.2

Published

Standard, sane defaults for HTTP errors in slay apps.

Downloads

16

Readme

slay-error

Standard, sane defaults for HTTP errors in slay apps.

Usage

You should use this within your middlewares.js in your Slay app

middlewares.js

module.exports = function (app, opts, done) {
  //
  // All your other middlewares first (most of the time)
  //

  //
  // Generally you want your error handling last.
  //
  app.use(require('slay-error')(app, { disableLog: false }));
};

In your application, when you pass an error to the next(error) callback of a request handler, this middleware will handle the reporting and response for that error in your application.

module.exports = function handler(req, res, next) {
  // if error
  next(new Error('let the middleware handle this'));
};

If the error that you pass to this middleware has a location property, res.location(error.location) will be called for you.

If you don't want the error logged, you can use the option disableLog: true or set the log property of the error to false.

You can also control the log level of the error using the level property. So, if level: 'info' only app.log.info will be invoked with the log message and metadata.

Hint

In your application you can use a tool like errs that will allow you to define the structure of errors, either with pre-defined/registered errors or by passing all of the properties of the error to errs.create