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

connect-validation

v0.2.0

Published

A middleware that provides `addError()` and `sendError()` response methods.

Downloads

9

Readme

================== connect-validation

connect-validation is a middleware for connect.js (so you can use it with express applications) that helps handling 400 BAD REQUEST errors on JSON APIs, in a deterministic way.

Specifically, the top-level JSON object in the response will always contain a key named "status", which maps to a string identifying the cause of the error. Unexpected errors will have a status string of “error”; errors expected as part of the protocol flow will have a specific status.

Errors will have three different keys:

  • location is the location of the error. It can be “querystring”, “header” , “url” or “body”;
  • name is the eventual name of the value that caused problem;
  • description is a description of the problem encountered.

For instance, that would be something like::

{
  "status": "errors",
  "errors": [{"location": "body",
              "name": "version",
              "description": "version should be an integer"
             }]
} 

Great, how do I install that?

You have to install the middleware in your express application.

.. code-block:: javascript

var express = require('express');
var validationMiddleware = require('connect-validation');

var app = express();
var app.use(validationMiddleware);

Once installed, addError and sendError methods will be available on all Response objects.

How to use it?

Once installed, you can use these two methods whenever you need to send back errors to the client. You can add as many errors as you want by using the req.addError(location, name, description) method.

At the end of the validation, use sendError() to build the 400 errors response.

.. code-block:: javascript

app.get('/', function (req, res) {
  if (!req.query.hasOwnProperty('id')) {
    res.addError("querystring", "id", "missing; id");
    res.sendError();
    return;
  }
});

If you have only one error, you can use sendError directly.

.. code-block:: javascript

app.get('/', function (req, res) {
  if (!req.query.hasOwnProperty('id')) {
    res.sendError("querystring", "id", "missing; id");
    return;
  }
});

That's all, folks!