Jean-Francois 'Jeff' Moy

· 1 min read

Extra robustness in your Koa projects with Typescript

With a bit of Typescript magic, it is possible to add strict typing to the body of Koa requests and responses.

Typescript and Koa users know how loose the Typescript typing is for the requests and responses of the Koa contexts. Indeed, Koa (and Koa-Body) default types use any for the request and response body type.

This short blog post will show how you can add more robustness to your controllers by typing your bodies thanks to a simple generic interface.

Sparkling Koa with Genericity

We want to be able to provide the types of the request and the response body, whilst keeping the built-in flexibility. That's easy to achieve with Typescript generics as demonstrated below:

import { Context, Request } from 'koa';

interface KoaRequest<RequestBody = any> extends Request {
    body?: RequestBody;

export interface KoaContext<RequestBody = any, ResponseBody = any> extends Context {
    request: KoaRequest<RequestBody>;
    body: ResponseBody;

export interface KoaResponseContext<ResponseBody> extends KoaContext<any, ResponseBody> {}

Having typed bodies should not prevent you from runtime checking the request bodies to ensure that you were provided with a valid input. If you are composing middlewares, you probably runtime check up the chain, and having typed bodies downstream where you know the input has been validated prevents you from duplicating the checks.

For assembling responses, having type safety at the compiler level should prove enough.

I am actually surprised that those are not the original type definitions in @types/koa and @types/koa-body but I am sure they had their reasons.


Let's put our new interfaces in practice with a couple of examples.

import Router from 'koa-router';
import koaBody from 'koa-body';

interface HelloWorldRequestDto {
    name: string;

interface HelloWorldResponseDto {
    message: string;

const helloRouter = new Router();'/', koaBody(), async (ctx: KoaContext<HelloWorldRequestDto, HelloWorldResponseDto>) => {
    // Request body is now typed.
    const { name } = ctx.res.body;
    ctx.res.statusCode = 200;
    // Response body is also typed.
    ctx.body = {
        message: `Hello ${name}!`,

The compiler will error if we try to access properties not defined in the body types. Using the same DTO types, the code below would not compile:'/', koaBody(), async (ctx: KoaContext<HelloWorldRequestDto, HelloWorldResponseDto>) => {
    // The compiler will fail as lastName is not defined in `HelloWorldRequestDto`.
    const { name, lastName } = ctx.res.body;
    ctx.res.statusCode = 200;
    // The compiler would also fail here because we are defining a property absent from `HelloWorldResponseDto`, and `message` is absent.
    ctx.body = {
        msg: `Hello ${name}!`,

The KoaContext interface uses default value for the generics; this allows specifying the request body type without the response's: KoaContext<RequestBodyType> will assume that the response body type is any. The KoaResponseContext allows you to specify the response body type without the request's for extra convenience.


Leveraging Typescript and generics, we were able to add stricter typing to Koa. This should help you when composing middlewares, and assembling your response bodies. Happy coding!

You can comment on this article on HackerNews or Lobsters.