Code that runs in the user's web browser, including React components, event handlers, and UI rendering.
Client-side means code that runs in the user's web browser — on their computer, not on a server. In your app, React components, hooks like useLoaderData and useActionData, JSX, CSS, and event handlers are all client-side.
The opposite is server-side — code that runs on Supabase's servers, like Edge Functions, RLS policies, and database queries.
The client-server split in your app:
| Client-Side (Browser) | Server-Side (Supabase) | |---|---| | React components | Database queries | | Forms & UI | Edge Functions | | useLoaderData, useActionData | RLS Policies | | Browser console | Supabase Logs | | DevTools & Network Tab | Supabase Dashboard |
Why this matters for debugging:
When something breaks, the first question is: where does it break? Client-side or server-side?
If the Network Tab shows a 200 status but empty data, the problem is server-side (RLS). If the console shows a TypeError, the problem is client-side (your component code).
Related: Frontend, React, Component, Server, Backend, Edge Function, Console (Browser), Network Tab, DevTools
We give you the skills to build, deploy, and own a full product. Professional stack, AI co-pilot, no coding background required.