Skip to Content

middleware.ts

middleware.ts runs before every handler in its folder and below, and can set access for the whole folder.

app/ ├── middleware.ts # every handler ├── orders/ │ └── get.ts └── (admin)/ ├── middleware.ts # only handlers in (admin)/ └── reports/get.ts

What it does

Middleware is for work many handlers share: logging, a request id, a header check. Sign-in and roles need no middleware: app/auth.ts resolves the user and access gates routes.

Order:

Request → resolve user (app/auth.ts) → app/middleware.ts → app/(admin)/middleware.ts → access check → handler

Exports

  • default (optional): one Hono middleware, or an array run left to right.
  • access (optional): applies to every handler below. A handler’s own access wins.

A file may hold just export const access = ["admin"];.

Example

app/(admin)/middleware.ts
import type { MiddlewareHandler } from "hono"; export const access = ["admin"]; const logger: MiddlewareHandler = async (c, next) => { const t = Date.now(); await next(); console.log(`${c.req.method} ${c.req.path} ${Date.now() - t}ms`, c.get("user")?.id ?? "-"); }; export default [logger];

Good to know

  • Middleware only applies downward: a file in app/orders/ doesn’t affect app/users/.
  • The user is resolved first, so middleware can read c.get("user"). access is checked after all middleware.
  • Stop a request with fail(...) from manh/errors; the caller gets { error, message, code }.
  • *.cron.ts, *.email.ts and *.telegram.ts don’t pass through middleware.
  • access takes literal values only: manh.run reads it without running it.
  • Don’t import manh/oauth. Deploy drops any app/middleware.ts that imports it.

Next steps

Last updated