@routup/decorators

Define request handlers as classes with TypeScript decorators, then mount them on any routup router. Familiar shape if you're coming from NestJS, tsoa, or Spring — controllers, parameter injection, declarative paths.

The decorator metadata is also what @routup/swagger reads (via @routup/swagger-preset) to generate OpenAPI documents — so the same controller is both your routing surface and your API contract.

Installation

npm install @routup/decorators

The plugin requires TypeScript decorator metadata. In your tsconfig.json:

{
    "compilerOptions": {
        "experimentalDecorators": true,
        "emitDecoratorMetadata": true
    }
}

Quick start

// controller.ts
import { DController, DGet, DPath } from '@routup/decorators';

@DController('/users')
export class UserController {
    @DGet('')
    async list() {
        return [{ id: 1, name: 'Ada' }];
    }

    @DGet('/:id')
    async show(@DPath('id') id: string) {
        return { id: Number(id), name: 'Ada' };
    }
}

// app.ts
import { Router, serve } from 'routup';
import { decorators } from '@routup/decorators';
import { basic, readRequestBody, useRequestCookie, useRequestQuery } from '@routup/basic';
import { UserController } from './controller';

const router = new Router();

router.use(basic());
router.use(decorators({
    controllers: [UserController],
    parameter: {
        body: (ctx, name) => name ? readRequestBody(ctx.event, name) : readRequestBody(ctx.event),
        cookie: (ctx, name) => useRequestCookie(ctx.event, name as string),
        query: (ctx, name) => name ? useRequestQuery(ctx.event, name) : useRequestQuery(ctx.event),
    },
}));

serve(router, { port: 3000 });

When to use it

• You prefer class-based controllers to functional handler files
• You're generating OpenAPI from your controllers via @routup/swagger
• You're migrating a NestJS / tsoa / class-validator codebase and want a familiar shape

The plugin doesn't replace defineCoreHandler — it sits alongside it. You can mount decorator controllers and functional handlers on the same router.

See also

• Controllers — @DController, HTTP method decorators, async handlers, returning a Response
• Parameters — every parameter decorator with its parser-extractor wiring
• @routup/swagger — generate OpenAPI from your decorated controllers
• @routup/swagger-preset — the metadata preset that maps @DController / @DGet / @DBody to OpenAPI