What I mean by problem is the issue to organize not related/different code on the same library. Indeed Supabase.UI is the most debatable one as it depends on a whole different project configuration for assets and components. But what is the division line?
As Supabase don’t have so much APIs as AWS, it seems fair to accept drawbacks from implementing all of them as a monorepo, but I would like to confirm this idea from experiences of other people.
