CLI

✔ All prerequisites satisfied.
ℹ Selected Edge Kit
ℹ Writing wrangler.jsonc...
✔ Worker name, vars, and bindings set.
✔ Stripe, auth, and Turnstile skipped.
✔ Dependencies installed.
✔ Local D1 database ready.
✔ Git configured with upstream.
✔ Project initialization completed.

To help you get started with Edge Kit as quickly as possible, we use the same CLI as Core and AI. One new command clones the kit, writes env files, configures wrangler.jsonc, and prepares a local services.

The CLI is in beta. Commands and prompts may evolve as we ship more kits and setup flows.

Installation

You can run commands without installing globally:

npx @turbostarter/cli@latest <command>

pnpm dlx @turbostarter/cli@latest <command>

yarn dlx @turbostarter/cli@latest <command>

bunx @turbostarter/cli@latest <command>

Or install globally and run:

npm install -g @turbostarter/cli

turbostarter <command>

pnpm add -g @turbostarter/cli

turbostarter <command>

yarn global add @turbostarter/cli

turbostarter <command>

bun add -g @turbostarter/cli

turbostarter <command>

Use --help or -v for help and the installed version.

Commands that touch an existing repo (like project update) must run from the project root, or pass --cwd to point at it.

New projects

npx @turbostarter/cli@latest new -k edge

Without -k, pick Edge Kit (new) when the CLI asks which kit to use.

Options:

Examples:

npx @turbostarter/cli@latest new -k edge
npx @turbostarter/cli@latest new --kit edge --cwd ~/projects

You will be asked a few questions to configure your project:

✔ All prerequisites satisfied, let's start! 🚀

? Which kit do you want to use? › Edge Kit (new)
? Enter your project name. › Acme
? Configure all providers now? ›
    Yes, configure now (recommended)
    No, just let me ship, now!

Let's configure it!
You can skip any step by pressing enter.

? Configure contact and sender email? › Yes
? Contact inbox email › hello@acme.com
? Sender email address › noreply@acme.com
? Configure authentication methods and OAuth? › No
? Configure Turnstile? › No
? Configure Stripe? › No
? Configure Cloudflare Web Analytics? › No

Creating a new Edge Kit project in .../acme

✔ Repository successfully pulled!
✔ Environment variables successfully set!
✔ Dependencies successfully installed!
✔ Local D1 database ready!
✔ Git successfully configured!

🎉 Edge Kit is ready in .../acme!
> cd acme
> pnpm dev

The CLI clones turbostarter/edge, copies .env.example to .env.local, sets environment variables and points upstream at the kit repository. If you configure providers, it writes those values into .env.local and into wrangler.jsonc vars (public keys and config only).

Updates

npx @turbostarter/cli@latest project update

Optional: -c, --cwd <path> to target a project outside the current directory.

Before updating, the CLI validates that:

• You are running from a TurboStarter project root (or the path you passed)
• Your git working tree is clean
• Your upstream remote matches Edge Kit (turbostarter/edge)

Then it fetches upstream and merges upstream/main into your current branch. If conflicts occur, it lists the conflicting files and the next git add / git commit steps.