astro-i18next: Translation doesn't work, it shows a key instead of translated text.

Adding the following configuration to the astro-i18next.config has helped:

  i18nextServer: {
    backend: {
      loadPath: './public/locales/{{lng}}/{{ns}}.json',
    },
  },

The code at line 78 works incorrectly at least on Windows:

fileURLToPath(config.publicDir) + "locales/{{lng}}/{{ns}}.json",

Still seeing this issue when deploying to Vercel

[!IMPORTANT] To solve this simply add the following to the file astro-i18next.config.mjs:

import en from "./public/locales/en/translation.json" assert {type: "json"};
import es from "./public/locales/es/translation.json" assert {type: "json"}; // other example

export default {
    i18nextServer: {
        resources: {
            en: {
                translation: {
                    ...en
                }
            },
            es: { // other example
                translation: {
                    ...es
                }
            }
        },
    }
};

Adapt the code as you need it, don’t forget variables like defaultLocale and locales

Got rid of the fsBackend plugin and added the resources object, and now everything is working. But I hope it’s a temporary solution and the issue will be fixed in the further releases…

Still seeing this issue when deploying to Vercel

Fixed my deploy on Vercel by adding includeFiles in my adapter settings:

  adapter: vercel({
    includeFiles: ["./public/locales/en/translation.json", "./public/locales/pt/translation.json"],
  }),