Registry / web-framework / koa-connect

koa-connect

JSON →
library2.1.1jsnpmunverified

koa-connect is a utility package that enables the integration of standard Connect or Express middleware into a Koa application. It acts as a bridge, adapting the `(req, res, next)` signature of Connect/Express middleware to Koa's `(ctx, next)` context-based middleware pattern. The current stable version is 2.1.1. While not actively undergoing rapid feature development, the package is in a maintenance state, receiving updates for compatibility and bug fixes as needed. It serves a niche purpose, primarily when a Koa-native version of a required middleware is unavailable or for library authors aiming for framework-agnostic HTTP middleware. Developers are strongly cautioned to prefer Koa-specific middleware when available due to fundamental design differences between Koa's async/await flow and Express's callback-based approach, which can lead to unexpected behavior and control flow issues.

web-frameworkhttp-networking
npm install koa-connect
github ↗package ↗
INSTALL
IMPORT
SIG · KOA-CONNECT
K
koa-connect
web-frameworkjavascriptv2.1.1
Install
—
Import
—
Disk
—
Pass rate
0/ 6
Env Coverage0 / 6
glibc
18–22
musl
18–22
Install & Compatibility
Where this runs
tested against v? · npm install
Install × environment matrix
Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux
musl
node 18–226 runs
build_error
glibc
node 18–226 runs
build_error
Code
Verified usage

Verified import paths — ran on the pinned version, not inferred.

c2k
✓ import c2k from 'koa-connect';
✗ const c2k = require('koa-connect');
ESM import for modern Node.js and bundlers. The package supports both ESM and CommonJS.
c2k
✓ const c2k = require('koa-connect');
CommonJS require for older Node.js environments. This is demonstrated in the quickstart.
MiddlewareAdapter
✓ import type { MiddlewareAdapter } from 'koa-connect';
Type import for TypeScript users to explicitly type the `c2k` function, although typically inferred.

Demonstrates how to integrate a standard Connect/Express-style middleware into a Koa application using `koa-connect`, illustrating the control flow between Koa and adapted middleware.

const Koa = require('koa'); const c2k = require('koa-connect'); // A generic Express-style middleware function function connectMiddleware(req, res, next) { res.writeHead(200, { 'Content-Type': 'text/plain' }); res.end('From the Connect middleware'); next(); // Crucial to call next to continue the Koa chain } // A basic Koa middleware to illustrate the flow async function koaGreetingMiddleware(ctx, next) { console.log('Koa middleware: Before calling next'); await next(); // Proceed to downstream middleware console.log('Koa middleware: After downstream middleware'); } const app = new Koa(); app.use(koaGreetingMiddleware); app.use(c2k(connectMiddleware)); // Integrate the Connect middleware // Final Koa middleware to show control flow continues app.use(async (ctx, next) => { if (ctx.path === '/') { ctx.body = ctx.body || 'Hello from Koa after Connect!'; } await next(); }); app.listen(3000, () => { console.log('Server running on http://localhost:3000'); });
Debug
Known issues
gotchaIt is highly recommended to use Koa-specific middleware instead of converting an Express version when Koa-native alternatives are available. Koa and Express have fundamentally different designs (async/await vs. callback-based), and `koa-connect` is a workaround, not a seamless replacement, which can lead to unexpected behavior and control flow issues.
fix
Prioritize `koa-*` packages. Only use `koa-connect` when a Koa-native solution is truly unavailable or for very simple, self-contained middleware.
affects: >=1.0.0
gotchaWhen adapting an Express-style middleware, you *must* explicitly declare and invoke the `next` callback parameter within the middleware function for the Koa chain to continue. Failure to call `next()` will halt the request processing at the adapted middleware.
fix
Ensure your Connect/Express middleware function signature is `(req, res, next)` and that `next()` is called at the appropriate point, typically at the end of the middleware's logic, to pass control to the next Koa middleware.
affects: >=1.0.0
gotchaWhen writing framework-agnostic middleware intended for use with `koa-connect`, avoid using Express-dependent APIs (e.g., `res.send()`, `req.params`, `req.body`) as these are not part of the standard Node.js `http` module and will not be available or function correctly within Koa's context.
fix
Restrict adapted middleware to using only core Node.js `http.IncomingMessage` (req) and `http.ServerResponse` (res) methods and properties, or properties explicitly added by other universal middleware.
affects: >=1.0.0
Errors
Common errors & fixes
TypeError: res.send is not a function
An Express-style middleware adapted by `koa-connect` is attempting to use `res.send()`, which is an Express-specific method and not available on the native Node.js `http.ServerResponse` object provided within Koa's context.
fix
Modify the Express middleware to use standard Node.js `res.end()` or `res.write()` methods, or ensure `ctx.body` is set in a subsequent Koa middleware after the adapted middleware has processed the request.
Request hangs indefinitely or subsequent Koa middleware are not executed.
The adapted Connect/Express middleware did not call the `next()` function, preventing the Koa middleware chain from proceeding to the next handler.
fix
Review the Connect/Express middleware's implementation and ensure `next()` is invoked correctly to pass control to the subsequent middleware in the Koa application.
Upgrade
Version history
2.1.1latest on npm
Audit
Dependencies

No dependency data recorded yet.

Agent activity
8 hits · last 30 days
node
8
Resources
githubhttps://github.com/vkurchatkin/koa-connect ↗
packagehttps://www.npmjs.com/package/koa-connect ↗
koa-connect — npm install koa-connect · libregistry