There seems no issue with your code example, it shouldnt have an hydration error since same data is present/render in both server and client side from what I can see. Nevertheless, I would suggest you following this guide of how setting up a global prisma client, where you dont need to disconnect after querying something. Also from a React standpoint, I dont see a good use case for having the Email component so far, you could just use the li element in the page.tsx file, to avoid prop drilling and so.

Try making these changes and see if it still happens. If so, please share an image of the hydration error instead of your explanation. Hope it helped😁