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

errors-handler

v1.0.3

Published

Simple and efficient global errors handler that handle errors of development and production , you don't worry about leaking informations in the production

Downloads

17

Readme

errors-handler

Simple and efficient global errors handler that handle errors of development and production , you don't worry about leaking informations in the production

Installation

npm i errors-handler --save

Before using it :

Make sur you have a .env file contain NODE_ENV=development/production For now i use it for my self , it's very usefull but there is messings errors , so i appreciate your contributions :)

Use

In an Express-based application:

const  app = express();
const errorsHandler = require('errors-handler')
const sendError = require('errors-handler/appError');
//don't work without .env with variable NODE_ENV=production/development
require('dotenv').config(); 


// Setup your middlewares
// Setup your routes
app.get('/foo', async (req, res, next) => {
//Yout code here
// const doc = await Modal.find();
 if(!doc) return next(new sendError('error message here' , status code number here) 
 res.json({
 // your response here
 })
});

// the global error handler middleware 
app.use(errorsHandler);

Errors types

| Error Type | Error in Production | | ------ | ------------ | CastError | Invalid path : value | ValidationError | Duplicate field value : value . please choose anothor value | JsonWebTokenError | Invalid token , please login again | TokenExpiredError | Token expired , please login again |

Options

Soon