Managing Shared Drizzle Schemas in a Multi-Repo Next.js Setup
What's the best strategy to share Drizzle + BetterAuth schema definitions and related authentication code across four separate Next.js repositories, given that the auth code resides in one 'portal' repo and each of the three 'product' repos requires access to the user session & user fields, ideally minimizing redundant schema updates?
(all are on the same domain with different subdomains)
(all are on the same domain with different subdomains)
