next-forge

Run bun install from the repository root, set DATABASE_URL for the database package, then start development with bun run dev. Use Turbo filters like bun run dev --filter app to scope work to a single app.

Deployable apps live under apps/ (app, web, api, email, docs, storybook) and shared modules live under packages/ imported as @repo/<name>. Authenticated product routes go in apps/app/app/api, public commerce routes in apps/web/app/api, and webhooks in apps/api/app/webhooks.

Replace the owning package first, such as packages/auth or packages/payments, then update the consuming route handlers like apps/app/app/api/auth/[...all]/route.ts or apps/api/app/webhooks/payments/route.ts. Also update env validation in the package keys.ts and any app env.ts files.

This repo uses Drizzle with the Neon serverless driver on PostgreSQL, not Prisma. Use bun run db:generate, db:migrate, db:push, and db:studio for schema workflows, and define tables in packages/database/schema.ts.

Env validation is split across package-level keys.ts files and each app's env.ts composition. Check packages/*/keys.ts for development fallbacks, then verify the consuming app actually composes that package's schema in its env.ts.

Treat app, web, and api as separate Vercel projects with their own root directories. Set shared environment variables like DATABASE_URL and NEXT_PUBLIC_* URLs across projects, and add provider-specific values only to the apps that need them.