hono-azurefunc-adapter

Azure Functions V4 adapter for Hono. Run Hono on Azure Functions.

Install

``bash
npm i @marplex/hono-azurefunc-adapter
`

Getting started

`typescript
//app.ts

import { Hono } from "hono";
const app = new Hono();

...

export default app
`

`typescript
//httpTrigger.ts

import honoApp from "./app";

import { azureHonoHandler } from "@marplex/hono-azurefunc-adapter";
import { app } from "@azure/functions";

app.http("httpTrigger", {
methods: [
"GET",
"POST",
"DELETE",
"HEAD",
"PATCH",
"PUT",
"OPTIONS",
"TRACE",
"CONNECT",
],
authLevel: "anonymous",
route: "{*proxy}",
handler: azureHonoHandler(honoApp.fetch),
});
`

Limitations

There are some limitations and other things you should keep in mind when running Hono inside Azure Functions.

$3

The default Azure Functions route prefix is /api. Be sure to start all your Hono routes with /api or change the default Azure Functions route prefix in host.json

`json
{
"extensions": {
"http": {
"routePrefix": ""
}
}
}
`

$3

In Node <=18 environments, if you are using hono/bearer-auth or any other library that uses crypto, be sure to define global.crypto = require("crypto"); before registering the http trigger.

$3

Azure Functions does not expose any signal or event for listening to http request interruptions. c.req.raw.signal` is useless and its never aborted.

Untested scenarios

- SSE (streaming response)