Client-Side
Code that runs in the user's web browser, including React components, event handlers, and UI rendering.
Detailed Explanation
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?
- Client-side errors show up in the browser console and Network Tab
- Server-side errors show up in Supabase logs and Edge Function logs
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
Start building software you actually own.
Learn the concepts, fix things with confidence, and ship real products with AI beside you. No coding background required, and we're with you from the first idea to launch.
Free to start. No card. Leave whenever you want.
- Free, from day one
- The Foundation courseShip your first real app in 8 weeks
- The communityBuild in public with people doing the same
- The glossary160+ terms in plain English