I18n Implementation - NextJS v14 404 & Middleware Errors

[angeloashmore]

Hi @damian.connolly, thank you for providing lots of details.

Could you take a look at this thread and give the recommended solution a try?

Long TTFB on multilangual site. Prismic cache bug (probably)

Hi @Vladyslav.L, thank you for your patience. We have an update. As you discovered, websites supporting multiple locales using createLocaleRedirect from @prismicio/next always have a 200ms-500ms TTFB delay. We found this happens because createLocaleRedirect fetches all of a Prismic repository's locales. The list of locales is used to detect and, if needed, prefix a locale to the URL. Unfortunately, fetch calls made in middleware.js are not cached like calls in your website's pa…

Our i18n documentation and start is out dated as we did not decide on a final direction internally, but what is described in that thread can be used today.

Notably, you can make the following changes to your setup:

• Remove the i18n property and the local-related lines from next.config.js. The i18n property is designed for the Pages Router, which your website does not seem to use.
• Remove the createClient() and client.getRepository() lines from middleware.ts. Fetching a repository's locale in middleware will cause every page to be delayed by ~300 ms, which should be avoided if possible.

I hope that helps! We are aware that we need to update our i18n and clarify the setup.