<ul><li>Navigation using <Link> component in a Next.js project suddenly stopped working without clear error messages due to i18n configuration issues.</li><li>The problem was traced back to improper i18n setup in the next-i18next configuration file and next.config.js file.</li><li>The root cause was related to mishandling of locale routing, leading to full page reloads instead of client-side transitions.</li><li>The issue was fixed by ensuring clean implementation of i18n config, importing it correctly in next.config.js, and verifying consistency in locale settings.</li></ul>

How i18n in Next.js broke my route interceptors (and how I fixed it)

Discover more