I do like the quick bootstrapping Remult offers via "JSON db" if one hasn't set up a DB yet. And entity classes defined as a .ts file is nice, as opposed to Prisma's DSL (e.g. schema.prisma file).
I see. Prisma does generate a FE client though (PrismaClient) that essentially can be dropped into NextJS API routes (or, more directly, used in the getServerSideProps method on a next js page). Thus its fairly integrated across the stack. (Not trying to jack this thread to peddle Prisma, just a longtime user of it and trying to find similarities).
It does seem feasible one could use Remult + Prisma + NextJS, with Prisma as Source of Truth of DB schema and Remult Source of Truth for Client side data model (although, that might go against the "define once, use anywhere" pattern laid out here).
Really like the project though, great docs and tutorial.
I do like the quick bootstrapping Remult offers via "JSON db" if one hasn't set up a DB yet. And entity classes defined as a .ts file is nice, as opposed to Prisma's DSL (e.g. schema.prisma file).