Issue: MUI v7 CircularProgress was causing hydration mismatch warnings due to different CSS class names between server and client renders. Solution: Only render the MUI loading component on the client side using isClient state flag. This prevents SSR hydration issues while maintaining the same functionality. Changes: - Added useState to track client-side rendering - Conditionally render CircularProgress only on client - Server now renders null for loading state (no hydration mismatch)
1.3 KiB
1.3 KiB