ORPC

We use the RPC version of ORPC. https://orpc.dev/docs/getting-started

Files

• src/server/handler.ts - ORPC RPC handler with error logging
• src/server/index.ts - ORPC middleware (baseOs, withUserOs, withoutUserOs)
• src/server/routes/index.ts - ORPC route definitions (currently empty)
• src/server/client/index.ts - Isomorphic ORPC client (server/client)
• src/server/utils/get-session.ts - Cached session getter

Routing

All routes be properly organized in src/server/routes. The file path should always match the RPC path. Every RPC function should be a folder containing an index.ts. Every sub-folder should also contain an index.ts which reexports the scoped routes.

ts
1// src/server/routes/posts/list/index.ts
2export const list = withUserOs.handler();
3
4// src/server/routes/posts/index.ts
5import { list } from "./list";
6
7export const postsRoutes = {
8  list,
9};
10
11// src/server/routes/index.ts
12import { postsRoutes } from "./posts";
13
14export const routes = {
15  posts: postsRoutes,
16};

Functions

ALWAYS use one of the os variables defined in src/server/index.ts depending on the data you need. If there is recurring logic consider update the existing os to deduplicate that work or create a new one. For example if you have a concept of organizations, consider making an export const withOrganizationOs = withUserOs.use(withOrganizationMiddleware);