Primitives

string

keywords

🚧 Coming soon ™️🚧

literals

const literals = type({
	singleQuoted: "'typescript'",
	doubleQuoted: '"arktype"'
})

patterns

Regex literals specify an unanchored regular expression that an input string must match.

They can either be string-embedded or refer directly to a RegExp instance.

const literals = type({
	stringEmbedded: "/^a.*z$/",
	regexLiteral: /^a.*z$/
})

lengths

🚧 Coming soon ™️🚧

number

keywords

🚧 Coming soon ™️🚧

literals

const literals = type({
	number: "1337"
})

ranges

🚧 Coming soon ™️🚧

divisors

Constrain a number to a multiple of the specified integer.

string

const evens = type({
	key: "number % 2"
})

fluent

const evens = type({
	key: type.number.divisibleBy(2)
})

bigint

To allow any bigint value, use the "bigint" keyword.

string

const bigints = type({
	foo: "bigint"
})

fluent

const symbols = type({
	foo: type.bigint
})

literals

To require an exact bigint value in your type, you can use add the suffix n to a string-embedded number literal to make it a bigint.

const literals = type({
	bigint: "1337n"
})

You may also use a unit expression to define bigint literals.

symbol

To allow any symbol value, use the "symbol" keyword.

string

const symbols = type({
	key: "symbol"
})

fluent

const symbols = type({
	key: type.symbol
})

To reference a specific symbol in your definition, use a unit expression.

No special syntax is required to define symbolic properties like { [mySymbol]: "string" }. For more information and examples of how to combine symbolic keys with other syntax like optionality, see properties.

boolean

To allow true or false, use the "boolean" keyword.

string

const booleans = type({
	key: "boolean"
})

fluent

const booleans = type({
	key: type.boolean
})

literals

To require a specific boolean value, use the corresponding literal.

string

const booleans = type({
	a: "true",
	b: "false",
	// equivalent to the "boolean" keyword
	c: "true | false"
})

fluent

const booleans = type({
	a: type.keywords.true,
	b: type.keywords.false,
	// equivalent to the "boolean" keyword
	c: type.keywords.true.or(type.keywords.false)
})

null

The "null" keyword can be used to allow the exact value null, generally as part of a union.

string

const nullable = type({
	requiredKey: "number | null"
})

fluent

const nullable = type({
	requiredKey: type.number.or(type.null)
})

undefined

The "undefined" keyword can be used to allow the exact value undefined, generally as part of a union.

string

const myObj = type({
	requiredKey: "number | undefined"
})

fluent

const myObj = type({
	requiredKey: type.number.or(type.undefined)
})

Allowing undefined as a value does not make the key optional!

In TypeScript, a required property that allows undefined must still be present for the type to be satisfied.

The same is true in ArkType.

See an example

const myObj = type({
	key: "number | undefined"
})

// valid data
const validResult = myObj({ key: undefined })

// Error: name must be a number or undefined (was missing)
const errorResult = myObj({})