Architecture map
How the repo is organized
Click systems in the graph to inspect responsibilities, important files, and nearby dependencies.
Architecture map
Use this map to orient around systems, dependencies, and files worth reading first.
Click a system in the map
Explore supabase/supabase-js by selecting services, gateways, clients, and data stores. Each node shows the files, responsibilities, and neighboring systems an agent should keep in scope.
Pan, zoom, and use the minimap to keep large repos navigable.
Sign up to turn selected graph context into repo-aware agent sessions.
Key systems
What an agent should understand first
Browser, Node.js, React Native, or edge runtime consuming the SDK
Main coordinator orchestrating all SDK services; manages initialization and token refresh
Session management, JWT token refresh, MFA, password reset, OAuth flows
Type-safe SQL query builder; generates REST API calls with RLS support
WebSocket-based subscriptions to database changes and presence tracking
S3-compatible file upload, download, deletion, and vector storage operations
HTTP client for invoking serverless functions with automatic auth token injection
W3C Trace Context propagation for OpenTelemetry; optional observability integration
Evidence coverage
What this context is grounded in
Coverage
- Citations
- 11
- Findings
- 5
- Files discovered
- 494
- Architecture systems
- 13
- Architecture relationships
- 14
- Agent graph
- Agent graph entities
- 846
- Agent graph relationships
- 1,252