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

validize

v0.1.0

Published

functional validation/sanitization framework

Downloads

4

Readme

vandalize

functional minimal framework to create your own validation/sanitation lib

create a sanitizer

  // create your base sanitizers
  var san = require('vandalize/san')({
    up: () => (value) => value.toUpperCase(),
    cut: (length) => (value) => value.slice(0, length)
  })

  // combine your sanitizers to your specific sanitizer
  var cleanUsername = san.cut(6).up()

  // use it
  var username = cleanUsername('foobarbaz')
  assert(username === 'FOOBAR')

Special handling for objects

  var cleanUser = san.object({
    name: val.up(),
    password: val.cut(3)
  })

  var user = cleanUser({
    name: 'mr. hello',
    password: '1234567'
  })

  assert(user.name === 'MR. HELLO')
  assert(user.password === '123')

create a validator

  // create your base validators
  var san = require('vandalize/val')({
    isString: () => (value) => typeof value === 'string'
    hasLength: (length) => (value) => value.length === length
  })

  // combine your validators to your specific validator
  var isUsername = val.isString().hasLength(5)

  // use it
  assert(isUsername('foobarbaz') === false)
  assert(isUsername(1) === false)
  assert(isUsername('12345') === true)

Special handling for objects

  var isUser = val.object({
    name: val.isString(),
    password: val.hasLength(3)
  })

  var result = isUser({
    name: 'mr. hello',
    password: '1234567'
  })

  // result = { key: 'password', message: 'validation failed' }

Use your own message

You can use your own error message by either providing it on the validator itself or when initilizing your custome validator

  var san = require('vandalize/val')({
    isString: () => (value) => {
      return typeof value === 'string' || 'expected string, got ' + typeof value
    }
  })

  var checker = san.isString()

  assert(checker(123) === 'expected string, got number')
  var san = require('vandalize/val')({
    isString: () => (value) => typeof value === 'string'
  })

  var checker = san.isString('expected string')

  assert(checker(123) === 'expected string')

Exceptions

You can also use exceptions to let a validation fail

  var san = require('vandalize/val')({
    isString: () => (value) => {
      if (typeof value !== 'string') {
        throw new Error('expected string, got ' + typeof value)
      }
      return true
    }
  })

  var checker = san.isString()

  assert(checker(123) === 'expected string, got number')

Exception mode

You can also let the lib throw exceptions one a failing validation.

  var san = require('vandalize/val')({
    isString: () => (value) => typeof value === 'string' || 'expected string, got ' + typeof value
  }, {
    mode: 'exception'
  })

  var checker = san.isString()

  try {
    assert(checker(123)
  } catch(e) {
    assert(e.message === 'expected string, got number')
  }

All-errors-mode

In all other modes, the first error that arises will quit further validation. In all-mode the validation process continues up to the last defined validator.

  // create your base validators
  var san = require('vandalize/val')({
    isString: () => (value) => typeof value === 'string' || 'should be a string, is a ' + typeof value,
    hasLength: (length) => (value) => value.length === length || 'should have length ' + length
  })

  var isUsername = val.isString().hasLength(5)

  // use it
  assert(isUsername('foobarbaz') === ['should have length 5'])
  assert(isUsername(1) === ['should be a string, is a number', 'should have length 5'])
  assert(isUsername('12345') === [])

Exeption and error mode are also supported for objects. See the tests for detailed example.