How should the middleware matcher look like if the default locale is ommited?

[alexbuznik-stark]

Hi.

The default middleware matcher from the tutorial is matcher: ['/', '/(de|en)/:path*']

I want to support a web-site that has default locale ommited (en-US).

How should the matcher look like then?
Are the matchers applied in order?

My suggestion, but I'm still not sure it works well for all cases.

  matcher: [
    "/",
    `/(${locales.join("|")})/:path*`,
    "/:path*",
    '/((?!api|_next/static|_next/image|assets|favicon.ico|sw.js|site.webmanifest).*)',
  ],

[amannn]

You mean you're using localePrefix: 'as-needed'? This is the one that's suggested in the docs: Pathnames without a locale prefix

[amannn]

The example in the docs doesn't list all pathnames, right? It's a negative lookup that ignores certain paths, while explicitly mentioning those where a dot is expected.

Can you provide some examples?

[alexbuznik-stark]

Well, I'm a bit a confused with examples.

So the tutorial has this matcher:

  matcher: ['/', '/(de|en)/:path*']

Then, the example from the repo has this which lists root and paths localized:

  matcher: [
    // Enable a redirect to a matching locale at the root
    '/',

    // Set a cookie to remember the previous locale for
    // all requests that have a locale prefix
    '/(de|en)/:path*',

    // Enable redirects that add missing locales
    // (e.g. `/pathnames` -> `/en/pathnames`)
    '/((?!_next|_vercel|.*\\..*).*)'
  ]

[alexbuznik-stark]

So the question is it going to suffice the matcher with the negative lookup for the static assets to make it work on all paths with localePrefix: 'as-needed':

    matcher: ['/((?!_next|_vercel|.*\\..*).*)']

[amannn]

It depends on your app, have you read the section Pathnames without a locale prefix?

[alexbuznik-stark]

Thank you, I have seen it.