Control of middleware execution order

[ghost]

Dears,

I wonder if there is a possibility to define middleware execution order. Like this

1. /middleware/auth.ts (adding user to context)
2. /middleware/protect.ts (protect route by throwing 403 if context.user.role is not eligible for the route)
   ...

Regards TJ

[misaon]

+1

[ghost]

So far, come to very simple workaround

// ~/server/middleware/index.ts
import authMiddleware from '../handlers/auth';
import logMiddleware from '../handlers/log';

export default defineEventHandler(event => {
  logMiddleware(event);
  authMiddleware(event);
});

// ~/server/handlers/log.ts
const logMiddleware = defineEventHandler(event => {
  if (!event.path?.includes('/api/v1')) {
    return;
  }

  console.log(event.node.req.method, event.path);
});
export default logMiddleware;

// ~/server/handlers/auth.ts
const authMiddleware = defineEventHandler(event => {
  event.context.user='foo'
});
export default authMiddleware;

~/server/middleware/index.ts can be (async event=>{}) as well.
Changing the order of the calls in index.ts solves the question.

I know it is simple - usually, I like simple solutions. Please tell me maybe I underseen something.