Middleware triggered without matching "matcher"
Unanswered
Ghost ant posted this in #help-forum
Ghost antOP
I have created a middleware.ts file inside my src directory.
I'm on nextjs 15.3. When i run next dev my middleware is triggered for all routes. Not just /a/
Feels like a bug? Or I'm totally misunderstanding something here
export const config = {
matcher: "/a/:path*"
} as MiddlewareConfig
export default function middleware(request: NextRequest) {
console.log(request.url)
}
I'm on nextjs 15.3. When i run next dev my middleware is triggered for all routes. Not just /a/
Feels like a bug? Or I'm totally misunderstanding something here