How w3barsi/senatoriables works
Project type and purpose
• This is a full-stack web application starter template (TanStarter) built on React 19 + React Compiler, TanStack Start (SSR framework) with Router & Query, Tailwind CSS + shadcn/ui for styling, Drizzle ORM for Postgres-based data persistence, and Better Auth for OAuth-based authentication.
• It provides an end-to-end example: file-based routing in src/routes, tRPC-powered APIs in src/server/trpc, and a client-side React app in src/client.tsx.
File structure
• Top-level:
• src/client.tsx, src/ssr.tsx → client & SSR entry points
• src/routes/ → TanStack file-based route definitions & UI components
• src/lib/ → shared client libs (auth, UI components, hooks, middleware, utils)
• src/server/ → tRPC router, auth setup, database init
• docker-compose.yml, .env.example, drizzle.config.ts → database and ORM configuration
• Key patterns:
• File-based routing → mapping URL ↔ React components
• RPC pattern (tRPC) → client & server share type-safe contract
• Layered architecture → UI → hooks → business logic → data access
README for architectural insights
• Confirms stack: React Compiler, TanStack Start (SSR + routing), TanStack Query (data fetching), Drizzle ORM → Postgres, Better Auth (OAuth).
• Mentions OAuth providers (GitHub, Google, Discord).
• Describes development scripts (pnpm dev, pnpm db push).
Main components and their interactions
a. Frontend (Browser)
• React Compiler-built UI
• TanStack Router handles client-side navigation (file routes → React pages)
• TanStack Query for data fetching & caching
• UI layer: shadcn/ui + Tailwind components (in src/lib/components)
• Hooks & middleware (e.g., use-media-query, auth-guard)
b. API layer (tRPC client/server)
• Client: src/lib/trpc/react.ts → useQuery / useMutation calls
• Server: src/server/trpc/init.ts, router.ts, routes/*.ts define RPC procedures
• Auth guard middleware wraps protected procedures
c. Backend & Persistence
• Drizzle ORM (drizzle.config.ts, src/types/db.ts) → Postgres via Docker
• Better Auth (src/server/auth.ts) → user/session management with external OAuth
d. External Services
• OAuth providers (GitHub, Google, Discord) for authentication
Architectural patterns & design principles
• Separation of concerns: UI, routing, data layer, authentication
• Type-safe end-to-end contracts via TypeScript + tRPC
• File-based routing → convention over configuration
• Middleware pattern for auth enforcement
• Infrastructure as code: Docker Compose for database