decorators

Vovk.ts decorators

Decorators wrap static methods on controllers. Three kinds:

• HTTP decorators (@get, @post, @put, @patch, @del) — mark procedure as HTTP route. See procedure skill.
• Metadata decorators (@prefix, @operation) — attach info, no behavior change.
• Custom decorators (createDecorator) — middleware wrapping handler. How auth, logging, feature flags attach.

One syntax: @decorator. vovk init enables experimentalDecorators in tsconfig.json; a webpack build (next build --webpack, Next.js 15's default) needs it, Turbopack (Next.js 16's default) compiles vovk's decorators either way.

@prefix

Class-level route prefix:

import { prefix, get, procedure } from 'vovk';

@prefix('users')
export default class UserController {
  @get('{id}')
  static getUser = procedure({ /* ... */ }).handle(/* ... */);
}
// → GET /api/users/{id}

Root-level — @prefix('') or omit (same effect):

export default class RootController {
  @get()
  static ping = procedure().handle(() => ({ ok: true }));
}
// → GET /api

.auto() — name-derived routes

Use method name instead of path:

@put.auto()
static doSomething = procedure().handle(/* ... */);
// → PUT /api/<prefix>/do-something

Method names → kebab-case. Works with every HTTP decorator (@get.auto(), @post.auto(), etc.), same options.

HTTP decorator options

Second arg: response-header + CORS config.

@put('do-something', {
  headers: { 'x-hello': 'world' },
  cors: true,
})
static doSomething = procedure().handle(/* ... */);

• headers — merged into response.
• cors: true — permissive CORS for that route (access-control-allow-origin: *, preflight answered). Needs OPTIONS in segment's initSegment() exports — else Next.js answers the preflight itself (204 with Allow, no Access-Control-* headers), and the browser blocks the cross-origin call. Exact headers and CORS for every route → base.

Custom decorators — createDecorator