Show HN: Typebase – A single-folder back end you write in TypeScript

Post by SifatAhmed » Sun, Aug 30, 2026, 4:12 AM UTC

optimisticedits wrote: post #8

SifatAhmed wrote: post #6

This looks great. Question specifically on the Cloudflare Workers target: when you deploy there, does Typebase use D1 for the DB, or does the Postgres/Neon backend stay the same regardless of which server target you pick (Vercel/Workers/Deno) - i.e. is the DB layer decoupled from the server runtime, or does choosing Workers also mean choosing D1? I ask because I've shipped a small Workers+D1 service and the main fric…

I see no code there to automatically pick D1 for the DB when you deploy to Cloudflare. On Cloudflare, it should use the `@neondatabase/serverless` driver configured here https://github.com/typebase-io/monorepo/blob/fa3af0b71126caa...

Post by hirako2000 » Sun, Aug 30, 2026, 4:35 AM UTC

chrysoprace wrote: post #29

apsurd wrote: post #15

Earlier quoted context omitted.

that’s likely the promise but it’s so confusing and high cognitive overhead to maintain that backend frontend relationship. ‘use client’ - i think the special sauce for why people use nextjs is all frontend based. the frontend that comes from the backend. nextjs dx is a special kind of hell. disclaimer: im just a simple rails guy.

Next.js is a poor choice for a client-side application. It is first and foremost a server-side framework, and trying to force it to be client-side is to work against it. There are so many better options than Next.js for dedicated client-side front-ends.