The ClientOnly component wraps content that should only render on the client side, preventing server-side rendering hydration mismatches.

You can provide a fallback prop to display content during server-side rendering or before client hydration completes.

Common scenarios where ClientOnly is useful:

• Accessing browser-only APIs (localStorage, window, document)
• Rendering components that depend on client-side state
• Preventing hydration mismatches with dynamic content
• Lazy-loading heavy components only on the client