NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm, #1490 most downloaded on npm
JSON Schema TypeScript definitions with complete inline documentation.
Latest stable
9.0.0
Last release 1 months ago
15 Oct 2026
Release timing varies
gaps range from 6 weeks to 3.7 years
Some releases are documented
notes for 4 of 8 stable releases
Nothing withdrawn
no release was ever pulled
8 years old
8 releases · first in 2019
Drag across the ruler to compare, or tap a release to open it.
draft 2020-12 includes the deprecated $recursiveAnchor and $recursiveRef keywords that its meta-schema still lists.
$vocabulary is Record<string, boolean> in 2019-09 and 2020-12,Record<string, string>. (#119)prefixItems must be an array of schemas in 2020-12. A bare schema wascontentEncoding is string in 2019-09 and 2020-12 (it remains thebase16,base32, base32hex, base64url) as well as RFC 2045, so the closed unionschema.contentEncoding now sees string instead of the union.JSONSchema<Value> with a union Value constrains type to thoseJSONSchema<string | null> acceptstype: "string", "null", or ["string", "null"]. Previously the generictype for a single-kind Value.dist/deno and the deno.land/xnpm:json-schema-typed). Previously published deno.land/x versions remainJSONSchema itself keeps its 8.x shape — one object type with every keyword,
type accepting any string on the unconstrained type, full documentation on
hover, and JSONSchema.Interface interchangeable with its object half — so
existing schemas and schema-reading code compile unchanged.
Not done, deliberately (#118): checking keywords against type at every
nesting level. It is achievable only by making JSONSchema a union
discriminated on type, and TypeScript then stops showing keyword
documentation on hover wherever the union cannot be resolved to one member
(every schema without a type, and every position when list types are
supported). Inline documentation is the point of this package, so JSONSchema
stays a single object type. JSONSchema.Object, JSONSchema.String, etc.
remain for top-level narrowing.
json-schema-typed/v1: the upcoming JSON Schema v1 specification,main branch. v1 is unreleased;v1/2026)2020-12 untiljson-schema-typed/next: a moving alias for the newest in-progressv1).json-schema-typed/2019-09 and json-schema-typed/2020-12 as the canonicaldraft-2019-09 and draft-2020-12 remain as aliases thatKeywordByType is exported from every module (keyword names grouped by thetype they apply to), along with JSONSchema.KeywordsFor andJSONSchema.Narrowed, the pieces JSONSchema.String, JSONSchema.Object,JSONSchema.Interface takes a third type parameter,Sub, for the type of nested schemas.ContentEncoding.Base16, Base32, Base32Hex, and Base64URL (2019-09$recursiveAnchor and $recursiveRefJSONSchema), and a hover-documentation test against theallOf, anyOf, oneOf, not, if, then,else), contains, and contentSchema no longer inherit the parenttype; a child may declare any type, as the spec allows. On theschema.allOf[0] is a JSONSchema rather than aJSONSchema<Value, SchemaType>.format keyword is permitted on every type, not only strings{ type: "integer", format: "int64" }).JSONSchema.TypeValue is now TypeName | \${TypeName}` |; it no longer includes string(norstring's method types) that leaked in through ValueOf, so a plain stringis no longer aTypeValue. The unconstrained JSONSchemastill accepts any string fortype, via string & {}` so that completions keeptype, contains, minContains, $id,contentEncoding, RFC 3339 format wording, and the applicator annotationsrc/ holds the generator, thenpm run build (Node 22.18+, TypeScript 7). The published declarations aremaxContains and minContains carry minimum: 0; deprecated and$recursiveAnchor carry default: false, matching the meta-schemas.email format documentation and a broken RFC 5321 link.$dynamicRef in v1 is a plain anchor name, not a URI reference, per the v1Your coding agent can read these notes before it upgrades. Set up the MCP server →
Documentation, reference link, and credit updates.
Nothing published for this version
Now distributed for Deno and Node.js, and includes supports for the following 3 JSON Schema drafts:
Now distributed for Deno and Node.js, and includes supports for the following 3 JSON Schema drafts:
draft-07draft-2019-09draft-2020-12JSONSchema changed from an interface to a type: a union that allows
boolean values in order to align with the JSON Schema spec. Code that
extended the JSONSchema interface can extend JSONSchema.Interface.json-schema-typed/draft-07 to keep using Draft 7.Nothing published for this version
Nothing published for this version
Nothing published for this version
Older history is available in the git log.
Older history is available in the git log.
One column per quarter.