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

@bouncingpixel/error-router

v0.7.0-beta

Published

An Express error handler/router than directs errors to the proper error page

Downloads

12

Readme

error-router

An Express handler for handling errors and determining the view to show to the user.

Working With

Requirements

  • NodeJS 6 LTS

Using error-router

The general error handler will either send a message via JSON for AJAX calls or it will render an error page. Errors can have a custom field, status, which defines which HTTP status code to use for that error. If the status is not defined, a 500 status is assumed.

Suggest using Http-Errors to preset status.

Alternatively, when using Error, status may be set along with showView to define the specific template.

When the generic error handler is rendering a page, it may use fallback pages if the specified page does not exist. The order the error handler will try is defined by:

  • The template set in showView if set on the Error object
  • Templates within any subdirectories up to the root views directory for:
    • A template based on the status code
    • A template based on the status code class (ex all 400-499 fall back to 4xx and 500-599 fall back to 5xx)
    • A generic template used to catch all
  • Just rendering the string out

Example code: 503 with showView set to "errors/oops" with the URL "blog/this-is-a-post"

  • errors/oops.dust
  • blog/errors/503.dust
  • blog/errors/5xx.dust
  • blog/errors/error.dust
  • errors/503.dust
  • errors/5xx.dust
  • errors/error.dust
  • No template, just send the string

For non-GET routes, the client will be redirected for non-XHR requests. The clients by default will be redirected back to the previous page. XHR clients will receive the error over JSON and will not be redirected. 401 redirects are special in that they can be redirected to a specific page by setting redirectOn401 in the options when initializing the error-router. The redirect location can also be changed by setting either redirectTo on the error object being thrown or by settings errorRedirectTo on the Express req object for the specific request.