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

vayder

v1.0.0

Published

A library that allows you to validate inputs on express routes via middlewares. It leverages the power of Joi with an easy, fluent interface for the middlewares to make it effortless to build a robust validation layer on your express server.

Downloads

4

Readme

VAYDER

A library that allows you to validate inputs on express routes via middlewares. It leverages the power of Joi and Celebrate with an easy, fluent interface for the middlewares to make it effortless to build a robust validation layer on your express server.

API:

| method | description | input | | ------ | ----------- | ----- | | validateBody | will validate the body of the request against the provided Joi Schema | Joi Schema | | validateParams | will validate the URL parameters passed into the request against the provided Joi Schema | Joi Schema | | validateQuery | will validate the request query string against the provided Joi Schema | Joi Schema | | validateHeaders | will validate the request Headers against the provided Joi Schema | Joi schema |

How to Use

1) Create a JOI schema

// schema.js

const Joi = require('joi');

module.exports = Joi.object().keys({
  foo: Joi.string().required(),
  bar: Joi.number().min(10).max(20),
});

2) Add it to your Express route

// app.js

const express = require('express');
const vayder = require('vayder');

const blahSchema = require('./schema.js');
const app = express();


app.post('/blah',
  vayder.validateBody(blahSchema),
  (req, res) => { res.send('Hello World!');}
);

app.listen(3000, () => {
  console.log('Example app listening on port 3000!');
});

Handling Errors

As per Joi docs, any validation failure that is caught by Joi will be thown as an error with the .isJoi property attached to it. It is recommended to have an error handling middleware at the bottom of your app.js to handle this:

app.use('*', (err, req, res, next) => {
    if(err.isJoi) {
      // do stuff
    }

    return next(err);
});

Advanced

Multiple Validations

You can do multiple validations in a very clear and concise syntax:

app.get('/',
  vayder.validateHeaders(AuthenticationSchema),
  vayder.validateQuery(paginationSchema),
  vayder.validateParams(userIdSchema),
  someController.doStuff);

Organizing Schemas

A useful way to organize / manage the schema imports is by creating a directory tree called models/validations in your project.

webapp
├── app.js
├── controllers
├── datasource
├── middlewares
├── models
│   └── validations
│       ├── accessToken.js
│       ├── accountSignUp.js
│       ├── index.js
│       ├── credentials.js
│       └── pagination.js
│
├── routes.js
├── serializers
├── services
└── utilities

Then, in the models/validations/index.js file, you can manage a single entry point to all the validations:

// index.js

module.exports = {
  accessToken: require('./accessToken'),
  accountSignUp: require('./accountSignUp'),
  credentials: require('./credentials'),
  pagination: require('./pagination'),
}

This makes for a cleaner interface when validating routes:

// routes.js
const vayder = require('vayder');
const schemas = require('./models/validations');

app.get('/',
  vayder.validateHeaders(schemas.accessToken),
  vayder.validateQuery(schemas.pagination),
  someController.doStuff
);