Framework CLI overview
Use the tavo CLI as the supported interface for creating, understanding, validating, building, and shipping a Tavo.js application.
What the CLI owns
The framework CLI understands Tavo.js routes, layouts, stores, generators, and provider-neutral build artifacts. Prefer it over hand-written framework plumbing because its output stays aligned with the installed package version.
Choose a workflow
Start or extend an app
Scaffold a project, then generate functional routes, components, stores, actions, and layouts.Read guide →
Understand a project
Run development servers and inspect routes, inventory, diagnostics, and individual entities.Read guide →
Validate production
Generate route types and production output, enforce budgets, and preview the real SSR build.Read guide →
Ship and observe
Build static or Node output and read protected production runtime metrics.Read guide →
Automate safely
Use bounded JSON context, hashes, dry runs, change receipts, and focused verification.Read guide →
Run the project-local version
Generated applications install @tavojs/cli as a development dependency, which makes the project-local tavo binary available. Use the generated package scripts for normal development. For a command without a script, use npx from the project root so it resolves the installed binary and contributors and CI use the version in the lockfile.
bashnpm run dev
npx tavo --version
npx tavo --help
# Equivalent local execution:
pnpm exec tavo --version
yarn tavo --version
bun run tavo --version