Backend Topology
Esta página aún no está disponible en tu idioma.
init supports three backend shapes. A scaffolded project does not require all three backend shapes.
TanStack Start
apps/app is independently full-stack. Its server routes and functions provide the
smallest backend option when a scaffolded project only needs the web application. They do not
require apps/api.
Hono API
apps/api is an optional Hono service. It runs on Bun and exposes Hono RPC and tRPC
clients from apps/api/src/client.ts. Application workspaces can import only this file
from another application workspace. It also contains the authenticated Files SDK gateway.
Run the local connect-backend template command to connect client application workspaces. The
template command owns adapter seams and environment wiring. Application workspaces never import source
from apps/api outside the exported client contract.
Convex
packages/backend is an optional Convex backend with API types that Convex generates and
a React client. It exists in packages/ because application workspaces consume it as a
workspace library. It deploys independently to Convex.
Run the local connect-backend template command to add the client provider and authentication
wiring to supported application workspaces. When you select Convex, you explicitly select
a workspace and a hosted service.
Local defaults
The default application core runs without a hosted account. Local service dependencies
use infra/local/docker-compose.yml. Optional backend workspaces and client adapters
must remain removable. Their removal must not leave imports, environment requirements, or
build failures.