Route level middleware

[SuhelMakkad]

Goals

1. Allow the creation of route-level middleware
2. Similar to every segment having layout.ts and page.ts, the user can create middleware.ts on every segment
   middleware

Non-Goals

No response

Background

Current middleware supports most of the cases but it can get tricky to export matcher when we have nested routes.

Proposal

Goals

1. Allow the creation of route-level middleware
2. Similar to every segment having layout.ts and page.ts, the user can create middleware.ts on every segment
   middleware

Non-Goals

No response

Background

Current middleware supports most of the cases but it can get tricky to export matcher when we have nested routes.

Proposal

We can have an additional file as middleware.ts which will function the same as the current root level middleware.ts, but will get triggered for only child routes.

for example

├--/admin                
|  ├ /admin/middleware
|  ├ /admin/dashboard
|  ├ /admin/users
|  └ /admin/blogs
|
├--/user                
   ├ /user/middleware
   ├ /user/dashboard
   ├ /user/profile
   └ /user/items

/admin/middleware will get triggered for all the routes under /admin (/admin/dashboard, /admin/users, /admin/blogs.)
Similarly /user/middleware will get triggered for all the routes under /user (/user/profile, /user/items.)