Package Exports
- ts-json-schema-generator
- ts-json-schema-generator/dist/factory/formatter
- ts-json-schema-generator/dist/factory/formatter.js
- ts-json-schema-generator/dist/factory/generator
- ts-json-schema-generator/dist/factory/generator.js
- ts-json-schema-generator/dist/factory/parser
- ts-json-schema-generator/dist/factory/parser.js
- ts-json-schema-generator/dist/factory/program
- ts-json-schema-generator/dist/factory/program.js
- ts-json-schema-generator/dist/index.js
- ts-json-schema-generator/dist/src/AnnotationsReader/BasicAnnotationsReader
- ts-json-schema-generator/dist/src/AnnotationsReader/BasicAnnotationsReader.js
- ts-json-schema-generator/dist/src/AnnotationsReader/ExtendedAnnotationsReader
- ts-json-schema-generator/dist/src/AnnotationsReader/ExtendedAnnotationsReader.js
- ts-json-schema-generator/dist/src/ChainNodeParser
- ts-json-schema-generator/dist/src/ChainNodeParser.js
- ts-json-schema-generator/dist/src/CircularReferenceNodeParser
- ts-json-schema-generator/dist/src/CircularReferenceNodeParser.js
- ts-json-schema-generator/dist/src/Config
- ts-json-schema-generator/dist/src/Config.js
- ts-json-schema-generator/dist/src/ExposeNodeParser
- ts-json-schema-generator/dist/src/ExposeNodeParser.js
- ts-json-schema-generator/dist/src/NodeParser
- ts-json-schema-generator/dist/src/NodeParser.js
- ts-json-schema-generator/dist/src/NodeParser/AnnotatedNodeParser
- ts-json-schema-generator/dist/src/NodeParser/AnnotatedNodeParser.js
- ts-json-schema-generator/dist/src/NodeParser/AnyTypeNodeParser
- ts-json-schema-generator/dist/src/NodeParser/AnyTypeNodeParser.js
- ts-json-schema-generator/dist/src/NodeParser/ArrayLiteralExpressionNodeParser
- ts-json-schema-generator/dist/src/NodeParser/ArrayLiteralExpressionNodeParser.js
- ts-json-schema-generator/dist/src/NodeParser/ArrayNodeParser
- ts-json-schema-generator/dist/src/NodeParser/ArrayNodeParser.js
- ts-json-schema-generator/dist/src/NodeParser/AsExpressionNodeParser
- ts-json-schema-generator/dist/src/NodeParser/AsExpressionNodeParser.js
- ts-json-schema-generator/dist/src/NodeParser/BooleanLiteralNodeParser
- ts-json-schema-generator/dist/src/NodeParser/BooleanLiteralNodeParser.js
- ts-json-schema-generator/dist/src/NodeParser/BooleanTypeNodeParser
- ts-json-schema-generator/dist/src/NodeParser/BooleanTypeNodeParser.js
- ts-json-schema-generator/dist/src/NodeParser/CallExpressionParser
- ts-json-schema-generator/dist/src/NodeParser/CallExpressionParser.js
- ts-json-schema-generator/dist/src/NodeParser/ConditionalTypeNodeParser
- ts-json-schema-generator/dist/src/NodeParser/ConditionalTypeNodeParser.js
- ts-json-schema-generator/dist/src/NodeParser/EnumNodeParser
- ts-json-schema-generator/dist/src/NodeParser/EnumNodeParser.js
- ts-json-schema-generator/dist/src/NodeParser/ExpressionWithTypeArgumentsNodeParser
- ts-json-schema-generator/dist/src/NodeParser/ExpressionWithTypeArgumentsNodeParser.js
- ts-json-schema-generator/dist/src/NodeParser/FunctionNodeParser
- ts-json-schema-generator/dist/src/NodeParser/FunctionNodeParser.js
- ts-json-schema-generator/dist/src/NodeParser/HiddenTypeNodeParser
- ts-json-schema-generator/dist/src/NodeParser/HiddenTypeNodeParser.js
- ts-json-schema-generator/dist/src/NodeParser/IndexedAccessTypeNodeParser
- ts-json-schema-generator/dist/src/NodeParser/IndexedAccessTypeNodeParser.js
- ts-json-schema-generator/dist/src/NodeParser/InterfaceAndClassNodeParser
- ts-json-schema-generator/dist/src/NodeParser/InterfaceAndClassNodeParser.js
- ts-json-schema-generator/dist/src/NodeParser/IntersectionNodeParser
- ts-json-schema-generator/dist/src/NodeParser/IntersectionNodeParser.js
- ts-json-schema-generator/dist/src/NodeParser/LiteralNodeParser
- ts-json-schema-generator/dist/src/NodeParser/LiteralNodeParser.js
- ts-json-schema-generator/dist/src/NodeParser/MappedTypeNodeParser
- ts-json-schema-generator/dist/src/NodeParser/MappedTypeNodeParser.js
- ts-json-schema-generator/dist/src/NodeParser/NeverTypeNodeParser
- ts-json-schema-generator/dist/src/NodeParser/NeverTypeNodeParser.js
- ts-json-schema-generator/dist/src/NodeParser/NullLiteralNodeParser
- ts-json-schema-generator/dist/src/NodeParser/NullLiteralNodeParser.js
- ts-json-schema-generator/dist/src/NodeParser/NumberLiteralNodeParser
- ts-json-schema-generator/dist/src/NodeParser/NumberLiteralNodeParser.js
- ts-json-schema-generator/dist/src/NodeParser/NumberTypeNodeParser
- ts-json-schema-generator/dist/src/NodeParser/NumberTypeNodeParser.js
- ts-json-schema-generator/dist/src/NodeParser/ObjectLiteralExpressionNodeParser
- ts-json-schema-generator/dist/src/NodeParser/ObjectLiteralExpressionNodeParser.js
- ts-json-schema-generator/dist/src/NodeParser/ObjectTypeNodeParser
- ts-json-schema-generator/dist/src/NodeParser/ObjectTypeNodeParser.js
- ts-json-schema-generator/dist/src/NodeParser/OptionalTypeNodeParser
- ts-json-schema-generator/dist/src/NodeParser/OptionalTypeNodeParser.js
- ts-json-schema-generator/dist/src/NodeParser/ParenthesizedNodeParser
- ts-json-schema-generator/dist/src/NodeParser/ParenthesizedNodeParser.js
- ts-json-schema-generator/dist/src/NodeParser/PrefixUnaryExpressionNodeParser
- ts-json-schema-generator/dist/src/NodeParser/PrefixUnaryExpressionNodeParser.js
- ts-json-schema-generator/dist/src/NodeParser/RestTypeNodeParser
- ts-json-schema-generator/dist/src/NodeParser/RestTypeNodeParser.js
- ts-json-schema-generator/dist/src/NodeParser/StringLiteralNodeParser
- ts-json-schema-generator/dist/src/NodeParser/StringLiteralNodeParser.js
- ts-json-schema-generator/dist/src/NodeParser/StringTypeNodeParser
- ts-json-schema-generator/dist/src/NodeParser/StringTypeNodeParser.js
- ts-json-schema-generator/dist/src/NodeParser/TupleNodeParser
- ts-json-schema-generator/dist/src/NodeParser/TupleNodeParser.js
- ts-json-schema-generator/dist/src/NodeParser/TypeAliasNodeParser
- ts-json-schema-generator/dist/src/NodeParser/TypeAliasNodeParser.js
- ts-json-schema-generator/dist/src/NodeParser/TypeLiteralNodeParser
- ts-json-schema-generator/dist/src/NodeParser/TypeLiteralNodeParser.js
- ts-json-schema-generator/dist/src/NodeParser/TypeOperatorNodeParser
- ts-json-schema-generator/dist/src/NodeParser/TypeOperatorNodeParser.js
- ts-json-schema-generator/dist/src/NodeParser/TypeReferenceNodeParser
- ts-json-schema-generator/dist/src/NodeParser/TypeReferenceNodeParser.js
- ts-json-schema-generator/dist/src/NodeParser/TypeofNodeParser
- ts-json-schema-generator/dist/src/NodeParser/TypeofNodeParser.js
- ts-json-schema-generator/dist/src/NodeParser/UndefinedTypeNodeParser
- ts-json-schema-generator/dist/src/NodeParser/UndefinedTypeNodeParser.js
- ts-json-schema-generator/dist/src/NodeParser/UnionNodeParser
- ts-json-schema-generator/dist/src/NodeParser/UnionNodeParser.js
- ts-json-schema-generator/dist/src/NodeParser/UnknownTypeNodeParser
- ts-json-schema-generator/dist/src/NodeParser/UnknownTypeNodeParser.js
- ts-json-schema-generator/dist/src/NodeParser/VoidTypeNodeParser
- ts-json-schema-generator/dist/src/NodeParser/VoidTypeNodeParser.js
- ts-json-schema-generator/dist/src/TopRefNodeParser
- ts-json-schema-generator/dist/src/TopRefNodeParser.js
- ts-json-schema-generator/dist/src/Type/ArrayType
- ts-json-schema-generator/dist/src/Type/ArrayType.js
- ts-json-schema-generator/dist/src/Type/DefinitionType
- ts-json-schema-generator/dist/src/Type/DefinitionType.js
- ts-json-schema-generator/dist/src/Type/OptionalType
- ts-json-schema-generator/dist/src/Type/OptionalType.js
- ts-json-schema-generator/dist/src/Type/RestType
- ts-json-schema-generator/dist/src/Type/RestType.js
- ts-json-schema-generator/dist/src/Type/TupleType
- ts-json-schema-generator/dist/src/Type/TupleType.js
- ts-json-schema-generator/dist/src/Utils/modifiers
- ts-json-schema-generator/dist/src/Utils/modifiers.js
- ts-json-schema-generator/dist/src/Utils/removeUnreachable
- ts-json-schema-generator/dist/src/Utils/removeUnreachable.js
- ts-json-schema-generator/dist/src/Utils/symbolAtNode
- ts-json-schema-generator/dist/src/Utils/symbolAtNode.js
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (ts-json-schema-generator) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
ts-json-schema-generator
Extended version of https://github.com/xiag-ag/typescript-to-json-schema.
- Inspiration
- CLI Usage
tjsg autocomplete [SHELL]
tjsg generate [PATH]
tjsg help [COMMAND]
- Current state
- Contributors
- Programmatic Usage
- Run locally
- Publish
Inspiration
Inspired by YousefED/typescript-json-schema
. Here's the differences list:
- this implementation avoids the use of
typeChecker.getTypeAtLocation()
(so probably it keeps correct type aliases) - processing AST and formatting JSON schema have been split into two independent steps
- not exported types, interfaces, enums are not exposed in the
definitions
section in the JSON schema
CLI Usage
Run the schema generator with npx:
$ npx ts-json-schema-generator -t 'My.Type.Name' 'my/project/**/*.ts'
Or install the package and then run it
$ npm install -D ts-json-schema-generator
$ node_modules/.bin/tsjg -t 'My.Type.Name' 'my/project/**/*.ts'
Note that different platforms (e.g. Windows) may use different path separators so you may have to adjust the command above.
Also note that you need to quote paths with *
as otherwise the shell will expand the paths and therefore only pass the first path to the generator.
You can also run the CLI with TSJG_DEV=1
to run the CLI in development mode and have more verbose output.
$ TSJG_DEV=1 node_modules/.bin/tsjg -t 'My.Type.Name' 'my/project/**/*.ts'
Options
tjsg autocomplete [SHELL]
Display autocomplete installation instructions.
USAGE
$ tjsg autocomplete [SHELL] [-r]
ARGUMENTS
SHELL (zsh|bash|powershell) Shell type
FLAGS
-r, --refresh-cache Refresh cache (ignores displaying instructions)
DESCRIPTION
Display autocomplete installation instructions.
EXAMPLES
$ tjsg autocomplete
$ tjsg autocomplete bash
$ tjsg autocomplete zsh
$ tjsg autocomplete powershell
$ tjsg autocomplete --refresh-cache
See code: @oclif/plugin-autocomplete
tjsg generate [PATH]
Generate JSON schema from your Typescript sources
USAGE
$ tjsg generate [PATH] [-t <value>] [--top-ref] [-i <value>] [-p <value>] [-e all|none|export] [-j
none|basic|extended] [--markdown-description] [--sort-props] [--strict-tuples] [--type-check] [--ref-encode]
[--additional-properties] [--functions fail|comment|hide] [--minify] [-o <value>] [--extra-tags <value>]
[--discriminator-type json-schema|open-api]
ARGUMENTS
PATH Source file path
FLAGS
-e, --expose=<option> [default: export] Type exposing
<options: all|none|export>
-i, --id=<value> $id for generated schema
-j, --jsdoc=<option> [default: extended] Read JsDoc annotations
<options: none|basic|extended>
-o, --out=<value> Set the output file (default: stdout)
-p, --tsconfig=<value> [default: tsconfig.json] Your tsconfig.json to load entry files and compilation
settings
-t, --type=<value> Type name
--additional-properties Allow additional properties for objects with no index signature
--discriminator-type=<option> [default: json-schema] Type of discriminator to use
<options: json-schema|open-api>
--extra-tags=<value>... [default: ] Provide additional validation keywords to include
--functions=<option> [default: comment] How to handle functions. `fail` will throw an error. `comment`
will add a comment. `hide` will treat the function like a NeverType or HiddenType.
<options: fail|comment|hide>
--markdown-description Generate `markdownDescription` in addition to `description`. Implies
--jsdoc=extended
--minify Minify generated schema
--[no-]ref-encode Encode references
--[no-]sort-props Makes the schema stable by sorting properties
--strict-tuples Do not allow additional items on tuples
--[no-]top-ref Create a top-level $ref definition
--[no-]type-check Type checks to improve performance
DESCRIPTION
Generate JSON schema from your Typescript sources
EXAMPLES
Analyzes src/types.ts using tsconfig.json and pipes to stdout
$ tjsg generate src/types.ts -p tsconfig.json
Analyzes src/types.ts and writes the schema to schema.json
$ tjsg generate src/types.ts -o schema.json
See code: src/commands/generate.ts
tjsg help [COMMAND]
Display help for tjsg.
USAGE
$ tjsg help [COMMAND...] [-n]
ARGUMENTS
COMMAND... Command to show help for.
FLAGS
-n, --nested-commands Include all nested commands in the output.
DESCRIPTION
Display help for tjsg.
See code: @oclif/plugin-help
Current state
interface
typesenum
typesunion
,tuple
,type[]
typesDate
,RegExp
,URL
typesstring
,boolean
,number
types"value"
,123
,true
,false
,null
,undefined
literals- type aliases
- generics
typeof
keyof
- conditional types
- functions
Promise<T>
unwraps toT
export *
to include all exported types
Contributors
This project is made possible by a community of contributors. We welcome contributions of any kind (issues, code, documentation, examples, tests,...). Please read our code of conduct.
Programmatic Usage
You can use the library programmatically as well:
import tsj, { type Config } from "ts-json-schema-generator";
import fs from "node:fs";
const config: Config = {
path: "path/to/source/file",
tsconfig: "path/to/tsconfig.json",
type: "*", // Or <type-name> if you want to generate schema for that one type only
};
const outputPath = "path/to/output/file";
const schema = tsj.createGenerator(config).createSchema(config.type);
const schemaString = JSON.stringify(schema, null, 2);
await fs.promises.writeFile(outputPath, schemaString, { encoding: "utf-8" });
Custom formatting
Extending the built-in formatting is possible by creating a custom formatter and adding it to the main formatter:
- First we create a formatter, in this case for formatting function types (note that there is a built in one):
import { BaseType, Definition, FunctionType, SubTypeFormatter } from "ts-json-schema-generator";
import ts from "typescript";
export class MyFunctionTypeFormatter implements SubTypeFormatter {
// You can skip this line if you don't need childTypeFormatter
public constructor(private childTypeFormatter: TypeFormatter) {}
public supportsType(type: BaseType): boolean {
return type instanceof FunctionType;
}
public getDefinition(type: FunctionType): Definition {
// Return a custom schema for the function property.
return {
type: "object",
properties: {
isFunction: {
type: "boolean",
const: true,
},
},
};
}
// If this type does NOT HAVE children, generally all you need is:
public getChildren(type: FunctionType): BaseType[] {
return [];
}
// However, if children ARE supported, you'll need something similar to
// this (see src/TypeFormatter/{Array,Definition,etc}.ts for some examples):
public getChildren(type: FunctionType): BaseType[] {
return this.childTypeFormatter.getChildren(type.getType());
}
}
- Then we add the formatter as a child to the core formatter using the augmentation callback:
import { createProgram, createParser, SchemaGenerator, createFormatter } from "ts-json-schema-generator";
import { MyFunctionTypeFormatter } from "./my-function-formatter.ts";
import fs from "fs";
const config = {
path: "path/to/source/file",
tsconfig: "path/to/tsconfig.json",
type: "*", // Or <type-name> if you want to generate schema for that one type only
};
// We configure the formatter an add our custom formatter to it.
const formatter = createFormatter(config, (fmt, circularReferenceTypeFormatter) => {
// If your formatter DOES NOT support children, e.g. getChildren() { return [] }:
fmt.addTypeFormatter(new MyFunctionTypeFormatter());
// If your formatter DOES support children, you'll need this reference too:
fmt.addTypeFormatter(new MyFunctionTypeFormatter(circularReferenceTypeFormatter));
});
const program = createProgram(config);
const parser = createParser(program, config);
const generator = new SchemaGenerator(program, parser, formatter, config);
const schema = generator.createSchema(config.type);
const schemaString = JSON.stringify(schema, null, 2);
await fs.promises.writeFile(outputPath, schemaString, { encoding: "utf-8" });
Custom parsing
Similar to custom formatting, extending the built-in parsing works practically the same way:
- First we create a parser, in this case for parsing construct types:
// my-constructor-parser.ts
import { Context, StringType, ReferenceType, BaseType, SubNodeParser } from "ts-json-schema-generator";
// use typescript exported by TJS to avoid version conflict
import ts from "ts-json-schema-generator";
export class MyConstructorParser implements SubNodeParser {
supportsNode(node: ts.Node): boolean {
return node.kind === ts.SyntaxKind.ConstructorType;
}
createType(node: ts.Node, context: Context, reference?: ReferenceType): BaseType | undefined {
return new StringType(); // Treat constructors as strings in this example
}
}
- Then we add the parser as a child to the core parser using the augmentation callback:
import { createProgram, createParser, SchemaGenerator, createFormatter, type Config } from "ts-json-schema-generator";
import { MyConstructorParser } from "./my-constructor-parser.ts";
import fs from "node:fs";
const config: Config = {
path: "path/to/source/file",
tsconfig: "path/to/tsconfig.json",
type: "*", // Or <type-name> if you want to generate schema for that one type only
};
const program = createProgram(config);
// We configure the parser an add our custom parser to it.
const parser = createParser(program, config, (prs) => {
prs.addNodeParser(new MyConstructorParser());
});
const formatter = createFormatter(config);
const generator = new SchemaGenerator(program, parser, formatter, config);
const schema = generator.createSchema(config.type);
const schemaString = JSON.stringify(schema, null, 2);
await fs.promises.writeFile(outputPath, schemaString, { encoding: "utf-8" });
Run locally
You can also run this tool locally:
- Clone the repository
$ git clone https://github.com/vega/ts-json-schema-generator.git
$ cd ts-json-schema-generator
- Install dependencies
$ yarn
- Run the tool
$ yarn --silent run run --path 'test/valid-data/type-mapped-array/*.ts' --type 'MyObject'
Or run with debugging:
$ yarn --silent run debug --path 'test/valid-data/type-mapped-array/*.ts' --type 'MyObject'
And connect via the debugger protocol.
AST Explorer is amazing for developers of this tool!
Publish
Publishing is handled by a 2-branch pre-release process, configured in publish-auto.yml
. All changes should be based off the default next
branch, and are published automatically.
- PRs made into the default branch are auto-deployed to the
next
pre-release tag on NPM. The result can be installed withnpm install ts-json-schema-generator@next
- When merging into
next
, please use thesquash and merge
strategy.
- When merging into
- To release a new stable version, open a PR from
next
intostable
using this compare link.- When merging from
next
intostable
, please use thecreate a merge commit
strategy.
- When merging from