Overview
Use your generated AppConfig from the browser or another service with the typed client, TanStack Query helpers, and realtime subscriptions.
The client layer consumes the API that codegen derives from your server files. Create one typed client, pass it to the TanStack Query option builders when you use React, and turn on realtime when a screen should update as data changes.
Pages
| Page | What it covers |
|---|---|
| Client SDK | createClient<AppConfig>(), collection/global CRUD, routes, uploads, search, errors, and adapter-specific mounts. |
| TanStack Query | Query and mutation option builders for collections, globals, routes, and realtime-backed reads. |
| Realtime | Live collection and global queries over one multiplexed connection. |
Related
- Getting Started - create your first generated
AppConfig. - Adapters - Realtime - configure the server-side transport behind live queries.
- Concepts - Collections - define the data model the client consumes.
Environment
Declare your environment variables once with a Standard Schema, and QUESTPIE validates them at boot, types `env.*` end to end, and splits server secrets from client-public vars across every bundler, so a misconfigured deploy fails before it starts, not at the first request.
Client SDK
A fully typed client for your app's API, call createClient once with your generated AppConfig and get inferred CRUD, globals, custom routes, search, file uploads, and live realtime queries, all derived from your server schema.