[Docs]: Middleware matcher with Next-Auth

[hakan-berat]

Link to page

https://github.com/amannn/next-intl/tree/main/examples/example-app-router-next-auth

Describe the problem

I am using Next-Auth and Next-Intl together. I have progressed smoothly with the codes in the example section. My auth mechanizm works correctly. But in my project, I have some cases where I need to intercept with middleware before the requests I make hit the api routes. But i think with the current matcher configuration this becomes impossible.

Because if I remove the 'api' from the matcher configuration the requests always go with the locale prefix but my api folder has to be outside [locale]. I would like to ask for your support on this issue,

Thanks.

---

middleware.js

import { withAuth } from 'next-auth/middleware'
import createMiddleware from 'next-intl/middleware'
import { locales } from './lib/config/routes.js'

const publicPages = [
  '/',
  '/login',
  '/register',
  '/list',
  '/cart',
  '/about',
]

const intlMiddleware = createMiddleware({
  defaultLocale: 'tr',
  locales,
  localePrefix: 'always',
})

const authMiddleware = withAuth((req) => intlMiddleware(req), {
  callbacks: {
    authorized: ({ token }) => token != null,
  },
  pages: {
    signIn: '/login',
  },
})

export default async function middleware(req, res) {
  //!!!The requests I go to api routes do not hit middleware.
  const pathname = req.nextUrl.pathname
  const publicPathnameRegex = RegExp(
    `^(/(${locales.join('|')}))?(${publicPages
      .flatMap((p) => (p === '/' ? ['', '/'] : p))
      .join('|')})/?$`,
    'i'
  )
  const isPublicPage = publicPathnameRegex.test(pathname)

  if (isPublicPage) {
    return intlMiddleware(req)
  } else {
    return authMiddleware(req)
  }
}

export const config = {
  matcher: [
    '/((?!api|_next|.*\\..*).*)',
    '/(tr|en)/:path*',
  ],
}

My app structure:

[amannn]

If you want to protect your Route Handlers with NextAuth, I guess you could change the matcher for them to pass also through the middleware, but add a condition within the middleware code to exclude them from running through the middleware from next-intl.

I'll move this to a discussion since it's a usage question.