Bun Patties

Most full-stack frameworks were designed in the Node era and carry its accumulated tooling tax: a bundler bolted on, a separate file watcher, a glob library, an HTTP layer wrapped around node:http. Each is a dependency to install, configure, keep in sync, and debug.

Bun changed the baseline. The runtime now ships an HTTP server (Bun.serve), a bundler (Bun.build), filesystem globbing (Bun.Glob), a test runner and hot reload — all native, all already there. Patties started from a simple question: what does a full-stack framework look like if you build it on those primitives instead of re-importing the Node-era stack on top of them?

What you get

• React 19 SSR over renderToReadableStream, served by Bun.serve.
• Route and island discovery done once at build time and inlined into the production bundle — the server never re-scans the disk at runtime.
• Handlers receive a standard Request and return a standard Response; the only added affordance is a thin PattiesContext.
• Deployment targets (bun, edge) behind adapters, not vendor lock-in.

Fewer dependencies, web-standard boundaries, and the speed of doing the expensive work at build time.

Packages

• patties — the meta-framework: React 19 SSR and filesystem routing on Bun.serve.
• create-patties — the official scaffolder: bunx create-patties my-app.
• patties-ui — an optional shadcn-compatible, copy-in component catalog stamped into your project by patties add.

bunx create-patties@latest my-app
cd my-app
bunx patties dev

Source on GitHub