I have come up with two ideas: - split Prisma schemas between modules, joining them in the schema.prisma in the app using the framework - generate a unique Prisma client for each module, export the typings and merge them with the app’s Prisma client The other problem that I must think about is how to manage migrations for the framework’s modules. With the first solution, all migrations are in the app, as usual. With the second I think that framework’s migrations should be executed with a custom solution, complex but keeps things modularized. Has anyone done that kind of schema splitting? Suggestions?

@Codker 👋 Are these modules going to be in the same repository?

No, the framework with these modules will be bundled and used as a dependency of the apps

In that case, you can have Prisma Client in a repo of itself in the monorepo and reference it in other modules.