Run builds, tests and type checks across your apps in dependency order, with cached results.

5 files · 6 KB

Turborepo ↗

Why I keep it

I keep the site, API and shared packages in one repo, so Turborepo can run their checks in the right order. WithSeismic, Benson and Vouchernaut all use it. The agent gets the whole tree, while Turbo works out which tasks depend on which packages.

A cached build once left WithSeismic’s analytics missing, so the environment rules matter as much as the task graph. I’ve included the starter’s turbo.json and a commented Next.js variant, plus workspace config and root scripts, so you can declare your own build inputs explicitly.

Take the files

5 files · 6 KB

  • README.md2 KB
  • package.json875 B
  • pnpm-workspace.yaml103 B
  • turbo.json1 KB
  • turbo.nextjs.json2 KB

Keep building your setup: The stack

Back to the shelves →
  • 015 files · 151 KB

    The SaaS starter

    Start with accounts, organisations, email and analytics wired into a React app and Hono API.

  • 0216 files · 18 KB

    Hono

    Give your API typed routes, generated docs and a consistent error response before adding features.

  • 038 files · 8 KB

    Drizzle

    Keep your database schema typed and your SQL migrations checked in beside the code that needs them.

  • 042 files · 5 KB

    Better Auth with passkeys

    Keep accounts, organisations and passkey sign-in in your own Hono API and Postgres database.

  • 059 files · 10 KB

    TanStack

    Keep React routes, session checks and cached server data working from the same types.

  • 065 files · 5 KB

    Lefthook and Biome

    Check staged code at commit time and types before a push, including work written by your agents.