npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

koa-micro-ts

v6.0.1

Published

Microservice Typescript Framework - based on koa

Readme

koa-micro-ts

Microservice framework based on koa

   _                               _                      _
  | | _____   __ _       _ __ ___ (_) ___ _ __ ___       | |_ ___
  | |/ / _ \ / _` |_____| '_ ` _ \| |/ __| '__/ _ \ _____| __/ __|
  |   < (_) | (_| |_____| | | | | | | (__| | | (_) |_____| |_\__ \
  |_|\_\___/ \__,_|     |_| |_| |_|_|\___|_|  \___/       \__|___/

     Koa TypeScript Microservice Framework - batteries included

NPM Version NPM Downloads Git Issues Closed Issues Caretaker MIT license

Quick Start

This package provides a minimalistic, simple to use, koa based micro service template. A few common used middleware packages are already included. To keep it small as possible, we added some own tiny libraries like CORS, JWT-wrapper, auto routes, logger, validators, APIdoc, API-History Fallback. Included middleware/libs:

  • body parser (now configurable since version 3) - detailed docs for all bodyparser options BODYPARSER.md
  • basic router
  • auto router - smart directory based auto-generation of routes - detailed docs AUTOROUTES.md
  • CORS - detailed docs CORS.md
  • JWT - detailed docs JWT.md
  • static files serving - detailed docs STATIC.md
  • API history fallback functionality APIFALLBACK.md
  • validators - detailed docs VALIDATORS.md
  • health API endpoint - detailed docs HEALTH.md
  • graceful shutdown - detailed docs SHUTDOWN.md
  • logger - detailed docs LOGGER.md
  • parsing command line arguments - detailed docs ARGS.md
  • dev/production mode detection - see below in this README.md
  • catch errors - detailed docs CATCHERRORS.md
  • request stats - detailed docs REQUESTSTATS.md
  • integrated API doc - auto-generated for all autoRoute endpoints - detailed docs APIDOC.md

Most of these modules can be enabled with just one line of code. Configuration is super simple and lets you create your micro service within minutes.

New Release 5

Version 5 is a security-hardening release. Based on a full security audit, several unsafe defaults were fixed: the built-in CORS middleware no longer reflects arbitrary request origins, error responses no longer leak internal details in production, the JWT middleware only exposes verified token payloads, the generated API doc page is HTML-escaped and request stats can no longer grow memory unbounded. It also moves to koa 3 and Node 18+. Most apps run unchanged — see the breaking changes and the upgrade path below.

Version 6 - Breaking Changes

  • Dependencies: @koa/router 15 (path-to-regexp 8)
  • Wildcard routes (exports.star) now generate a named wildcard {/*path} instead of a bare /*. A bare * is rejected by path-to-regexp 8 and threw on route registration (Missing parameter name at index ...)
  • star is now a regular token like detail: it works for every method and at any position in the export name (post_star, put_detail_star, delete_star, …), so a path-based resource API can be expressed through autoRoute alone — with API doc and automatic jwt.middleware(). Only export names are affected: a star directory still maps to a literal /star segment
  • The matched remainder is no longer an unnamed index param: use ctx.params.path instead of ctx.params[0]. It is undefined (not '') when nothing follows the base, so default it when you post-process it

Before (v5):

// routes/wikis/index.route.ts  →  GET /api/v1/wikis/*
exports.star = async (ctx: any, next: any) => {
  const rest = ctx.params[0];           // 'pages/intro', '' at the base
  ctx.body = { segments: rest.split('/') };
};

After (v6):

// routes/wikis/index.route.ts  →  GET /api/v1/wikis{/*path}
exports.star = async (ctx: any, next: any) => {
  const rest = ctx.params.path ?? '';   // 'pages/intro', undefined at the base
  ctx.body = { segments: rest.split('/') };
};

Routes you register manually via newRouter()/useRouter() follow the same rule: replace router.get('/files/*', ...) with router.get('/files{/*path}', ...).

  • autoRoute() now logs a warning when it registers a route below an already registered wildcard of the same method. That combination is a silent authorization hole: a public wildcard swallows authenticated routes mounted at the same prefix afterwards, so their jwt.middleware() never runs — see AUTOROUTES.md

Version 5 - Breaking Changes

  • Dependencies: koa 3
  • minimal node version: node V18
  • CORS: default credentials: truefalse
  • CORS: the default origin is now * instead of reflecting the request origin. origin additionally accepts an array (allowlist) or a function (ctx) => origin
  • CORS: credentials: true now requires an explicitly configured origin (string, allowlist array or function). Without it, CORS headers are omitted instead of reflecting the request origin — see CORS.md
  • catchErrors(): 5xx responses only contain a generic Internal Server Error in production. Full details are still logged and returned in development mode (app.development) or when the error sets expose: true (Koa convention, e.g. ctx.throw) — see CATCHERRORS.md
  • JWT middleware: ctx.jwt now contains only the verified token payload (previously the unverified decoded token was set before verification). The payload is also available as ctx.state.user
  • SPA fallback (apiHistoryFallback()): the Accept header check was fixed — requests accepting text/html or */* get the fallback (previously both were required, so plain browser requests could miss the fallback)
  • request stats: pathCounts is capped at 1000 distinct paths, further paths are aggregated under (other)
  • validators.sanitize() and validators.stripAll() are deprecated — they are not a reliable defense against injection, use parameterized queries and output encoding instead

Upgrading from v4

  1. Make sure you run Node 18 or later, then update the package: npm install koa-micro-ts@5.
  2. CORS with cookies/credentials: if you call app.cors({ credentials: true }) without an explicit origin, browsers will now be denied. Configure your allowed origins explicitly:
    app.cors({
      origin: ["https://app.example.com"],
      credentials: true,
    });
    If you relied on the old reflect-any-origin behavior and really want it (not recommended), pass origin: (ctx) => ctx.get('Origin').
  3. Error responses: if clients parse error details from 5xx responses, either throw with expose: true / use ctx.throw(...), or handle those errors in your own middleware before catchErrors().
  4. JWT: if you read ctx.jwt for tokens that fail verification — that is no longer possible; handlers behind jwt.middleware() only ever see verified payloads. ctx.state.user now works as documented.
  5. Optional hardening: protect the stats and API doc endpoints with JWT (app.stats('/stats', true), app.apiDocAuth = true) and set body parser limits (jsonLimit, formLimit, formidable.maxFileSize) — see REQUESTSTATS.md, APIDOC.md, BODYPARSER.md.

Version 4 - Breaking Change

app.autoRoute() is now an async function.

So you need to call it within an async/await block ... here an example:

const main = async () => {
  await app.autoRoute(path.join(__dirname, '/routes'), '/api/v1');
  ...
  app.start(3000);
}

main()

Version 3 - Breaking Change

app.bodyParser() needs to be called now. Please call this before adding any routes. This has a configuration object, detailed documentation on body parser options can be found here BODYPARSER.md

app.bodyParser({ multipart: true })

Installation

$ npm install koa-micro-ts

Usage

Here is an example how you can use koa-micro-ts. Depending on your use case most of the things here are optional and only required if you want to use them:

import { app, Application } from "koa-micro-ts";
import { join } from "path";

// setting variables only for demo purposes.
// You can set this as environment variables
process.env.APP_NAME = "micro-service";
process.env.VERSION = "1.0.0";

// enable body parser (with desired options)
app.bodyParser({ multipart: true });

// enable helpth endpoint (defaults to  tow endpoints /live and /ready)
app.health();

// enable helmet (optional)
app.helmet();

// enable cors (optional)
app.cors();

// parse command line params (optional)
app.parseArgs();

// catch uncatched errors - must be 'used' before adding routes
app.catchErrors();

// set up static server (optional)
app.static(join(__dirname, "/public"));

// using router
const router: any = app.newRouter();

router.get("/route", (ctx: Application.Context, next: Application.Next) => {
  ctx.body = "OK from static route";
});

app.useRouter(router);

// enable gracefull shutdown (optional)
app.gracefulShutdown();

app.ready = true; // /health /ready endpoint now returns true
app.start(3000);

Have a look at the function reference APP.md for all options

Auto-Routes

This is one of the smart features of this package:

autoRoute allows you to just write your API endpoints and place them into a directory structure. When calling await app.autoRoute(...directory..., mountpoint), this directory will be parsed recursivly and all TypeScript files with extension .route.ts are added as routes. All routes then will be mounted to the given mountpoint. Your API structure then matches exactly your directory structure. This makes writing and maintaining your API endpoints super simple.

Detailed docs with examples can be found here: AUTOROUTES.md

Dev / Production Mode

The app instance has a development property that is set to true when providing a --dev or --development argument during startup or if the environment variable DEVELOPMENT exists.

You can use this property e.g. like this:

if (app.development) {
  ...
}

Examples

The example in the path examples shows how to use koa-micro-ts and

  • enable health endpoint
  • enable helmet
  • enable cors
  • serving static pages
  • using standard router
  • using auto routes

Building Example App

git clone https://github.com/sebhildebrandt/koa-micro.git
cd koa-micro
npm install
npm run build-example
npm run example

Now try the following routes in your browser:

Static Page:

  • http://localhost:3000/

Standard Routes

  • http://localhost:3000/route
  • http://localhost:3000/route2

Health Routes

  • http://localhost:3000/liveness
  • http://localhost:3000/readyness

Routes from autoRouter

  • http://localhost:3000/api/v1/
  • http://localhost:3000/api/v1/hello/
  • http://localhost:3000/api/v1/error/
  • http://localhost:3000/api/v1/resource/?param=value

Advanced usage

As koa-micro-ts uses some external packages, you can also refer to the documentation of the used packages to see their options:

License MIT license

The MIT License (MIT)

Copyright © 2026 Sebastian Hildebrandt, +innovations.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Further details see LICENSE file.