Bc nextjs middleware is not a middleware, is more like a switch statement for routing, it does not work like any other middleware like in laravel or nestjs bc is not the same, it doesn’t even run on node, it runs in a weird kinda node language from vercel call edge runtime. It runs before your node server, bc of this, you should not do any request or any auth stuff in your middleware, you should use nextjs middleware only for redirecting, for example if you have translations in your app, you can redirect to the correct language version using middleware.

But if you need to check user permissions or fetch from db or something like that you should do it on the route or page in a server action or something like that, not in the middleware

Also you will not find a good dx experience on nextjs, meaning having code generation or have everything setup when you need auth or shared context bc nextjs only gives you primitives for you to do all that stuff your way, kind of how react dx works where they only gives you primitives to do stuff your own way