#!/usr/bin/env node /** * create-litro — Scaffolding CLI for Litro * * Usage: * npm create @beatzball/litro * npx @beatzball/create-litro * npx @beatzball/create-litro [--recipe ] [--mode ] [--adapter ] * * is a path, not a bare name. Relative to the current * directory, or absolute, and a quoted leading `~` means your home * directory. The project is named after the last segment. * * A recipe declares which adapters it can produce. Asking for one it cannot is * refused before anything is written, and the prompt offers only what it can. * * A DEPRECATED adapter is off the prompt but still resolves from --adapter, and * prints a notice saying when it is removed. * * Documentation site for an existing repository: * npx @beatzball/create-litro site --recipe starlight --for-repo . \ * --site-url https://example.dev * * --for-repo read the repo's name, description, remote and default * branch, then write metadata, the starlight config, * a deploy (Dockerfile + nginx.conf) and an AGENTS.md * --site-url canonical URL the site is served from * --deploy deploy files to emit (default: docker) * --with-blog keep the recipe's sample blog (default: removed) * * Recipe options: * --blog, --no-blog answer a recipe's "Include a blog?" question without * being asked. Only for a recipe that offers it. * * npx @beatzball/create-litro --list-recipes * * Prompts for project name, recipe, and mode, then scaffolds a complete * Litro project from the selected recipe template. * * No external dependencies — uses Node.js built-ins only. */ export {}; //# sourceMappingURL=index.d.ts.map