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

express-error-middlewares

v1.0.3

Published

Express JS generic error middlewares for HTTP 404 not found and 500 server internal error

Downloads

17

Readme

express-error-middlewares

Express JS generic error middlewares for HTTP 404 not found and 500 server internal error.
Created to skip always re-writing boilerplate code, and to make it easy to handle errors thrown from async route handlers.

Examples

Adding error middleware to express

const express = require("express");
const app = express();

const { _404, _500 } = require("express-error-middlewares");

app.use("/", require("./routes.js"));

// Mount 404 and 500 error middleware last
app.use(_404);
app.use(_500);

app.listen(3000, () => console.log("Server running on port 3000"));

Wrapping async route handlers to use _500 error handling middleware if anything throws asynchronously

const express = require("express");
const router = express.Router();

const { asyncWrap } = require("express-error-middlewares");

router.get(
  "/some-route",
  asyncWrap(async (req, res) => {
    const err = new Error("Throwing from an async route handler");

    // Set any code you want on the error object, will be 500 if left empty
    err.code = 501;
    
    // Any error thrown, either explicitly or from another function called within this async route handler
    // Will be caught, and passed to the error middleware handler
    throw err;

    res.status(200).json({ ok: true });
  })
);

module.exports = router;

License, Author and Contributing

This project is developed and made available under the "MIT" License
Pull requests are welcomed and open a issue if you have any questions!
If you more questions, contact us via email
Authors: