Bun-powered product starter

Honolulu

Opinionated Bun monorepo: Hono API, Drizzle on Postgres, React/Vite frontend, shared Valibot schemas, and Vitest. Optional Supabase.

BunHonoDrizzlePostgresReactViteValibotVitest

Live demo Source code Discuss this work

Honolulu starter: your code in paradise. Bun, Hono, React, Drizzle. — Bun-powered product starter

Problem

Greenfield products burn weeks on config before shipping a first feature.

Architecture

Product flow

Scaffold with the CLI, pick defaults, push schema, and start from a typed todos sample instead of empty config week.

My responsibility

I designed and shipped the monorepo starter: API shape, ORM defaults, web app wiring, shared validation, and CI-friendly tests, including the public create flow via `bun create honolulu`.

Decision

Keep the stack thin and typed: Bun workspaces, Hono routes, Drizzle on Postgres, shared Valibot schemas, Vitest, and a React/Vite app, instead of a heavier framework pile.

What could fail

Scaffold drift, weak defaults that force rework before the first feature, and a starter that looks complete but fails under real API and auth work.

How I made it reliable

Modular Hono routes, shared Valibot validation before the DB, Vitest in CI, and a public API demo at honolulu-api.vercel.app to smoke-check the scaffold after create.

Result

Reusable lightweight stack with a public API demo at honolulu-api.vercel.app.