Pre-1.0 — active development
Patties is under active development (currently 0.x). The framework API, CLI flags, config shape, and the UI catalog may change between releases — backward compatibility is not guaranteed until 1.0.0. Pin an exact version and review the release notes before upgrading.
Where the project stands
The framework runtime, scaffolder, and UI catalog are published and usable today. The modular-monolith convention is a design exploration in the specs, sequenced behind a pluggable-validation foundation.
Published packages
Fetched in your browser straight from registry.npmjs.org. A green Release run is not enough — presence here is confirmed against the live registry.
Fetching dist-tags from registry.npmjs.org…
| Package | Latest | Dist-tags | Last published |
|---|---|---|---|
| Loading… | |||
Fetching releases from api.github.com…
| Release | Tag | Published |
|---|---|---|
| Loading… | ||
Shipped capabilities
Bun-native runtime ✓ Shipped
Bun.serve · Bun.Glob · Bun.build · bun --hot
HTTP on Bun.serve, discovery on Bun.Glob, bundling on Bun.build, hot-reload on bun --hot — no Webpack, chokidar, or node:http wrapper. Framework overview →
Filesystem routing + React 19 SSR ✓ Shipped
app/routes/ → Bun route patterns · renderToReadableStream · islands
Routes compiled from the filesystem, React 19 streaming SSR, and opt-in client islands with on-demand hydration. Routing → · Rendering & islands →
Build-time discovery ✓ Shipped
discover once at build, inline into the bundle, serve frozen
Route + island discovery runs during build and is inlined; the production server never re-scans the disk. Integration tests gate it. Build pipeline →
CLI + adapters ✓ Shipped
patties dev / build / deploy / secret · bun + edge adapters
The full CLI plus deploy adapters for bun and edge, keeping platform specifics out of the core. CLI → · Adapters & targets →
create-patties scaffolder ✓ Shipped
project type · Patties UI · monorepo · deploy target · coding-agent overlays
A guided prompt flow that stamps a working app, optionally with Patties UI starter components and a container target, plus Claude/Codex skill overlays. Project scaffolding →
Patties UI catalog ✓ Shipped
60 shadcn-compatible, copy-in components · patties add
All 60 components ship; patties add <component> stamps source into app/components/ui/ — never a versioned dependency. React 19 style, Tailwind v4 + CSS variables.
Optional AI + plugins + AGENTS.md ✓ Shipped
agents/tools/jobs · plugin hooks · CLAUDE.md / AGENTS.md generation
Optional AI primitives (lazy @anthropic-ai/sdk), plugin hooks for build/dev/jobs, and a regenerated app inventory for coding agents. AI & agents → · Plugins → · AGENTS.md →
Roadmap
The next body of work is the modular-monolith design exploration: a thin convention where modules talk only through a published public index.ts, enforced by one build-time boundary check. It is sequenced behind a pluggable-validation foundation. Everything below is Draft today — specs written, no implementation issue opened yet.
Pluggable validation Spec 29 · Foundation
widen the AI-tool API from Zod to Standard Schema
Lands first. Retypes ToolConfig.input to StandardSchemaV1 so module templates ship validator-agnostic tools (Zod, Valibot, ArkType) written once instead of migrated later. Spec 29 →
Modular-monolith convention Spec 28 · Planned
modulesDirs · per-module routes/islands/agents-md · public-API boundary
Adds an optional modulesDirs so the router scans module subdirectories, the island scanner emits module-prefixed keys, and the manifest groups by module — flat layout unchanged when absent. Spec 28 →
create-patties — modular by default CLI Spec 21 · Planned
drop --type · modular default template · module-first agent overlays
Rewrites the default template as a modular layout (modules/home/ + modules/api/), pre-fills modulesDirs, and authors AI module tools against Standard Schema. CLI Spec 21 →
Delivery epics E1–E3 · Planned
- E1Convention & boundary — module folder layout + build-time public-API import check. Epic 01
- E2Route discovery macro —
Bun.Globmerges each module's routes into one frozenBun.servetable. Epic 02 - E3Starter · docs · release —
--template modularscaffold, docs, and a minor release verified on npm. Epic 03
Design specs & status
The design specifications are the source of truth for why the framework is shaped the way it is. ● Live describes shipped behaviour; ○ Draft is a proposed convention not yet implemented.
| Specification | Scope | Status |
|---|---|---|
| Overview & index | The thesis: a modular monolith on Bun-native primitives | ○ Draft |
| Using Patties | create-patties, the framework + CLI, Patties UI | ● Live |
| Architecture | Layer model, build-time discovery, deploy artifact | ● Live |
| Features | Modules & boundary, data ownership, graph checker, UI | ○ Draft |
| Frontend & UI stack | The full frontend/UI layer breakdown | ● Live |
| Decision records | ADRs: folders-not-classes, no DI, the boundary check | ○ Draft |
| Delivery tracker | Filterable epics / specs / tasks with status | ◐ Tracking |
| Spec 29 — Pluggable validation | Standard Schema for AI tools (foundation) | ○ Draft |
| Spec 28 — Modular monolith | The modulesDirs convention | ○ Draft |
| Spec 21 — create-patties | Modular-by-default scaffolding | ○ Draft |
Browse the full specification archive
The table above is the curated set. The complete agent_specs/ archive — every framework, CLI, and UI spec, plus all accepted, backlog, and deferred RFCs and the raw research notes — is browsable in full.
How releases ship
Versions are managed with Changesets. Each package (patties, create-patties, patties-ui) is versioned and published to npm independently; GitHub Releases mirror the notes. Pre-release work ships on the next dist-tag.