For the complete documentation index, see llms.txt. Prefer markdown by appending.mdto documentation URLs or sendingAccept: text/markdown.
CLI
Create a new TurboStarter project from the CLI with your preferred apps preconfigured. Fastest path from install to running Expo.
✔ All prerequisites satisfied.ℹ Selected - Core Kitℹ Configuring web app...✔ Billing and email ready.✔ Feature flags configured.ℹ Configuring mobile app...✔ Auth and store billing set up.ℹ Skipping browser extension.✔ Dependencies installed.✔ Local database started.✔ Project initialization completed.To help you get started with TurboStarter as quickly as possible, we've developed a CLI that bootstraps a new project (with configuration) in seconds.
One new command covers every kit:
- Core Kit - web (required), optional mobile and browser extension, plus billing, email, analytics, monitoring, and feature flags
- AI Kit - web with optional mobile, plus AI Gateway, model providers, tools, voice, and storage env setup
- Edge Kit - Cloudflare app with Wrangler bindings and local D1
You can also update an existing project by merging the latest upstream changes for the kit you already use.
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.
Starting a new project
Use the new command to initialize configuration and dependencies for a new project.
npx @turbostarter/cli@latest newOptions:
| Flag | Description |
|---|---|
-k, --kit <core|ai|edge> | Skip the kit prompt and create that kit |
-c, --cwd <path> | Directory where the project folder is created (defaults to the current directory) |
Examples:
npx @turbostarter/cli@latest new -k core
npx @turbostarter/cli@latest new --kit ai --cwd ~/projectsYou will be asked a few questions to configure your project:
✔ All prerequisites satisfied, let's start! 🚀
? Which kit do you want to use? › Core Kit
? Enter your project name. › Acme
? What do you want to ship? ›
◉ Web app
◉ Mobile app
◯ Browser extension
? Configure all providers now? ›
Yes, configure now (recommended)
No, just let me ship, now!
Creating a new TurboStarter project in ...
✔ Repository successfully pulled!
✔ Git successfully configured!
✔ Dependencies successfully installed!
✔ Services successfully started!
🎉 Core Kit is ready in .../acme!
> cd acme
> pnpm devThe CLI clones the kit repo, prepares env files, installs dependencies with pnpm, points upstream at the kit repository, and creates an initial commit. For kits with a local services, it also starts Docker and runs setup for all of them (Docker must be available for that path).
Updating an existing project
npx @turbostarter/cli@latest project updateOptional: -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
upstreamremote matches the detected kit (turbostarter/core,turbostarter/ai, orturbostarter/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.
Prefer the CLI for day-to-day updates
project update is the fastest path when your tree is clean. For a full manual walkthrough (stash, resolve lockfile conflicts, health checks), see Updating codebase.
How is this guide?
Last updated on