template-kit pack
The `template-kit pack` command — what it produces, what it refuses, and why.
Build a template’s submission artifact: a zip of the template’s source plus the workspace lockfile, validated and stamped.
template-kit pack <template>Run it from the workspace root, or from inside a template folder (the template is inferred). In a workspace with several templates you must name one — the submission unit is a single template.
What it produces
Section titled “What it produces”<template>.zip at the workspace root, containing:
pack-manifest.json— the exact kit version the source was validated against, a content hash of the template tree, the pack timestamp, and acheckflag recording that validation passed.package.jsonandpackage-lock.jsonfrom the workspace root, so the build is reproducible withnpm ci.templates/<template>/— the template’s source only (sections, manifest, theme, README). Nonode_modules, no build output, no other template.
What it refuses
Section titled “What it refuses”pack will not produce a zip when:
check <template>is not green — fix the reported problems first.- the workspace has no
package-lock.json— runnpm installand commit it. - a dependency uses a local
file:/link:protocol — depend on published versions.
Fix the reported cause and run it again.
See also
Section titled “See also”- Check — the gate
packruns before it will produce a zip.