Discussing the Hono Middleware for Azure Functions Custom Handler (on Nammatham v3)

[mildronize]

Dear all who developing Hono Framework, I've quiet new in Hono, I would like to dicuss the design middleware or has alternative for more cleaner code and type-safety

During design and developing Nammatham v3 (Azure Functions Framework), I've heard the good news the that's the Hono support Azure Functions.

However, that Hono adapter for Azure Functions based on the official Azure Functions v4 which same idea behind the Nammatham v2.

The major problem of the official Azure Functions v4 is it cannot be bundled and cannot use with the monorepo
Azure/azure-functions-nodejs-library#201, with Azure Custom Handler I can build, bundling with monorepo and deploy successfully.

So, I've design the Hono Middleware for Azure Functions
see summary design below (which support type infer from Hono):

import { Hono } from 'hono';
import { logger } from 'hono/logger';
import { FunctionTrigger } from 'nammatham';

// DO NOT SET `basePath` for Hono App, Azure Functions will handle it
const app = new Hono();
app.use(logger());

const trigger = new FunctionTrigger();

app.all(
  ...trigger.http({
    route: '/SimpleHttpTrigger',
  }),
  c => {
    // Getting the function context
    const context = c.var.func;

    context.log('JavaScript HTTP trigger function processed a request.');
    context.log(`invocationid is: ${context.invocationId}`);
    context.log(`The third log message.`);

    return context.json({
      hello: 'world',
    });
  }
);

the result will be

{
    "hello": "world"
}

Note: This code is run with Azure Functions Host which is act like a reverse proxy forward request to Hono router

Or you can see all design interface in the Playground

[yusukebe]

cc: @Marplex

[mildronize]

Thank you so much @yusukebe, I'm really appreciate your work, extending Hono Framework is my best idea for maintaining the project which requires type-safe leveraging Hono type-inference system.

[yusukebe]

Hi! Honestly, I'm not very familiar with Azure Functions, so I'd be happy if the developers who are using Azure Functions would discuss it here!

[Marplex]

Hi! So if I understand this correctly, the standard azure functions library won't bundle with esbuild. You're bypassing this problem by not using the library at all, and using a custom handler that runs the script with Bun. Is this correct?

[mildronize]

Yes, it's correct, in V3 I don't use Azure Functions Node.js v4 anymore, just simple custom handler like go, rust lang,
However, i need to handle a lot of stuff behind the scene.

It almost close to Nammatham v1 thats consume only type from Azure Functions Node.js v3, it needs to handle function.json generation

[Marplex]

Hi! So if I understand this correctly, the standard azure functions library won't bundle with esbuild. You're bypassing this problem by not using the library at all, and using a custom handler that runs the script with Bun. Is this correct?