Better support for different middleware functions on different routes

[datteroandrea]

Describe the feature you'd like to request

I believe that being able of having multiple different middleware functions that work on different routes is needed, the current approach (see here) is not the best for code quality.

Describe the solution you'd like

We could create a middleware folder where we have multiple different middleware files that handle logic for different routes.
Also multiple different middleware can be run in the same route and there needs to be an order of execution of middlewares.

Describe alternatives you've considered

The current implementation, however it is not the best.

[alaato]

it is definitely more intuitive and makes it easier to make less complex api.

At least for me coming from express.js

[Oscar-AGUDELO]

Hope this can help you ! @datteroandrea

[alaato]

how would you handle the response?
for example i would like to show an error page that says that they are un authorized.
returning a response is just gonna give the json back.

[Oscar-AGUDELO]

I was planning to deal with error management later but I couldn't help but try it. The example is for a website with several languages but you can adapt it: @alaato

[alaato]

So, making an error route and redirecting there? I thought of it but i preferred to have the error page render on the same route.
Well, we gotta wait for that.
Thank you btw, it's good to see what others think

[Netail]

Maybe a solution where you can multiple middleware.ts files and will only apply to the routes/subroutes in which the middleware.ts is placed.

e.g.

app
├── page.tsx
├── layout.tsx
├── middleware.ts
├── stores
│   └── page.tsx
└── dashboard
    ├── page.tsx
    └── middleware.ts

where the middleware.ts in the root of the app directory applies to all routes and the middleware.ts in the dashboard only for the /dashboard and subpaths

[alaato]

According to the docs, You can't have more than one middleware, only one and it should be inside the root of the project, outside of app.
As far as I know

[Netail]

Correct for now, but mine was more of a proposal for the future of middlewares in NextJS 😅

[alaato]

Aah, my bad then 😅