rpc

Vovk.ts RPC client

Every controller procedure with HTTP decorator automatically gets typed client counterpart. vovk generate produces these client modules from segment schemas, emitting TypeScript into the project:

• Composed client (default): one client for all segments at composedClient.outDir (default ./src/client, or ./client when the app isn't in src/app). Import from '@/client' (standard Next.js alias; alias-less projects use a relative path).
• Segmented client: per-segment subdirs of segmentedClient.outDir (same default dir). Import from '@/client/<segment>'.

Key identity: client module name = key used in initSegment's controllers map, regardless of import path.

// server
initSegment({ controllers: { UserRPC: UserController } });

// client (composed)
import { UserRPC } from '@/client';
await UserRPC.getUser({ params: { id: '42' } });

Not UserControllerRPC. Not UserController. Whatever the key is.

Generating client

npx vovk generate

What it does:

• Reads .vovk-schema/**/*.json for every segment (nested segments live in subdirectories, e.g. .vovk-schema/customer/static.json).
• Emits generated code into configured outDir using selected fromTemplates preset (default ['ts']).
• Composed client (default): emits index.ts, schema.ts, openapi.ts, openapi.json at outDir root (default ./src/client, or ./client when the app isn't in src/app). Project's own tsc handles the files; import from '@/client'.
• Segmented client: same four files per segment under <outDir>/<segment>/; import from '@/client/<segment>'.
• Generated dir is gitignored by vovk init and rebuilt by the prebuild script (vovk generate); no need to commit it.

See "Client layout and import paths" below.

vovk generate does NOT rebuild schemas from controller source. Schema emission = separate step: vovk dev runs alongside Next.js dev server, hits each segment's _schema_ endpoint (only available when NODE_ENV === 'development'), writes JSON into .vovk-schema/. vovk generate reads whatever's there.