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

field-test

v1.2.1

Published

Custom object schema validation

Downloads

6

Readme

field-test

This is a small object schema validation test builder. It does not come with a validation library built in. You simply provide a schema with test functions to test against object properties, and provide error messages if those tests fail.

Ideally, object properties should be strings but they can be anything you choose.

NPM

Quick Example

/* works great for form validation */

const validate = require('field-test')

/* schema */
const schema = {
  username: [{
    test: function (str) { return str.length >=5 && str.length < 20 },
    message: 'username must contain 5 - 20 characters'
  }],
  email: [{
    test: function (str) { return /@/.test(str) },
    message: 'email must contain an @ character'
  },
  {
    test: function (str) { return /\.com/.test(str) },
    message: 'email must contain a .com extension'
  }]
}

validate({ username: 'java', email: '[email protected]' }, schema)

/* returns { username: ['username must contain 5 - 20 characters'] } */

Why?

Most of the validation and object schema validation libraries come with a lot of validation and sanitation methods that you might not need. Some of those libraries also don't have useful error messages (looking at you Joi). This allows you to write as many tests as you like with whatever error messages you want.

Each test also accepts an argument property if you need to pass a configuration object to your test. This is useful if you choose to use this with a validation library,

example

/* import validator library from npm using es6 */

import { isLength, isEmail } from 'validator'
import validate from 'field-test'

/* using same example as above */
const schema = {
  username: [{
    test: isLength,
    argument: { min: 5, max: 20 },
    message: 'username must be between 5 - 20 characters'
  }],
  password: [{
    test: isEmail,
    message: 'email must be valid email format'
  }]
}

validate({ username: 'java', '[email protected]' }, schema)

/* returns { username: ['username must contain 5 - 20 characters'] } */

If all tests pass field-test will just return an empty object