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

interface-validator

v1.1.1

Published

Validate JSON objects with TypeScript-like interface specifications.

Downloads

214

Readme

Interface Validator

Validate JSON objects with TypeScript-like interface specifications.

Installation

npm install interface-validator

Usage

Specify TypeScript-like interface definition:

const Product = {
  name: 'string!',
  price: 'number!',
  'description?': 'string'
};
import {getMismatchedFields, validate} from 'interface-validator';

const invalidItem = {
  name: '',
  price: '100'
}
const mismatched = getMismatchedFields(invalidItem, Product);
const isValid = valid(invalidItem, Product);
// Result:
// mismatched = ['name']
// isValid = false
// item = {
//   name: undefined,
//   price: 100
// }

Types

Values are checked by this simple statement:

typeof value === specType

Supported types include:

  • string
  • number
  • boolean
  • object
  • nested interface

Nested interface definition is supported. E.g

const Product = {
  name: 'string!',
  price: {
    value: 'number!',
    currency: 'string!'
  },
  'description?': 'string'
}

Type enforcing: You can append ! to the type names to indicate you want to cast the values to the specified types before checking. The tested object's fields will be modified to contain the typecasted values. Refer to the above example to see the effect.

There are some special cases:

  • number!: if the converted value is NaN or Infinity, the value will be set to undefined
  • boolean!: only 'true' and 'false' will be converted to boolean. All other values will be set to undefined.
  • string!: if the value is empty string, it will be set to undefined.

Optional fields are indicated with a question mark after the field name, like 'description?';

When to use this

There are many powerful validation libraries out there. This library is not meant to rival their functionalities. Instead, this is intended to perform very simple run-time interface checks.

In TypeScript you can put compile-time contract on JSON objects using interface but they are stripped away at run-time. So there is no way to perform obj instanceof Interface even when using TypeScript. Not to mention plain Javascript where there is no concept of an interface.

So when you want to do just object instanceof Interface, use this library. Any slightly more complex cases should be handled by more sophisticated libraries.

Contribute

Report issues or submit pull requests.

Tests

npm test