Valibot to JSON Schema

Utility to convert Valibot schemas to JSON schema (draft 07).

1import { toJsonSchema } from '@valibot/to-json-schema';
2import * as v from 'valibot';
3
4toJsonSchema(v.string()); // { type: "string" }

Some Valibot features can't be mapped to JSON schema. For example, transformation actions have no equivalent in JSON schema. Also, some Valibot schemas or validations are too JS-specific and do not have an equivalent JSON schema attribute.

Supported features

Note: Converted schemas may behave slightly differently in JSON schema validators (especially for string format) because their implementation is different from Valibot's.

Schema	Status	Note
any	✅
array	✅
boolean	✅
enum	✅
intersect	✅
lazy	⚠️	The .getterfunction is always executed with undefined as input
literal	⚠️	Only JSON compatible values are supported
looseObject	✅
looseTuple	✅
null	✅
nullable	✅
nullish	✅
number	✅
objectWithRest	✅
object	✅
optional	✅
picklist	⚠️	Only JSON compatible values are supported
record	⚠️	Only plain string schemas for the key of the record are supported
strictObject	✅
strictTuple	✅
string	✅
tupleWithRest	✅
tuple	✅
union	✅
unknown	✅
variant	⚠️	The discriminator key will be ignored

Actions	Status	Note
description	✅
email	✅
integer	✅
ipv4	✅
ipv6	✅
isoDate	✅
isoTimestamp	✅
length	⚠️	Only in combination with string and array schema
maxLength	⚠️	Only in combination with string and array schema
maxValue	⚠️	Only in combination with number schema
minLength	⚠️	Only in combination with string and array schemas
minValue	⚠️	Only in combination with number schema
multipleOf	✅
regex	⚠️	RexExp flags are not supported in JSON schema
uuid	✅
value	✅

Configurations

Option	Type	Note
errorMode	'throw' | 'warn' | 'ignore'	The policy for handling incompatible schemas and actions.
definitions	Record<string, GenericSchema>	The schema definitions for constructing recursive schemas. If not specified, the definitions are generated automatically.

Error mode

The errorMode configuration controls how the converter handles unsupported schemas and actions. By default, the error mode is set to 'throw'. To force the conversion of unsupported Valibot features, you can set it to 'ignore'.

Unsupported schemas usually return an empty JSON schema ({}) and unsupported actions are usually ignored.

1import { toJsonSchema } from '@valibot/to-json-schema';
2import * as v from 'valibot';
3
4toJsonSchema(v.file(), { errorMode: 'ignore' }); // {}
5
6toJsonSchema(v.pipe(v.string(), v.creditCard()), { errorMode: 'ignore' }); // { type: "string" }

Definitions

Nested schemas can be broken in multiple named definitions.

1import { toJsonSchema } from '@valibot/to-json-schema';
2import * as v from 'valibot';
3
4const EmailSchema = v.pipe(v.string(), v.email());
5toJsonSchema(v.object({ email: EmailSchema }), {
6  definitions: { EmailSchema },
7});
8
9/*
10{
11  $schema: "http://json-schema.org/draft-07/schema#",
12  type: "object",
13  properties: {
14    email: {
15      $ref: "#/$defs/EmailSchema",
16    },
17  },
18  required: ["email"],
19  additionalProperties: false,
20  $defs: {
21    EmailSchema: {
22      type: "string",
23      format: "email",
24    },
25  },
26}
27*/

Definitions are not required for converting lazy schemas. Missing definitions will be generated automatically.

1import { toJsonSchema } from '@valibot/to-json-schema';
2import * as v from 'valibot';
3
4const StringSchema = v.string();
5toJsonSchema(v.object({ key: v.lazy(() => StringSchema) }));
6
7/*
8{
9  $schema: "http://json-schema.org/draft-07/schema#",
10  type: "object",
11  properties: {
12    key: {
13      $ref: "#/$defs/0",
14    },
15  },
16  required: ["key"],
17  additionalProperties: false,
18  $defs: {
19    "0": {
20      type: "string",
21    },
22  },
23}
24*/