- Pages Router: translations load on the server again with a custom
interpolation.prefix/suffix-localeStructureand the serverloadPathare built from the configured prefix and suffix (e.g.{lng}/{ns}), but the file loader that replaced i18next-fs-backend in 16.0.0 only replaced{{lng}}and{{ns}}. It tried to read a literalpublic/locales/{lng}/{ns}.json, the error only showed withdebug: true, andserverSideTranslationsreturned empty namespaces, so pages rendered the raw keys. The loader now uses the same prefix and suffix as the config. The default config and a functionlocalePathare unchanged. Thanks @nk-batman21 (#2350)