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 🙏

© 2026 – Pkg Stats / Ryan Hefner

validimir

v1.5.0

Published

Create validation functions.

Readme

validimir

Minimalistic validation functions with a fluid api, to be used with flexible model layers or as standalone.

build status Dependency Status Coverage Status

Example

var v = require('validimir');

var fn = v().object().hasKey('foo').each(v().string());

fn({ foo: 'bar', beep: 'boop' });
// => { errors: [] }

fn({ foo: 'bar', beep: 2 });
// => { errors: [{
//      value: 2,
//      operator: 'string',
//      actual: 'number',
//      message: 'Expected a string but got a number'
//    }] }

fn({ beep: 2 });
// => { errors: [
//      {
//        value: 2,
//        operator: 'string',
//        actual: 'number',
//        message: 'Expected a string but got a number'
//      },
//      {
//        value: { beep: 2 },
//        operator: 'hasKey',
//        excepted: 'foo',
//        message: 'Expected {"beep":2} to have key foo'
//      }
//    ]}

Installation

With npm do:

npm install validimir

API

Validimir will provide you with a useable .message for errors, or you can pass in your own to each method.

v()

Create a new validation function.

.number([message])

.string([message])

.boolean([message])

.object([message])

.array([message])

.buffer([message])

.date([message])

Assert value is of given type. Types are exact, so .array() won't accept an object and vice versa.

.email([message])

Assert value is a valid email. The regular expression used is:

/^([\w_\.\-\+])+\@([\w\-]+\.)+([\w]{2,10})+$/

.equal(value[, message])

.notEqual(value[, message])

Assert value is (or not) equal to value. ltgt ranges can be used as well.

.match(reg[, message])

.notMatch(reg[, message])

Assert value matches (or doesn't match) regular expression reg.

.hasKey(key[, message])

Assert object value has key key.

.len(length[, message])

Assert value is of length length. ltgt ranges can be used as well.

.of(array[, message])

.notOf(array[, message])

Assert value can (or can't) be found in array.

.each(fn)

Assert each of value - no matter whether it's an array or object - passes fn with should be a function returned by validimir or an api compatible module.

.custom(fn)

Add a custom check fn.

A function is expected to take a value, validate it synchronously and returns either undefined on success or a truthy error value on failure. In theory error values can be of any truthy type, but to be consistent with other checks in validimir it should be an object with the following properties:

  • value: The value that didn't pass the validation
  • operator: The name of the operator that failed
  • message: A descriptive error messsage
  • expected: The expected value, if any

Example:

var v = require('validimir');
var isIP = require('validator').isIP;
var checkIP = function(value) {
  if (!isIP(value)) {
    return {
      value: value,
      operator: 'ip',
      message: 'Expected a valid IP address'
    }
  }
};
var fn = v().custom(checkIP);

fn('not an ip address').errors;
// => [ { value: 'not an ip address',
//        operator: 'ip',
//        message: 'Expected a valid IP address' } ]

fn('127.0.0.1').errors;
// => []

.errors

Array of errors objects found validating value. Accessible on the result of calling the validation function, e.g.

var v = require('validimir');
v().number()(13).errors;

.valid()

Helper function asserting .errors.length === 0. Accessible on the result of calling the validation function, e.g.

var v = require('validimir');
v().string()('13').valid();

License

(MIT)

Copyright (c) 2013 Julian Gruber <[email protected]>

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.