Don't use variables in NextJS middleware config

Guide how to fix the issue: "Next.js can't recognize the exported `config` field in route "/src/middleware": Unsupported template literal with expressions at "config.matcher[2]". The default config will be used instead."

When creating middleware for your Next.js application, configuring path matchers is essential to define which routes should be intercepted. In this tutorial, I demonstrate the importance of static path matching, especially when integrating features like Internationalization with the 'next-intl' library. While it may be tempting to use dynamic path patterns, Next.js documentation clearly states that middleware config cannot depend on variables. Learn why this restriction exists and how to avoid common errors when setting up your middleware configuration.

Видео Don't use variables in NextJS middleware config канала Blue Cell