koa-micro-ts
v6.0.1
Published
Microservice Typescript Framework - based on koa
Maintainers
Readme
koa-micro-ts
Microservice framework based on koa
_ _ _
| | _____ __ _ _ __ ___ (_) ___ _ __ ___ | |_ ___
| |/ / _ \ / _` |_____| '_ ` _ \| |/ __| '__/ _ \ _____| __/ __|
| < (_) | (_| |_____| | | | | | | (__| | | (_) |_____| |_\__ \
|_|\_\___/ \__,_| |_| |_| |_|_|\___|_| \___/ \__|___/
Koa TypeScript Microservice Framework - batteries includedQuick 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
autoRouteendpoints - 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/router15 (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 ...) staris now a regular token likedetail: 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 throughautoRoutealone — with API doc and automaticjwt.middleware(). Only export names are affected: astardirectory still maps to a literal/starsegment- The matched remainder is no longer an unnamed index param: use
ctx.params.pathinstead ofctx.params[0]. It isundefined(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 theirjwt.middleware()never runs — see AUTOROUTES.md
Version 5 - Breaking Changes
- Dependencies: koa 3
- minimal node version: node V18
- CORS: default
credentials: true→false - CORS: the default
originis now*instead of reflecting the request origin.originadditionally accepts an array (allowlist) or a function(ctx) => origin - CORS:
credentials: truenow requires an explicitly configuredorigin(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 genericInternal Server Errorin production. Full details are still logged and returned in development mode (app.development) or when the error setsexpose: true(Koa convention, e.g.ctx.throw) — see CATCHERRORS.md- JWT middleware:
ctx.jwtnow contains only the verified token payload (previously the unverified decoded token was set before verification). The payload is also available asctx.state.user - SPA fallback (
apiHistoryFallback()): the Accept header check was fixed — requests acceptingtext/htmlor*/*get the fallback (previously both were required, so plain browser requests could miss the fallback) - request stats:
pathCountsis capped at 1000 distinct paths, further paths are aggregated under(other) validators.sanitize()andvalidators.stripAll()are deprecated — they are not a reliable defense against injection, use parameterized queries and output encoding instead
Upgrading from v4
- Make sure you run Node 18 or later, then update the package:
npm install koa-micro-ts@5. - CORS with cookies/credentials: if you call
app.cors({ credentials: true })without an explicitorigin, browsers will now be denied. Configure your allowed origins explicitly:
If you relied on the old reflect-any-origin behavior and really want it (not recommended), passapp.cors({ origin: ["https://app.example.com"], credentials: true, });origin: (ctx) => ctx.get('Origin'). - Error responses: if clients parse error details from 5xx responses,
either throw with
expose: true/ usectx.throw(...), or handle those errors in your own middleware beforecatchErrors(). - JWT: if you read
ctx.jwtfor tokens that fail verification — that is no longer possible; handlers behindjwt.middleware()only ever see verified payloads.ctx.state.usernow works as documented. - 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-tsUsage
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 exampleNow try the following routes in your browser:
Static Page:
http://localhost:3000/
Standard Routes
http://localhost:3000/routehttp://localhost:3000/route2
Health Routes
http://localhost:3000/livenesshttp://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 
The
MITLicense (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.
