Skip to content
HomePagesHomePages template kit
Menu

Prepare a submission

Package a template for submission.

Package a template for submission.

Get the template to a green check, then pack it:

Terminal window
template-kit check <template>
template-kit pack <template>

pack will not produce a zip until check <template> passes — it re-runs the same gate itself, and a failing check reports every problem in one pass, not one at a time, so a manual check first is just a faster feedback loop, not a separate requirement. A passing pack writes <template>.zip at the workspace root: the template’s source, pack-manifest.json (the kit version, a content hash, and the check flag), and the workspace’s package.json / package-lock.json so the build reproduces with npm ci.

pack refuses to write a zip when:

  • check <template> is not green — fix the reported problems first.
  • the workspace has no package-lock.json — run npm install and commit it.
  • a dependency uses a local file:/link: protocol — depend on a published version instead.

Each refusal prints the cause; fix it and run pack again.

Terminal window
template-kit check <template>
template-kit pack <template>

Verify with the author looppack refuses to build the zip until check is green, so a clean loop is the gate.

  • Pack — what the zip contains and the full refusal list.
  • Check — the gate pack runs before it will produce a zip.