create-pinarkive-app
v0.1.2
Published
CLI to scaffold official PinArkive starter templates (Next.js, Vite, or Cloudflare Workers).
Maintainers
Readme
create-pinarkive-app
Small CLI to scaffold an official PinArkive starter into a new folder—no git history in the output (uses degit).
These starters are intended to be published as public repositories under the PinArkive GitHub organization and are free to use.
What it does
- Prompts for a project folder name and starter (or use flags).
- Downloads the selected repo’s
mainbranch from GitHub. - Ensures the target directory is missing or empty.
- Removes
.gitfrom the generated project if present. - Prints next steps (
cd, env file,npm install,npm run dev).
Generated projects come from the official PinArkive starter repositories:
| Template flag | Source repo |
|---------------|-------------|
| next | pinarkive/starter-next-supabase (main) |
| vite | pinarkive/starter-vite-react (main) |
| workers | pinarkive/starter-hono-workers (main) |
Usage
npx create-pinarkive-appNon-interactive (requires folder name + template):
npx create-pinarkive-app my-app --template next --yes
npx create-pinarkive-app my-app --template vite --yes
npx create-pinarkive-app my-app --template workers --yesFlags:
--template next|vite|workers(alias:-t)--yes/-y— skip prompts (must pass project name and--template)
Local development
cd create-pinarkive-app
npm install
npm run devnpm run dev runs node --watch index.js (Node 18+). Use npm start for a single run.
Test locally without publishing
From this package directory:
npm linkThen elsewhere:
create-pinarkive-app
# or
node /path/to/create-pinarkive-app/index.jsTo unlink: npm unlink -g create-pinarkive-app (or npm unlink create-pinarkive-app from the package folder).
Publish to npm
Bump
versioninpackage.json.Ensure you are logged in:
npm loginPublish scoped or unscoped as your org allows:
npm publish --access publicThe
create-pinarkive-appbinary is declared inpackage.json→bin.
Requires Node 18+.
Requirements
- Network access to clone from GitHub.
- Write permission in the current working directory.
Future ideas
- Auto install — optional
npm installin the new folder after scaffold. - More flags — additional non-interactive options (e.g. package manager).
- Docs media — link preview GIFs in starter READMEs after they are recorded post-publish.
