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-mongoose-status

v0.0.3

Published

A simple lib to handle mongoose responses and convert them to correct HTTP status in a REST API using Express

Downloads

5

Readme

express mongoose status

This is a simple lib to handle mongoose responses and convert them to correct HTTP status in a REST API using Express

under continuous improvement....

Problems in common mongoose + express usage

Many code around the web, you can see something like this (when the err has error handler...):

route.get("/some/route/:id", function (req, res, next) {
  MongooseModel.find({"_id": req.params.id }, function (err, data) {
    if (err) {
      return res.status(500).send(err.name); //or next(err), res.sendStatus(500) etc
    }
    res.send(data);
  });
});

Whats the problem with follow approach?

  • Any kind of error will throws status 500 Internal Error
  • If the param.id isn't a ObjectId, it will throw a CastError (instead of 404 not found behavior)
  • Any ValidatorError error will not throws a expected 400 Bad Request
  • Even with valid ObjectId in param.id, successful, but empty responses will throw a 200 OK

Why not just abstract this? Why repeat yourself with a lot of validations? It can be so simple...

var statusHandler = require("express-mongoose-status");
route.get("/some/route/:id", function (req, res, next) {
  MongooseModel.find({"_id": req.params.id }, function (err, data) {
    statusHandler(err, res, data);
  });
});

Installation

npm install express-mongoose-status --save

To be added

  • Doc
  • Samples
  • Tests