Small CLI for scaffolding and managing Gista.js starter projects.

npx gistajs create my-app
npx gistajs create my-app --starter website --no-install --no-git

Today the CLI covers project creation, starter diffs, pin management, Turso provisioning, and Vercel provisioning. For starters that define pnpm prep, gistajs create offers to run that setup step after dependencies install.

Plan a local add-on install against the current project:

npx gistajs add ./addons/storage

gistajs add is planning-only right now. It prints the files that would be created or blocked, plus any manual touchpoints the host project needs to wire.

Compare the starter changes since your project's pinned release:

npx gistajs diff --latest                            # full diff from project pin to latest release
npx gistajs diff --latest --stat                     # summary only

Or compare changes between starter releases:

npx gistajs diff auth 2026-03-28-001 2026-03-29-001        # full diff
npx gistajs diff auth 2026-03-28-001 2026-03-29-001 --stat # summary only

Advance your project pin after accepting an upgrade:

npx gistajs pin 2026-04-01-001

Scaffolded projects carry one base starter lineage for their lifetime. That baseline lives in package.json as gistajs.pin:

{
  "gistajs": {
    "pin": "form:2026-04-01-001"
  }
}

gistajs diff --latest uses that pin as the starting point and compares it to the latest published release for the same starter. After you accept an upgrade, advance the pin explicitly with gistajs pin <release-key>.

Provision the current project from its package.json metadata:

npx gistajs provision

For starters that declare Turso and Vercel, this prompts for a shared deployment region, provisions Turso first, writes DB_URL plus DB_AUTH_TOKEN into .env, and then syncs COOKIE_SECRET, DB_URL, and DB_AUTH_TOKEN to Vercel production envs. The command checks the project's declared gistajs dependency first and fails clearly if the installed CLI is too old.

You can still run a provider directly when debugging:

npx gistajs provision turso
npx gistajs provision vercel

The command is interactive. It asks for a shared region first, defaults new projects to Turso's nearest region when available, falls back to Oregon otherwise, reuses the saved gistajs.region on later runs, creates a Turso group in that region when needed, links Vercel when needed, and asks before overwriting existing database credentials in .env.

pnpm install
pnpm typecheck
pnpm build
pnpm test
pnpm build && node dist/bin.cjs logo

pnpm np