LPM CLI

JSON Schemas

Published and locally emitted JSON Schemas for lpm.json and lpm.config.json.

lpm schema lpm.json
lpm schema lpm.config.json
lpm schema lpm.json -o schema.json

LPM ships JSON Schemas for the two JSON config files it owns: lpm.json and lpm.config.json. Use the published URLs for editor autocomplete, or use lpm schema to emit the schema from the exact CLI version installed on your machine.

Published URLs

FileCanonical schema URLCompatibility alias
lpm.jsonhttps://cli.lpm.dev/schemas/lpm.jsonhttps://lpm.dev/schemas/lpm.json
lpm.config.jsonhttps://cli.lpm.dev/schemas/lpm.config.jsonhttps://lpm.dev/schemas/lpm.config.json

Use the canonical cli.lpm.dev URL in new files:

lpm.json
{
  "$schema": "https://cli.lpm.dev/schemas/lpm.json"
}
lpm.config.json
{
  "$schema": "https://cli.lpm.dev/schemas/lpm.config.json"
}

Emit Locally

lpm schema lpm.json
lpm schema lpm.config.json

Without -o, LPM pretty-prints the schema to stdout. With -o / --out, it writes the pretty-printed JSON to that path:

lpm schema lpm.json -o lpm.schema.json
lpm schema lpm.config.json --out lpm-config.schema.json

lpm schema accepts only these two kinds:

KindSource of truth
lpm.jsonAuto-derived from the typed Rust struct that parses lpm.json.
lpm.config.jsonHand-authored alongside the lpm add consumer code, with drift tests against the published copy.

Unknown kinds fail with a message listing the supported values.

Flags

FlagEffect
-o <PATH>, --out <PATH>Write the schema to a file instead of stdout.

Plus the global flags.

See also

  • lpm.json - runtime, tasks, services, tunnel, env, and publish config
  • lpm.config.json - source-package installer config
  • lpm add - consumer flow for packages that ship lpm.config.json
  • lpm dev - common lpm.json consumer