Use existing web application frameworks in serverless environments
npm install serverless-httpThis module allows you to 'wrap' your API for serverless use. No HTTP server, no ports or sockets. Just your code in the same execution pipeline you are already familiar with.
Note: v4.0.0 doesn't intentionally intorudce any breaking changes, but uses a PassThrough stream internally instead of a stub - however, this is a sensitive area, so in order to avoid unintentional breaks, a semver major version was used. You should hopefully not have to change anything, but test thoroughly please.
Thank you to Upstash for reaching out to sponsor this project!
![]() Upstash: Serverless Database for Redis
Start for free in 30 seconds! |
* Node (http.createServer)
* Connect
* Express
* Koa
* Restana
Sails
Hapi
Fastify
Restify
Polka
Loopback
* AWS
* Genezio
* Azure (Experimental, untested, probably outdated)

Please check the examples folder!
``javascript
const serverless = require('serverless-http');
const Koa = require('koa'); // or any supported framework
const app = new Koa();
app.use(/ register your middleware as normal /);
// this is it!
module.exports.handler = serverless(app);
// or as a promise
const handler = serverless(app);
module.exports.handler = async (event, context) => {
// you can do other things here
const result = await handler(event, context);
// and here
return result;
};
`
`javascript
const serverless = require('serverless-http');
const express = require('express');
const app = express();
app.use(/ register your middleware as normal /);
const handler = serverless(app, { provider: 'azure' });
module.exports.funcName = async (context, req) => {
context.res = await handler(context, req);
}
``
Your code is running in a serverless environment. You cannot rely on your server being 'up' in the sense that you can/should not use in-memory sessions, web sockets, etc. You are also subject to provider specific restrictions on request/response size, duration, etc.
> Think of this as a familiar way of expressing your app logic, not trying to make serverless do something it cannot.
Pull requests are welcome! Especially test scenarios for different situations and configurations.
Here are some more detailed examples and advanced configuration options as well as provider-specific documentation