What It Does
This quickstart gets you from dependency install to running app(s) with local Supabase.
When To Use
- First local run.
- Verifying environment after pulling updates.
Prerequisites
- Node.js
>=20 pnpm- Docker Desktop
Important
This page describes the standard kit integration path; adapt app-specific paths and config names when your project differs.
How To Use
Install dependencies.
pnpm installGenerate SQL artifacts and start Supabase.
pnpm run db:generate
pnpm run supabase:startCopy test env template for the app you run.
cp apps/dashboard/.env.test apps/dashboard/.env.local
cp apps/marketing/.env.test apps/marketing/.env.localStart app dev server.
pnpm --filter ./apps/dashboard dev
# or
pnpm --filter ./apps/marketing devCapability Map
| Capability | Main docs |
|---|---|
| Settings API | /docs/web/features/settings |
| Auth | /docs/web/features/authentication |
| Billing | /docs/web/features/billing |
| Monitoring | /docs/web/features/monitoring |
| Translations | /docs/web/features/translations |
| CMS/Docs | /docs/web/features/cms |
MCP Context
capability: bootstrap_project
entrypoints:
- package.json scripts
- apps/*/.env.test
inputs:
- selected_app
outputs:
- running_local_app
constraints:
- docker required for local supabase
- app env vars must be present
side_effects:
- installs dependencies
- starts local servicesAgent Recipe
- Run install and DB bootstrap commands from root.
- Copy the relevant
.env.testto.env.local. - Start one app with workspace filtering and validate route load.
Troubleshooting
- If auth/database routes fail, confirm Supabase is running (
pnpm run supabase:start). - If build fails on missing envs, compare
.env.localagainstenvs.tsin that app.
Related
How is this guide?
Last updated on 3/23/2026