@amritk/mjst 0.22.0 → 0.23.0

package/AI.md

@@ -8,7 +8,7 @@ reference is [README.md](./README.md); config options are in
 
 > Pre-alpha: generated output and flags change without notice pre-1.0. This
 > package ships **only a `mjst` binary** — there are no JS exports. For the
-> programmatic API import `@amritk/parsers` etc. instead.
+> programmatic API import `@amritk/validation` etc. instead.
 
 ## The four commands
 
@@ -57,11 +57,19 @@ mjst markdown ./config.schema.json --table --readme ./README.md
    `--discriminator <prop>` when the document tags frames with something other
    than `type`; a channel carrying `x-mjst: { discriminator }` keeps its own.
 
+## Picking what gets emitted
+
+Every run emits the type. `--types-only` stops there. A bare run adds a parser;
+`--validators` adds `isX`/`validateX` beside it; `--validators-only` emits those
+*without* a parser, which is the shape to reach for when the generated code only
+ever judges input it did not produce. `--check`, `--coerce` and `--repair` each
+add one more entry point to the validator half and work under either flag.
+
 ## Common flags
 
 `--schema` / `--schema-dir`, `--out-dir` / `--out-file`, `--input`,
-`--validators`, `--examples`, `--message-contracts`, `--discriminator`,
-`--types-only`, `--build`, `--strict`, `--strip-unknown`,
+`--validators` / `--validators-only`, `--examples`, `--message-contracts`,
+`--discriminator`, `--types-only`, `--build`, `--strict`, `--strip-unknown`,
 `--unknown-keys count-keys|count-enumerable`, `--readonly`,
 `--import-ext ts|js`, `--config <path>`, `--resolve-remote` /
 `--allowed-hosts` (SSRF-guarded remote `$ref`s).

package/README.md

@@ -321,6 +321,10 @@ npx mjst markdown ./config.schema.json --table --readme ./README.md
 | `--layout` | Default layout for nested properties: `headings` (default), `table`, or `none`. |
 | `--sort` | Property order: `schema` (default) or `alphabetical`. |
 | `--heading-level` | Heading level of the page title, 1-6 (default: `1`). |
+| `--type-column` | When a property table renders its **Type** column: `auto` (default — only when a row fills it with something a reader could act on), `always`, or `never`. |
+| `--default-column` | When a property table renders its **Default** column: `auto` (default), `always`, or `never`. |
+| `--required-style` | How a property table says which properties are required: `marker` (default — `_required_` beside the name) or `column` (a **Required** column). |
+| `--required-first` | List the required properties at the top of every table, the rest under them. |
 | `--table` | Render the HTML config table instead of the prose pages. |
 | `--readme` | Markdown file the table is spliced into (default: `README.md`). Requires `--table`. |
 
