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

@jagota-brothers/common

v0.1.1

Published

Error handling shared common library

Downloads

93

Readme

Node Micro-Services Common Code

For ease of code sharing between different projects


Install

$ npm i @jagota-brothers/common

Usage Example:

// Other imports
import { notFoundError, currentUser } from '@jagota-brothers/common';

const app = express();

app.get('/', currentUser, (req, res) => {
    // if user is logged in, this would be defined
    const userInfo = req.user;
    // Rest of stuffs
});

// Other routes

// route for 404
app.all('*', async () => {
    throw new NotFoundError();
})

Custom Errors available

authorizationError : 401, Can use for unauthorized request.

badRequestError : 400, expects a string as parameter.

databaseError : 500, Failed to connect to DB.

notFoundError : 404, Not Found.

requestValidationError : 400, For failed validation (express-validator) requests.

Custom Middlewares

currentUser :

  • Checks cookie in request to see if user JWT is sent along with request.
  • Attaches data in JWT to request as req.user.

authorize : fn

  • Should only be used after currentUser middleware.
  • Takes an optional array of roles (string) as parameter.
  • Checks if that role is present in req.user.

errorHandler :

  • Global catch block.
  • Use as last middleware for the App.

validateRequest : fn

  • Accepts validation Schema (from express-validator) as parameter
  • Validates incoming data in request against schema & throws error if data is invalid

The middlewares marked as fn should be used as a function.

Example:

const validRolesToCreateArticle = ['author', 'admin'];

app.post('/article', currentUser, authorize(validRolesToCreateArticle), (req, res) => {
    // Implementation for this route    
})

License

This package is created & published under MIT License.