Dependencies
ORPC
ORPC is the typed RPC layer Tulip apps use for app-local routers, procedures, and client calls.
ORPC provides the RPC foundation for Tulip app templates.
Tulip does not ship a global router. Each app owns its ORPC context, middleware, procedures, route handlers, and router composition.
Where Tulip uses ORPC
- app templates wire ORPC server and client setup
- Commands commonly call ORPC mutation options
- Inline editing calls ORPC mutation options
- Data Tables often load data through ORPC query options
- AI routes can stream through ORPC procedures
- Storage and Drive providers expose ORPC contracts in package-specific flows
What Tulip adds
Tulip adds conventions for pairing ORPC with TanStack Query, permissions, commands, inline editing, and table data loading.
The shared query client helpers live in @tulip-systems/query/tanstack-query.
What your app owns
- RPC context
- auth middleware
- permission middleware
- route handler path
- router modules and domain procedures