CLI reference
Every `template-kit` command, with its full flag surface, exit codes and constraints.
One page per command, generated from the CLI’s own command definitions — so a flag
reaches this reference because it was declared, not because someone remembered the
page. Run template-kit --help for the same list at the terminal.
Authoring commands
Section titled “Authoring commands”| Command | What it does | Synopsis |
|---|---|---|
dev |
Start the local preview server | template-kit dev [template] [--port <n>] [--diagnostics-cmd <cmd>] [--no-auto-update] |
check |
Typecheck, lint, and validate a template | template-kit check [template] [--all] [--json] [--provenance] [--no-auto-update] |
theme |
Generate a template’s theme CSS from its theme.ts | template-kit theme [template] [--all] [--no-auto-update] |
pack |
Build a template’s submission zip | template-kit pack [template] [--no-auto-update] |
upgrade |
Move the workspace onto the latest @homepages release | template-kit upgrade [--dry-run] [--to <version>] |
Kit development
Section titled “Kit development”These drive the kit’s own development loop. A template author never needs them.
| Command | What it does | Synopsis |
|---|---|---|
status |
Show the installed kit version | template-kit status [workspace] |
Versions
Section titled “Versions”These pages describe @homepages/template-cli >=9.0.0 <10.0.0. The range, rather
than the exact version they were generated from: this corpus is committed build
output, so a page stamped with a patch version would be stale the day it shipped.
That CLI drives any @homepages/template-kit in ^9.0.0. A release ships
the two at one version, but an install can still pair them anywhere in that window,
which is why template-kit --version prints both.