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-common-middlewares

v1.0.24

Published

Common express middlewares

Downloads

7

Readme

There are 4 middleware:

  • requireLogin: check if user is login
  • requireRole: check if user is admin
  • checkIdExistene: check if an objectid exists in a mongodb collection
  • checkOwnership: check if a document is created by currently logged in user
  • globalErrorHandler: express global error handler
  • routeNotFound: simple prewritten function to handle route not found error

requireLogin

In order to make this middleware work:

  • you need to pass in User model created from express.Model as an arguement
  • defined process.env.JWT_SECRET
  • apply cookie-parse into express app
const { requireLogin } = require('express-common-middlewares');

router.use('/require-login', requireLogin(User), (req, res, next) => {
  res.status(200).json({ status: 'success', message: 'pass the test' });
});

requireRole

Require role simple check if req.user.role has a specific role.

// in this example, it check if user has role of admin
const { requireLogin, requireRole } = require('express-common-middlewares');

router.use(
  '/require-role',
  requireLogin(User),
  requireRole('admin'),
  (req, res, next) => {
    res.status(200).json({ status: 'success', message: 'pass the test' });
  },
);

It can also check if user has one of multiple roles

// in this example, it check if user has roles of admin, write or support
router.use(
  '/require-role',
  requireLogin(User),
  // it will pass if user is one of these 3 roles
  requireRole('admin', 'writer', 'support'),
  (req, res, next) => {
    res.status(200).json({ status: 'success', message: 'pass the test' });
  },
);

checkIdExistence

Check if all the object ids inside req.body.friends do exist.

req.body.friends can be a single objectid or array of objectids.

router.use(
  '/check-id-existence',
  checkIdExistence(User, 'friends'), // check if all ids in friends exist in db
  (req, res, next) => {
    res.status(200).json({ status: 'success', message: 'pass the test' });
  },
);

It will throw error if req.body.friends contains an user id that does not exist. You can check whatever field in whatever mongodb collection you want, not just req.body.friends fields in user collection.

requireOwnership

This middleware accept mongoose model as an argument. It will check if the document with id = req.params.id createdBy current login user.

// in this example, it check if user has role of admin
router.use(
  '/:id',
  requireLogin(User),
  requireOwnership(Product), // check if user has ownership to product with id = req.params.id
  (req, res, next) => {
    res.status(200).json({ status: 'success', message: 'pass the test' });
  },
);

Behaviour:

  • return success if user have ownership to that doc
  • return success if user is admin
  • return error if user does not have ownership
  • return error if document with id params does not exist
  • return error if document does not contain createdBy field

Important note:

  • the document that you checked ownership for need to have createdBy field contain creator userid
  • you need to use requireLogin middleware before using requireOwnership because + requireOwnership need to use req.user
  • The route you apply requireOwnership middleware must have req.params.id

Global error handler

This middleware only handle jwt verify failure. Otherwise, it just return generic message: Something wentwrong!

const app = express();

app.use(globalErrorHandler);

Route not found

This is everything this middleware do!

res.status(404).json({
  status: 'fail',
  message: 'This route is not defined',
});
const app = express();

app.use(routeNotFound);