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

node-data-validator

v1.1.3

Published

Validate object data in JS based on a given data model

Downloads

216

Readme

Discord License GitHub code size in bytes GitHub issues Build

Node Data Validator

Validate JavaScript objects based on an given model recursively.

About

This Data Validator was created out of necessity to validate received objects against an given data model on a websocket server, but it can be used to compare any data. You can specify data models with details like min- or max-size and more.

New in 1.1.0

  • Introducing: DetailedValues - specify exactly what you need. Read further to learn more.
  • Now deep searching arrays is possible.

Installation

NodeJS Installation

npm i node-data-validator

or - script tag for the browser

<script src="https://unpkg.com/node-data-validator@latest/Validator.js" type="text/javascript"></script>

Usage

Import

with Common JS

/* Import Validator */
const {Validator} = require("node-data-validator");

or - TypeScript Import

/* Import Validator */
import {Validator} from "node-data-validator";

Using the Module

/*
    IMPORTS
*/
const {Validator} = require("./Validator");

// Create test data
const input = {
    name: 'John',
    age: 23,
    email: "[email protected]",
    address: {
        street: "Main Street",
        city: "New York",
        zip: 24654
    },
    userIDs: [128923891, 238923, 234324, 234234, 23623456]
}

// Create model
const model = {
    name: String,
    age: Number,
    email: String,
    address: {
        street: String,
        city: String,
        zip: Number
    },
    userIDs: [Number],
}

// Output result
console.log(Validator(input, model));

Detailed Values

Working with DetailedValues is exactly as working with primitives. Firstly, import DetailedValues together with the Validator Function. with Common JS

/* Import Validator */
const {Validator, DetailedValue} = require("node-data-validator");

or - TypeScript Import

/* Import Validator */
import {Validator, DetailedValue} from "node-data-validator";

Then specify your model as following:

// Create model
const model = {
    name: new DetailedValue(String, {required: true, min: 4}),
    age: Number,
    email: String,
    address: {
        street: String,
        city: String,
        zip: Number
    },
    userIDs: [Number],
}

You can use the Type declaration in the DetailedValue exactly like the rest of the model, so things like [[Number]] and other shinanigans work fine.

A DetailedValue has the following options: | Option | Type | Description | Values | Default | |----------|---------|------------------------------------|-------------------|---------| | required | boolean | Is the value required? | true or false | true | | min | number | Min length of the value. | Number | null | | max | number | Max length of the value. | Number | null | | isEmail | boolean | Validate if the value is an email. | true or false | false |

Limitations

If you specify an array like userIDs: [Number] only the first data type - in this case Number - will be verified against the data array.