No translations for routes using getServerSideProps

🐛 Bug Report

Nothing is being translated for any routes deployed to Vercel that are using getServerSideProps, they are however working fine for SSG. Everything is working as expected locally.

To Reproduce

next-i18next.config.js

const path = require("path");

module.exports = {
  i18n: {
    defaultLocale: "en",
    locales: ["en", "de", "fr"],
    reloadOnPrerender: process.env.NODE_ENV === "development",
  },
  localePath: path.resolve("./public/locales"),
};

pages/profile.tsx

export const getServerSideProps: GetServerSideProps =>
    ...
    return {
      props: {
        ... ,
        ...(await serverSideTranslations(locale!, ["common", "profile"])),
      },
    };
  },
});

const Profile = (
  context: InferGetServerSidePropsType<typeof getServerSideProps>
) => {
  const { t } = useTranslation("profile");
...

Expected behavior

Expected resolution of a key when using t("key")

Your Environment

• runtime version: v14
• i18next version: ^12.0.0

[c-schober]

Upgrade to the newest Next version and next-i18next version still leads to not found translations for us on catch all routes when deploying with vercel. Seems like that vercel changed some parts of their architecture.

[FBosler]

+1 this, We have been seeing similar behaviour since yesterday around 15:00