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

@wonderlandlabs/validators

v1.0.2

Published

A microscopic validation suite for types

Downloads

4

Readme

This is an attempt to make a shareable library to validate fundamental types with as little code as possible.

the module is a function that returns a function that returns a test, by name. The nature of the tests is that if the candidate passes the test false is returned; if not, a string is returned describing the error.

This means, "false is good, string is fail".

import validators from '@wonderlandlabs/validators';
const val = validators();
const isString = val('string');

console.log(isString('foo')); 
// false

console.log(isString(1));
// 'must be string';

Current tests include:

  • string
  • number
  • integer
  • array
  • object
  • map (Map class)
  • set (Set class)
  • boolean (true or false)
  • date (Date class)
  • function
  • null
  • undefined
  • true (truthy)
  • false (falsy)

is

If you want true to be returned when an item is valid, call "is". Is returns true for good data, false for bad; therefore, never returns string.

import validators from '@wonderlandlabs/validators';
const val = validators();
const isString = val.is('string');

console.log(isString('foo')); 
// true

console.log(isString(1));
// false

Expanding validators

validators uses a closured set of tests; you can expand the tests by passing a function into validators:

import validators from '@wonderlandlabs/validators';
const val = validators();
const digits = [0,1,2,3,4,5,6,7,8,9];
function isDigit(value) {
  return digits.includes(value) ? false : 'must be 0-9'
}

val('digit', isDigit);

console.log(val('digit')(2)); 
// false
console.log(val('digit')(20)); 
// 'must be 0-9'

Your custom tests are only available from the instance function you use to define the test. This is intentional, to prevent singleton issues.