A modern CLI tool for scaffolding end-to-end type-safe TypeScript projects. It targets developers seeking to build full-stack applications with a highly customizable, minimal, and bloat-free approach, leveraging the latest stable dependencies. The primary benefit is enabling users to "roll their own stack" by selecting only necessary components, ensuring zero lock-in and promoting best practices.

How It Works

The CLI tool operates on a "choose your own adventure" philosophy, allowing granular selection of frontend frameworks, backend runtimes, APIs, databases, ORMs, and authentication solutions. It emphasizes end-to-end type safety across the stack and promotes a clean monorepo structure. This modular design minimizes boilerplate and ensures users integrate only the components they require, leading to leaner, more maintainable projects.

Quick Start & Requirements

Installation is straightforward using package managers:

• Recommended: bun create better-t-stack@latest
• pnpm create better-t-stack@latest
• npx create-better-t-stack@latest

Prerequisites include Node.js or Bun runtime. Full documentation, guides, and examples are available at better-t-stack.dev. A visual Stack Builder is also provided at https://better-t-stack.dev/new.

Highlighted Details

• Extensive support for diverse frontend (React, Next.js, Svelte, etc.), backend (Hono, Express, etc.), API (tRPC, oRPC), database (PostgreSQL, MongoDB, etc.), and ORM (Drizzle, Prisma, etc.) technologies.
• Integrates with modern tooling like Turborepo, Nx, Biome, Husky, and offers optional AI integration via a Claude Code plugin.
• Supports multiple runtimes including Bun, Node.js, and Cloudflare Workers, with deployment options for Cloudflare Workers.
• Features include end-to-end type safety, clean monorepo layouts, and zero lock-in by design.

Maintenance & Community

The project is structured as a monorepo containing the CLI, documentation website, and a Claude Code plugin. Contribution guidelines are available within the repository. While sponsors are mentioned, specific community channels (like Discord/Slack) or notable maintainer details are not provided in the README snippet.

Licensing & Compatibility

The license type is not explicitly stated in the provided README content. Therefore, compatibility for commercial use or closed-source linking cannot be determined without further information.

Limitations & Caveats

The primary limitation is the absence of a clearly stated open-source license, which is crucial for determining usage rights, especially for commercial applications. Further investigation into the repository's license file is recommended.