Most devs still fumble auth when using the App Router in Next.js.
- And I get it — juggling:
- API routes
- secure token handling
- and clean form validation with shadcn...
It’s easy to fall back on boilerplate or legacy auth flows that barely work.
That’s exactly the problem I hit when I tried integrating Better Auth with Prisma — using only the Next.js App Router (no pages directory, no hacks).
Here’s what I tackled:
🔐 Clean sign-
- up/login with email + password
- ✅ Form validation with shadcn/ui forms + Zod
- 📦 Full DB integration using Prisma
- 🧠 Session + token handling with middleware, not just cookie tricks
- 🧪 Safe actions via next-safe-action
All in one consistent auth system — no magic, no vendor lock-in.
If you're building a modern full-stack app with Next.js 15+ and want an auth system that’s secure, simple, and future-proof, I wrote up the guide here:
👇
App Router + Server Actions + Prisma
What would you add or do differently? Curious to see how others are handling auth.
Top comments (0)