@@ -408,6 +412,15 @@ Under `--table` only the content between `<!-- config-table-start -->
 <td colspan="4">Also emit validation functions alongside the parsers. For every generated type X the CLI writes a validateX (returning a rich ValidationResult with JSON-Pointer error paths) and an isX boolean type guard. They share one directory and one declaration of X with the parser: the type and the validators land in x.ts, and the parser moves to x.parse.ts beside them, importing the type from there. Works with both schema and schemaDir. Incompatible with typesOnly and outFile, which produce no runtime code.</td>
 </tr>
 <tr>
+<td>🛡️ <code>validatorsOnly</code></td>
+<td><code>--validators-only</code></td>
+<td><code>boolean</code></td>
+<td align="center"><code>false</code></td>
+</tr>
+<tr>
+<td colspan="4">Emit the validator half and no parser: the type, isX, validateX, and whichever of checkX, coerceX and repairX were asked for. Implies validators, so it does not need it as well. This is the mirror of typesOnly at the other end of the ladder — one run with nothing that rewrites a document, the other with nothing that executes at all — and it is what to reach for when the generated code only ever judges input it did not produce. Without it every run carries a parser. Incompatible with typesOnly and outFile.</td>
+</tr>
+<tr>
 <td>🔎 <code>check</code></td>
 <td><code>--check</code></td>
 <td><code>boolean</code></td>

package/dist/cli-config.d.ts

@@ -41,6 +41,17 @@ export type CliConfig = {
      * Useful when you only need the type shapes and do not need runtime validation.
      */
     readonly typesOnly?: boolean;
+    /**
+     * When true, emit the validator half and no parser: the type, `isX`,
+     * `validateX`, and whichever of `checkX`/`coerceX`/`repairX` were asked for.
+     *
+     * Implies `validators`, and is the mirror of `typesOnly` at the other end of
+     * the ladder — one run with nothing that rewrites a document, the other with
+     * nothing that executes at all. Without it every run carries a parser, so the
+     * library's own default (a type and its validators, nothing that builds a
+     * value) had no spelling here.
+     */
+    readonly validatorsOnly?: boolean;
     /**
      * When true, also emit validation functions alongside the parsers. For every
      * generated type `X` the CLI writes a `validateX` (returning a rich

package/dist/cli.js

@@ -377,19 +377,20 @@ const run = async () => {
   const fileConfig = configPath ? await loadConfig(configPath) : {};
   const cliConfig = parseCliArgs(args);
   const config = { ...fileConfig, ...cliConfig };
-  if (config.coerce && !config.validators) {
+  const wantsValidators = config.validators === true || config.validatorsOnly === true;
+  if (config.coerce && !wantsValidators) {
     console.error("Error: --coerce shapes the generated validators, so it needs --validators too.");
     process.exit(1);
   }
-  if (config.repair && !config.validators) {
+  if (config.repair && !wantsValidators) {
     console.error("Error: --repair shapes the generated validators, so it needs --validators too.");
     process.exit(1);
   }
-  if (config.check && !config.validators) {
+  if (config.check && !wantsValidators) {
     console.error("Error: --check shapes the generated validators, so it needs --validators too.");
     process.exit(1);
   }
-  if (config.branchErrors && !config.validators) {
+  if (config.branchErrors && !wantsValidators) {
     console.error("Error: --branch-errors shapes the generated validators, so it needs --validators too.");
     process.exit(1);
   }
@@ -413,10 +414,18 @@ const run = async () => {
     console.error("Error: --validators cannot be combined with --types-only, which emits no runtime code.");
     process.exit(1);
   }
+  if (config.validatorsOnly && config.typesOnly) {
+    console.error("Error: --validators-only cannot be combined with --types-only. Pick the one end you want: types alone, or types and validators.");
+    process.exit(1);
+  }
   if (config.validators && config.outFile) {
     console.error("Error: --validators cannot be combined with --out-file. Use --out-dir to emit validator files.");
     process.exit(1);
   }
+  if (config.validatorsOnly && config.outFile) {
+    console.error("Error: --validators-only cannot be combined with --out-file. Use --out-dir to emit validator files.");
+    process.exit(1);
+  }
   if (config.input === "asyncapi") {
     if (config.schemaDir) {
       console.error("Error: --input asyncapi reads a single document via --schema; it cannot be combined with --schema-dir.");

package/dist/combine-files.d.ts

@@ -1,4 +1,4 @@
-import type { GeneratedFile } from '@amritk/parsers';
+import type { GeneratedFile } from '@amritk/validation';
 /**
  * Merges the per-schema {@link GeneratedFile}s into a single self-contained
  * TypeScript module. Each generated file imports its sibling definitions via

package/dist/generate-files.d.ts

@@ -1,4 +1,4 @@
-import { type GeneratedFile } from '@amritk/parsers';
+import { type GeneratedFile } from '@amritk/validation';
 import type { JSONSchema } from 'json-schema-typed/draft-2020-12';
 import type { CliConfig } from './cli-config.js';
 /** Where one schema's generated files reach their runtime helpers from. */
@@ -14,7 +14,7 @@ export type HelpersPlacement = {
 };
 /**
  * Generates one schema's files, translating the CLI's flags into the single
- * options object `@amritk/parsers` takes.
+ * options object `@amritk/validation` takes.
  *
  * All four generation flows come through here so none of them can quietly hold a
  * different opinion about what a flag means — which is exactly what happened

package/dist/generate-files.js

@@ -1,4 +1,4 @@
-import { generate } from "@amritk/parsers";
+import { generate } from "@amritk/validation";
 import { resolveImportExt } from "./resolve-import-ext.js";
 import { resolveModes } from "./resolve-modes.js";
 const generateFiles = async (config, schema, rootTypeName, helpers) => generate(schema, rootTypeName, {

package/dist/help-text.d.ts

@@ -4,4 +4,4 @@
  * documents these flags (config.schema.json) is not shipped in the published
  * package; the help-text test cross-checks that every flag is listed.
  */
-export declare const HELP_TEXT = "mjst \u2014 generate TypeScript parsers and type definitions from JSON Schemas\n\nUsage:\n  mjst --schema <path> --out-dir <dir> [options]\n  mjst --schema-dir <dir> --out-dir <dir> [options]\n  mjst --schema <path> --out-file <file> --types-only [options]\n\nSubcommands (each with its own flags and --help):\n  mjst lint <files>                       Lint JSON/YAML documents against a ruleset\n  mjst compile-api <module> --out <file>  Compile @amritk/api route contracts into a fetch-handler module\n  mjst markdown <schema> --out-dir <dir>  Generate markdown documentation from a JSON Schema\n\nInput:\n  --schema <path>       Schema to process: a JSON Schema file, or a module when --input is set\n  --schema-dir <dir>    Directory of JSON Schemas, processed recursively (instead of --schema)\n  --input <format>      Schema source format: json (default), typebox, zod, valibot, effect, avro,\n                        or asyncapi (an AsyncAPI 2.x/3.0 document, JSON or YAML)\n  --export <name>       Which export of the schema module to use when --input names a module format\n\nOutput:\n  --out-dir <dir>       Output directory for the generated files\n  --out-file <file>     Single-file output instead of a directory (requires --types-only)\n  --types-only          Generate type definitions only, without parser functions\n  --validators          Also emit validateX/isX validators beside the parsers, over one\n                        shared declaration of each generated type\n  --check               Also emit checkX, the same result as validateX but stopped at the\n                        first violation (requires --validators)\n  --coerce              Also emit coerceX, which coerces scalars the way Ajv's coerceTypes\n                        does and then validates (requires --validators)\n  --repair              Also emit repairX, which coerces, validates, then repairs each\n                        rejected position to a schema-supplied value and reports the\n                        errors it repaired (implies --coerce; requires --validators)\n  --branch-errors       Explain a failing anyOf/oneOf with the errors of the branch it\n                        meant (requires --validators; costs a little on unions)\n  --examples            Also emit fast-check arbitraries + example values under examples/\n  --message-contracts   Also emit @amritk/api channel contracts under contracts/ (--input asyncapi only)\n  --discriminator <p>   Property naming which message a frame is, for --message-contracts (default: type)\n  --build               Compile the generated files to .js/.d.ts (implies --import-ext js)\n  --force               Deprecated; ignored (generated files always overwrite)\n  --import-ext <ext>    Extension on generated relative imports: ts (default) or js\n  --helpers <mode>      Runtime helpers: package or embedded (default: auto-detect from package.json)\n  --root-type <name>    Root type name for a single --schema run (default: schema title or filename)\n  --type-suffix <s>     Suffix appended to every $ref-derived type name\n  --banner [text]       Prepend a header comment to every generated file\n  --readonly            Emit deeply readonly type definitions\n\nValidation:\n  --strict              Throw on type/shape mismatches instead of coercing to defaults\n  --strip-unknown       Silently drop undeclared input keys at every nesting level\n  --case-insensitive    Normalize mis-cased enum/const strings to their exact casing\n  --log-warnings        console.warn on input keys not declared in the schema\n  --unknown-keys <s>    How closed objects are proven free of undeclared keys:\n                        count-keys (default, fastest on Bun) or count-enumerable (fastest on Node)\n  --formats <f>         String formats the generated validators enforce: \"all\", or a\n                        comma-separated list (e.g. uuid,date-time,email). Off by default,\n                        which leaves \"format\" an annotation as JSON Schema reads it.\n\nReference resolution:\n  --resolve-remote      Fetch http(s) $refs while resolving cross-file/remote refs (off by default)\n  --allowed-hosts <h>   Restrict remote $ref fetches to these hosts (comma-separated; implies --resolve-remote)\n  --allow-private-hosts Permit remote $refs to private/loopback hosts (SSRF guard, off by default)\n  --allowed-roots <d>   Extra directories a local $ref may resolve into, on top of the schema's own\n                        (comma-separated; relative to the current directory)\n\nMisc:\n  --config <path>       JSON config file with the same keys; CLI flags take precedence\n  --version, -v         Print the CLI version\n  --help, -h            Print this help\n\nDocs: https://github.com/amritk/mjst/tree/main/packages/cli#readme\n";
+export declare const HELP_TEXT = "mjst \u2014 generate TypeScript types, validators and parsers from JSON Schemas\n\nUsage:\n  mjst --schema <path> --out-dir <dir> [options]\n  mjst --schema-dir <dir> --out-dir <dir> [options]\n  mjst --schema <path> --out-file <file> --types-only [options]\n\nSubcommands (each with its own flags and --help):\n  mjst lint <files>                       Lint JSON/YAML documents against a ruleset\n  mjst compile-api <module> --out <file>  Compile @amritk/api route contracts into a fetch-handler module\n  mjst markdown <schema> --out-dir <dir>  Generate markdown documentation from a JSON Schema\n\nInput:\n  --schema <path>       Schema to process: a JSON Schema file, or a module when --input is set\n  --schema-dir <dir>    Directory of JSON Schemas, processed recursively (instead of --schema)\n  --input <format>      Schema source format: json (default), typebox, zod, valibot, effect, avro,\n                        or asyncapi (an AsyncAPI 2.x/3.0 document, JSON or YAML)\n  --export <name>       Which export of the schema module to use when --input names a module format\n\nOutput:\n  --out-dir <dir>       Output directory for the generated files\n  --out-file <file>     Single-file output instead of a directory (requires --types-only)\n  --types-only          Generate type definitions only, without parser functions\n  --validators          Also emit validateX/isX validators beside the parsers, over one\n                        shared declaration of each generated type\n  --validators-only     Emit the validator half and no parser: the type, isX, validateX and\n                        whichever of checkX/coerceX/repairX were asked for (implies\n                        --validators; the mirror of --types-only)\n  --check               Also emit checkX, the same result as validateX but stopped at the\n                        first violation (requires --validators)\n  --coerce              Also emit coerceX, which coerces scalars the way Ajv's coerceTypes\n                        does and then validates (requires --validators)\n  --repair              Also emit repairX, which coerces, validates, then repairs each\n                        rejected position to a schema-supplied value and reports the\n                        errors it repaired (implies --coerce; requires --validators)\n  --branch-errors       Explain a failing anyOf/oneOf with the errors of the branch it\n                        meant (requires --validators; costs a little on unions)\n  --examples            Also emit fast-check arbitraries + example values under examples/\n  --message-contracts   Also emit @amritk/api channel contracts under contracts/ (--input asyncapi only)\n  --discriminator <p>   Property naming which message a frame is, for --message-contracts (default: type)\n  --build               Compile the generated files to .js/.d.ts (implies --import-ext js)\n  --force               Deprecated; ignored (generated files always overwrite)\n  --import-ext <ext>    Extension on generated relative imports: ts (default) or js\n  --helpers <mode>      Runtime helpers: package or embedded (default: auto-detect from package.json)\n  --root-type <name>    Root type name for a single --schema run (default: schema title or filename)\n  --type-suffix <s>     Suffix appended to every $ref-derived type name\n  --banner [text]       Prepend a header comment to every generated file\n  --readonly            Emit deeply readonly type definitions\n\nValidation:\n  --strict              Throw on type/shape mismatches instead of coercing to defaults\n  --strip-unknown       Silently drop undeclared input keys at every nesting level\n  --case-insensitive    Normalize mis-cased enum/const strings to their exact casing\n  --log-warnings        console.warn on input keys not declared in the schema\n  --unknown-keys <s>    How closed objects are proven free of undeclared keys:\n                        count-keys (default, fastest on Bun) or count-enumerable (fastest on Node)\n  --formats <f>         String formats the generated validators enforce: \"all\", or a\n                        comma-separated list (e.g. uuid,date-time,email). Off by default,\n                        which leaves \"format\" an annotation as JSON Schema reads it.\n\nReference resolution:\n  --resolve-remote      Fetch http(s) $refs while resolving cross-file/remote refs (off by default)\n  --allowed-hosts <h>   Restrict remote $ref fetches to these hosts (comma-separated; implies --resolve-remote)\n  --allow-private-hosts Permit remote $refs to private/loopback hosts (SSRF guard, off by default)\n  --allowed-roots <d>   Extra directories a local $ref may resolve into, on top of the schema's own\n                        (comma-separated; relative to the current directory)\n\nMisc:\n  --config <path>       JSON config file with the same keys; CLI flags take precedence\n  --version, -v         Print the CLI version\n  --help, -h            Print this help\n\nDocs: https://github.com/amritk/mjst/tree/main/packages/cli#readme\n";

package/dist/help-text.js

@@ -1,4 +1,4 @@
-const HELP_TEXT = `mjst \u2014 generate TypeScript parsers and type definitions from JSON Schemas
+const HELP_TEXT = `mjst \u2014 generate TypeScript types, validators and parsers from JSON Schemas
 
 Usage:
   mjst --schema <path> --out-dir <dir> [options]
@@ -23,6 +23,9 @@ Output:
   --types-only          Generate type definitions only, without parser functions
   --validators          Also emit validateX/isX validators beside the parsers, over one
                         shared declaration of each generated type
+  --validators-only     Emit the validator half and no parser: the type, isX, validateX and
+                        whichever of checkX/coerceX/repairX were asked for (implies
+                        --validators; the mirror of --types-only)
   --check               Also emit checkX, the same result as validateX but stopped at the
                         first violation (requires --validators)
   --coerce              Also emit coerceX, which coerces scalars the way Ajv's coerceTypes

package/dist/load-config.js

@@ -30,6 +30,7 @@ const loadConfig = async (configPath) => {
     ...typeof obj["export"] === "string" && { export: obj["export"] },
     ...typeof obj["validators"] === "boolean" && { validators: obj["validators"] },
     ...typeof obj["typesOnly"] === "boolean" && { typesOnly: obj["typesOnly"] },
+    ...typeof obj["validatorsOnly"] === "boolean" && { validatorsOnly: obj["validatorsOnly"] },
     ...typeof obj["examples"] === "boolean" && { examples: obj["examples"] },
     ...typeof obj["messageContracts"] === "boolean" && { messageContracts: obj["messageContracts"] },
     ...typeof obj["discriminator"] === "string" && { discriminator: obj["discriminator"] },

package/dist/markdown/help-text.d.ts

@@ -3,4 +3,4 @@
  * HELP_TEXT: the flag list is small and stable, and the test cross-checks that
  * every flag is listed.
  */
-export declare const MARKDOWN_HELP_TEXT = "mjst markdown \u2014 generate markdown documentation from a JSON Schema\n\nUsage:\n  mjst markdown <schema> --out-dir <dir> [options]\n  mjst markdown <schema> --table --readme <file>\n\nTwo shapes come out of the same schema. By default it writes the prose\nreference \u2014 a heading, a type, the description and an example per property,\nacross as many pages as the schema's x-doc keyword declares. With --table it\nrenders one HTML table instead and splices it into an existing markdown file\nbetween <!-- config-table-start --> and <!-- config-table-end -->, leaving the\nrest of that file alone.\n\nProse reference options:\n  --out-dir <dir>      Directory the pages are written to (default: the current directory)\n  --file <path>        Output path of the index page (default: the schema's x-doc.file, then index.md)\n  --title <text>       Page title (default: the schema's title)\n  --language <lang>    Fence language for derived examples and literals (default: json)\n  --layout <mode>      Default layout for nested properties: headings (default), table, or none\n  --sort <order>       Property order: schema (default) or alphabetical\n  --heading-level <n>  Heading level of the page title, 1-6 (default: 1)\n\nTable options:\n  --table              Render the HTML config table instead of the prose pages\n  --readme <path>      Markdown file the table is spliced into (default: README.md)\n\nMisc:\n  --help, -h           Print this help\n\nDocs: https://github.com/amritk/mjst/tree/main/packages/cli#readme\n";
+export declare const MARKDOWN_HELP_TEXT = "mjst markdown \u2014 generate markdown documentation from a JSON Schema\n\nUsage:\n  mjst markdown <schema> --out-dir <dir> [options]\n  mjst markdown <schema> --table --readme <file>\n\nTwo shapes come out of the same schema. By default it writes the prose\nreference \u2014 a heading, a type, the description and an example per property,\nacross as many pages as the schema's x-doc keyword declares. With --table it\nrenders one HTML table instead and splices it into an existing markdown file\nbetween <!-- config-table-start --> and <!-- config-table-end -->, leaving the\nrest of that file alone.\n\nProse reference options:\n  --out-dir <dir>      Directory the pages are written to (default: the current directory)\n  --file <path>        Output path of the index page (default: the schema's x-doc.file, then index.md)\n  --title <text>       Page title (default: the schema's title)\n  --language <lang>    Fence language for derived examples and literals (default: json)\n  --layout <mode>      Default layout for nested properties: headings (default), table, or none\n  --sort <order>       Property order: schema (default) or alphabetical\n  --heading-level <n>  Heading level of the page title, 1-6 (default: 1)\n\nProperty table options (the root x-doc.table, for every table on every page):\n  --type-column <when>     Render the Type column: auto (default), always, or never\n  --default-column <when>  Render the Default column: auto (default), always, or never\n  --required-style <how>   Say which properties are required: marker (default, beside\n                           the name) or column (a Required column)\n  --required-first         List the required properties at the top of every table\n\nTable options:\n  --table              Render the HTML config table instead of the prose pages\n  --readme <path>      Markdown file the table is spliced into (default: README.md)\n\nMisc:\n  --help, -h           Print this help\n\nDocs: https://github.com/amritk/mjst/tree/main/packages/cli#readme\n";

package/dist/markdown/help-text.js

@@ -20,6 +20,13 @@ Prose reference options:
   --sort <order>       Property order: schema (default) or alphabetical
   --heading-level <n>  Heading level of the page title, 1-6 (default: 1)
 
+Property table options (the root x-doc.table, for every table on every page):
+  --type-column <when>     Render the Type column: auto (default), always, or never
+  --default-column <when>  Render the Default column: auto (default), always, or never
+  --required-style <how>   Say which properties are required: marker (default, beside
+                           the name) or column (a Required column)
+  --required-first         List the required properties at the top of every table
+
 Table options:
   --table              Render the HTML config table instead of the prose pages
   --readme <path>      Markdown file the table is spliced into (default: README.md)

package/dist/markdown/parse-markdown-args.d.ts

@@ -1,4 +1,4 @@
-import type { DocLayout, DocSort } from '@amritk/generate-markdown';
+import type { DocLayout, DocSort, DocTableColumn, DocTableRequired } from '@amritk/generate-markdown';
 /** The flags and positional the `markdown` subcommand understands. */
 export type MarkdownArgs = {
     /** Path to the JSON Schema to document (the sole positional). */
@@ -17,6 +17,14 @@ export type MarkdownArgs = {
     sort?: DocSort;
     /** Heading level of the page title (`--heading-level`). */
     headingLevel?: number;
+    /** When property tables render their Type column (`--type-column`). */
+    typeColumn?: DocTableColumn;
+    /** When property tables render their Default column (`--default-column`). */
+    defaultColumn?: DocTableColumn;
+    /** How property tables say which properties are required (`--required-style`). */
+    requiredStyle?: DocTableRequired;
+    /** True when `--required-first` was passed: required properties head every table. */
+    requiredFirst?: boolean;
     /** True when `--table` was passed: render the HTML table instead of the pages. */
     table?: boolean;
     /** Markdown file the table is spliced into (`--readme`). */

package/dist/markdown/parse-markdown-args.js

@@ -1,7 +1,21 @@
-const VALUE_KEYS = /* @__PURE__ */ new Set(["outDir", "file", "title", "language", "layout", "sort", "headingLevel", "readme"]);
-const BOOLEAN_KEYS = /* @__PURE__ */ new Set(["table"]);
+const VALUE_KEYS = /* @__PURE__ */ new Set([
+  "outDir",
+  "file",
+  "title",
+  "language",
+  "layout",
+  "sort",
+  "headingLevel",
+  "typeColumn",
+  "defaultColumn",
+  "requiredStyle",
+  "readme"
+]);
+const BOOLEAN_KEYS = /* @__PURE__ */ new Set(["table", "requiredFirst"]);
 const LAYOUTS = ["headings", "table", "none"];
 const SORTS = ["schema", "alphabetical"];
+const TABLE_COLUMNS = ["auto", "always", "never"];
+const REQUIRED_STYLES = ["marker", "column"];
 const toCamelCase = (key) => key.replace(/-([a-z])/g, (_, c) => c.toUpperCase());
 const parseChoice = (flag, value, choices) => {
   const match = choices.find((choice) => choice === value);
@@ -40,6 +54,15 @@ const assignValue = (args, key, value) => {
     case "headingLevel":
       args.headingLevel = parseHeadingLevel(value);
       return;
+    case "typeColumn":
+      args.typeColumn = parseChoice("type-column", value, TABLE_COLUMNS);
+      return;
+    case "defaultColumn":
+      args.defaultColumn = parseChoice("default-column", value, TABLE_COLUMNS);
+      return;
+    case "requiredStyle":
+      args.requiredStyle = parseChoice("required-style", value, REQUIRED_STYLES);
+      return;
     case "readme":
       args.readme = value;
       return;
@@ -78,7 +101,10 @@ const parseMarkdownArgs = (argv) => {
     const flagName = arg.slice(2);
     const key = toCamelCase(flagName);
     if (BOOLEAN_KEYS.has(key)) {
-      args.table = true;
+      if (key === "requiredFirst")
+        args.requiredFirst = true;
+      else
+        args.table = true;
       continue;
     }
     if (!VALUE_KEYS.has(key))

package/dist/markdown/run.js

@@ -6,7 +6,19 @@ const usageError = (message) => ({ code: 2, stdout: "", stderr: `Error: ${messag
 ` });
 const failure = (message) => ({ code: 1, stdout: "", stderr: `Error: ${message}
 ` });
-const PAGE_FLAGS = ["outDir", "file", "title", "language", "layout", "sort", "headingLevel"];
+const PAGE_FLAGS = [
+  "outDir",
+  "file",
+  "title",
+  "language",
+  "layout",
+  "sort",
+  "headingLevel",
+  "typeColumn",
+  "defaultColumn",
+  "requiredStyle",
+  "requiredFirst"
+];
 const run = async (argv) => {
   let args;
   try {
@@ -51,7 +63,15 @@ const run = async (argv) => {
     language: args.language,
     layout: args.layout,
     sort: args.sort,
-    headingLevel: args.headingLevel
+    headingLevel: args.headingLevel,
+    // Always passed: every member is optional, so the schema's own
+    // `x-doc.table` still decides whatever the flags left alone.
+    table: {
+      type: args.typeColumn,
+      default: args.defaultColumn,
+      required: args.requiredStyle,
+      requiredFirst: args.requiredFirst
+    }
   };
   let files;
   try {

package/dist/parse-cli-args.js

@@ -4,6 +4,7 @@ const LIST_KEYS = /* @__PURE__ */ new Set(["allowedHosts", "allowedRoots"]);
 const BOOLEAN_KEYS = /* @__PURE__ */ new Set([
   "typesOnly",
   "validators",
+  "validatorsOnly",
   "check",
   "coerce",
   "repair",
@@ -128,6 +129,9 @@ const assignBoolean = (config, key, value) => {
     case "typesOnly":
       config.typesOnly = value;
       return true;
+    case "validatorsOnly":
+      config.validatorsOnly = value;
+      return true;
     case "validators":
       config.validators = value;
       return true;

package/dist/resolve-modes.d.ts

@@ -1,4 +1,4 @@
-import type { Mode } from '@amritk/parsers';
+import type { Mode } from '@amritk/validation';
 import type { CliConfig } from './cli-config.js';
 /**
  * Turns the flags a run was given into the list of entry points `generate()`
@@ -11,7 +11,9 @@ import type { CliConfig } from './cli-config.js';
  *
  * `--types-only` is the one run with nothing to execute, so it stops at `types`
  * — asking for a parser there would emit runtime code the flag exists to avoid.
- * Everything else always carries a parser, because emitting one is what the CLI
- * does when you do not tell it otherwise.
+ * `--validators-only` is its mirror at the other end: everything that judges a
+ * document, and nothing that builds one. Between them, every run carries a
+ * parser, because emitting one is what the CLI does when you do not tell it
+ * otherwise.
  */
 export declare const resolveModes: (config: Partial<CliConfig>) => Mode[];

package/dist/resolve-modes.js

@@ -2,7 +2,7 @@ const resolveModes = (config) => {
   if (config.typesOnly === true)
     return ["types"];
   const modes = ["types"];
-  if (config.validators === true) {
+  if (config.validators === true || config.validatorsOnly === true) {
     modes.push("guard", "validate");
     if (config.check === true)
       modes.push("check");
@@ -11,7 +11,9 @@ const resolveModes = (config) => {
     if (config.repair === true)
       modes.push("repair");
   }
-  modes.push(config.strict === true ? "parseStrict" : "parse");
+  if (config.validatorsOnly !== true) {
+    modes.push(config.strict === true ? "parseStrict" : "parse");
+  }
   return modes;
 };
 export {

package/dist/validate-config.js

@@ -8,6 +8,7 @@ const CONFIG_KEYS = {
   outDir: { type: "string" },
   outFile: { type: "string" },
   typesOnly: { type: "boolean" },
+  validatorsOnly: { type: "boolean" },
   validators: { type: "boolean" },
   check: { type: "boolean" },
   coerce: { type: "boolean" },

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@amritk/mjst",
-  "version": "0.22.0",
+  "version": "0.23.0",
   "description": "Generate TypeScript parsers and type definitions from JSON Schemas.",
   "type": "module",
   "engines": {
@@ -49,14 +49,14 @@
     "./package.json": "./package.json"
   },
   "dependencies": {
-    "@amritk/adapters": "^0.6.4",
+    "@amritk/adapters": "^0.6.5",
     "@amritk/api": "^0.16.5",
-    "@amritk/asyncapi": "^0.3.2",
-    "@amritk/generate-examples": "^0.8.6",
-    "@amritk/generate-markdown": "^0.8.0",
-    "@amritk/helpers": "^0.23.0",
+    "@amritk/asyncapi": "^0.3.3",
+    "@amritk/generate-examples": "^0.8.7",
+    "@amritk/generate-markdown": "^0.9.0",
+    "@amritk/helpers": "^0.23.1",
     "@amritk/lint": "^0.6.1",
-    "@amritk/parsers": "^0.2.0",
+    "@amritk/validation": "^0.3.0",
     "@amritk/resolve-refs": "^0.7.1",
     "@amritk/yaml": "^0.7.2",
     "fast-glob": "^3.3.2",