Also, had the displeasure of using Prisma a while back. Extremely slow type generation, and complex to work with its client-server architecture. When your library requires a separate process you know you messed up.
If you want to just ship, pick up Next.js, or whatever you already know and add dependencies when you need them. Let thought leaders thought lead.
I'm searching for SQL typescript tooling for my next project.
I use prisma, and then when it becomes too complex, or is annoying, switch to sql.
Sometimes I don’t want to have to manually deserialize rows into my objects (and yes, orms do this for us, and some non-orms do too).
And that’s how you end with the 10 tools you started your comment with.
You can’t “just” start with next if you need authentication, translations, database acces, validations, csrf and other security protections, background jobs, permissions and a lot of other things that anything more complicated than a hello world will need.
If you want to just ship (anything more complicated than a landing page), start with Rails or Laravel.
Prisma is generating the Kysely type definitions automatically so it is still pretty hands off without the production overhead of prisma server/client.