0.5.0 — A second stack: Next.js, Postgres and Prisma

A second stack: Next.js, Postgres and Prisma.

flare create --stack next builds an app on Next.js 16, Neon Postgres and
Prisma 7, from the same descriptors, with the same dashboard, the same
validators and the same policies. What changes is the schema, the migrations
and where it deploys. Choosing a stack compares them
properly, including what the Next.js one cannot do.

The resource store was split from its database access to make this possible:
one interface, about fifty lines, with a Drizzle implementation and a Prisma
one behind it. Everything a resource means stayed shared, which is why a
unique-constraint error says "Sku is already taken" on both.

A catalogue on Next.js builds one against a real
Postgres, with ranked full-text search and honest measurements — including
the case where the index is the slower choice.

---

pnpm add -D @flaredev/cli@0.5.0

19 commits by @MUKE-coder.
Full changelog · Compare