runtypes

What is runtypes?

Runtypes is a TypeScript library that provides runtime validation and type checking for JavaScript objects. It allows developers to define types and validate data against those types at runtime, ensuring that the data conforms to the expected structure and types.

What are runtypes's main functionalities?

Basic Type Validation

Runtypes allows you to define basic types like String and Number and validate data against these types. If the data does not match the expected type, an error is thrown.

const { String, Number } = require('runtypes');

const Name = String;
const Age = Number;

Name.check('John Doe'); // Passes
Age.check(30); // Passes

// Name.check(123); // Throws an error
// Age.check('30'); // Throws an error

Object Validation

Runtypes allows you to define complex types like objects and validate data against these types. You can specify the structure of the object and the types of its properties.

const { Record, String, Number } = require('runtypes');

const Person = Record({
  name: String,
  age: Number
});

Person.check({ name: 'John Doe', age: 30 }); // Passes

// Person.check({ name: 'John Doe', age: '30' }); // Throws an error

Union Types

Runtypes supports union types, allowing you to define a type that can be one of several types. This is useful for validating data that can have multiple valid types.

const { Union, String, Number } = require('runtypes');

const StringOrNumber = Union(String, Number);

StringOrNumber.check('Hello'); // Passes
StringOrNumber.check(123); // Passes

// StringOrNumber.check(true); // Throws an error

Array Validation

Runtypes allows you to define array types and validate data against these types. You can specify the type of the elements in the array.

const { Array, String } = require('runtypes');

const StringArray = Array(String);

StringArray.check(['Hello', 'World']); // Passes

// StringArray.check(['Hello', 123]); // Throws an error

Optional Properties

Runtypes allows you to define optional properties in objects. This is useful for validating data where some properties may or may not be present.

const { Record, String, Number, Optional } = require('runtypes');

const Person = Record({
  name: String,
  age: Optional(Number)
});

Person.check({ name: 'John Doe' }); // Passes
Person.check({ name: 'John Doe', age: 30 }); // Passes

// Person.check({ name: 'John Doe', age: '30' }); // Throws an error

Other packages similar to runtypes

io-ts

io-ts is a runtime type system for IO decoding/encoding in TypeScript. It provides similar functionality to runtypes, allowing you to define types and validate data at runtime. However, io-ts has a more functional programming approach and integrates well with fp-ts.

zod

Zod is a TypeScript-first schema declaration and validation library. It provides a similar feature set to runtypes, allowing you to define schemas and validate data at runtime. Zod is known for its simplicity and ease of use.

yup

Yup is a JavaScript schema builder for value parsing and validation. It is similar to runtypes in that it allows you to define schemas and validate data. Yup is widely used in the React ecosystem, especially with form libraries like Formik.

README

Runtypes

Safely bring untyped data into the fold

Runtypes is a JavaScript and TypeScript library which allows you to take values about which you have no assurances and check that they conform to some type A. This is done by means of composable type validators of primitives, literals, arrays, tuples, records and unions. Better yet, it has TypeScript bindings which allow exactly expressing the validated results in a type-safe manner.

Installation

npm install --save runtypes

Example

For example, suppose you have objects which represent asteroids, planets, ships and personnel. In TypeScript, you might model them like so:

type Coordinates = [number, number, number]

interface Asteroid {
  type: 'asteroid'
  coordinates: Coordinates
  mass: number
}

interface Planet {
  type: 'planet'
  coordinates: Coordinates
  mass: number
  population: number
  habitable: boolean
}

type Rank
  = 'captain'
  | 'first mate'
  | 'officer'
  | 'ensign'

interface CrewMember {
  name: string
  age: number
  rank: Rank
  home: Planet
}

interface Ship {
  type: 'ship'
  coordinates: Coordinates
  mass: number
  name: string
  crew: CrewMember[]
}

type SpaceObject = Asteroid | Planet | Ship

If the objects which are supposed to have these shapes are loaded from some external source, perhaps a JSON file, we need to validate that the objects conform to their specifications. We do so by building corresponding Runtypes in a very straightforward manner:

import { boolean, number, string, literal, array, tuple, record, union } from 'runtypes'

const Coordinates = tuple(number, number, number)

const Asteroid = record({
  type: literal('asteroid'),
  coordinates: Coordinates,
  mass: number,
})

const Planet = record({
  type: literal('planet'),
  coordinates: Coordinates,
  mass: number,
  population: number,
  habitable: boolean,
})

const Rank = union(
  literal('captain'),
  literal('first mate'),
  literal('officer'),
  literal('ensign'),
)

const CrewMember = record({
  name: string,
  age: number,
  rank: Rank,
  home: Planet,
})

const Ship = record({
  type: literal('ship'),
  coordinates: Coordinates,
  mass: number,
  name: string,
  crew: array(CrewMember),
})

const SpaceObject = union(Asteroid, Planet, Ship)

Now if we are given a putative SpaceObject we can validate it like so:

// spaceObject: SpaceObject
const spaceObject = SpaceObject.coerce(obj)

If the object doesn't conform to the type specification, coerce will throw an exception.

Type inference

In TypeScript, the inferred type of Asteroid in the above example is

Runtype<{
  type: 'asteroid'
  coordinates: [number, number, number]
  mass: number
}>

That is, it's a Runtype<Asteroid>, and you could annotate it as such. But we don't really have to define the Asteroid interface in TypeScript at all now, because the inferred type is correct. Defining each of your types twice, once at the type level and then again at the value level, is a pain and not very DRY. If you still want a static Asteroid type that you can refer to, you can make it an alias to the Runtype-derived type like so:

type Asteroid = typeof Asteroid.witness

The witness: A field on a Runtype<A> is a lie--a false witness!--it's always undefined. But it's a useful one because applying the typeof operator to it allows us to obtain the derived type A and make a type alias.

Type guards

In addition to coercion, runtypes can be used as type guards:

function disembark(obj: {}) {
    if (SpaceObject.guard(obj)) {
        // obj: SpaceObject
        if (obj.type === 'ship') {
            // obj: Ship
            obj.crew = []
        }
    }
}