▲ 2 r/CLI

I built a CLI to scaffold Next.js monorepos with one command

I've been building and maintaining multiple web projects, and I kept running into the same problem: every new project required repeating a lot of setup work before I could focus on building the actual product.

So I built create-clubedge-app, a CLI that generates a Next.js monorepo from a versioned starter.

It includes a foundation for:

  • Next.js App Router and TypeScript
  • pnpm and Turborepo
  • PostgreSQL and Drizzle ORM
  • Supabase Auth
  • Testing, linting, and CI
  • Optional Redis-compatible caching and object storage integrations

One feature I particularly wanted was traceability. The generated project records the CLI version and starter reference, including the starter commit, so you can identify where it originated.

I've tested the published CLI by generating a project and running its type checks, tests, and production build.

I originally built this for my own development workflow, but I think it could be useful to other developers too.

I'd love honest feedback:

  • Would you use a starter like this for your own projects?
  • Is the included stack a useful starting point, or would you remove anything?
  • What would make you choose this over maintaining your own template?

Website: https://starter.clubedge.live

CLI source: https://github.com/Clubedge/create-clubedge-app

Starter source: https://github.com/Clubedge/clubedge-starter

I'm happy to answer questions about the architecture and implementation.

https://reddit.com/link/1x2bchu/video/gqi261o44muh1/player

reddit.com
u/PuzzleheadedWin5206 — 5 days ago
▲ 2 r/micro_saas+1 crossposts

I built a CLI to scaffold Next.js monorepos with one command

I kept finding myself repeating the same setup whenever I started a new Next.js project, so I decided to turn my usual workflow into a CLI.

It generates a monorepo with pnpm, Turborepo, Drizzle, PostgreSQL, Supabase Auth, and testing already wired up.

pnpm dlx u/clubedge/create-clubedge-app my-app

I also made the starter versioned so projects can be generated from a specific release.

It's still evolving, and I'd be interested in feedback from other developers: what do you usually include in your Next.js starter, and what would you do differently?

You can explore the project here:
CLI: https://github.com/Clubedge/create-clubedge-app
Starter: https://github.com/Clubedge/clubedge-starter
Website: https://starter.clubedge.live

u/Ok_Soil3082 — 5 days ago
▲ 8 r/coolgithubprojects+1 crossposts

I built a CLI to scaffold Next.js monorepos with one command

I've been building and maintaining multiple web projects, and I kept running into the same problem: every new project required repeating a lot of setup work before I could focus on building the actual product.

So I built create-clubedge-app, a CLI that generates a Next.js monorepo from a versioned starter.

It includes a foundation for:

  • Next.js App Router and TypeScript
  • pnpm and Turborepo
  • PostgreSQL and Drizzle ORM
  • Supabase Auth
  • Testing, linting, and CI
  • Optional Redis-compatible caching and object storage integrations

One feature I particularly wanted was traceability. The generated project records the CLI version and starter reference, including the starter commit, so you can identify where it originated.

I've tested the published CLI by generating a project and running its type checks, tests, and production build.

I originally built this for my own development workflow, but I think it could be useful to other developers too.

I'd love honest feedback:

  • Would you use a starter like this for your own projects?
  • Is the included stack a useful starting point, or would you remove anything?
  • What would make you choose this over maintaining your own template?

Website: https://starter.clubedge.live

CLI source: https://github.com/Clubedge/create-clubedge-app

Starter source: https://github.com/Clubedge/clubedge-starter

I'm happy to answer questions about the architecture and implementation.

u/PuzzleheadedWin5206 — 5 days ago