The plugin thinks the locale is set to undefined for localizePath()

[itsmatteomanf]

Describe the bug

Starting from the latest, v1.0.0-beta.18 release, all instances of localizePath() (at least, do not use other variations, but most depend on this) assume that the current locale is undefined, unless I manually add it in the function call, after the URL.

localizePath("/search") fails, localizePath("/search", "es") works.

To Reproduce

1. check any repo that uses localizePath() with a locale in the locales key in the plugin's config file (in my case this is the default locale, too), as it should be configured per the instructions (including the i18next.changeLanguage() at the top of the Astro file).
2. verify in the console the error, "WARNING(astro-i18next): "undefined" locale is not supported, add it to the locales in your astro config.".
3. all instances of localizePath() will return wrongly formatted URLs, missing the language part completely).

Expected behavior

It should get the current locale, which is correctly set (I checked, i18next.language returns the correct one) and use it if not set manually as it did previously.

Context (please complete the following information):

• astro-i18next version: v1.0.0-beta.18
• astro version: 2.0.16

Possible fixes

The issue seems to be related to the check here, which fails, haven't yet figured out where it went wrong, but it's definitely in the commits between v1.0.0-beta.17 and v1.0.0-beta.18.

astro-i18next/src/utils.ts

Line 238 in aa5f1c9

`WARNING(astro-i18next): "${locale}" locale is not supported, add it to the locales in your astro config.`

[loadbrain]

Same behaviour on my project, same context as mentioned above.

[Akasiek]

Same in my project. I fixed it by using i18next.langauge property in the second argument of localizePath() function, like so:

import i18next from "i18next";
import { localizePath } from "astro-i18next";

// ...

localizePath(link, i18next.language)

[ferrarafer]

Same behavior on my project, same context as mentioned above.

[itsmatteomanf]

Same in my project. I fixed it by using i18next.langauge property in the second argument of localizePath() function, like so:

import i18next from "i18next";
import { localizePath } from "astro-i18next";

// ...

localizePath(link, i18next.language)

I knew it was possible to fix this @Akasiek, but I have tens and tens of instances scattered across tens of files.
Can I do it? Sure.
Do I want to manually inject all of this? Nope, but I soon will have to if we don't get a reply/fix.

[yassinedoghri]

I'm guessing it's because I've set i18next as a peer dependency in beta.18. I'll look into it.

[itsmatteomanf]

@yassinedoghri I had to manually install it, after the update. It is installed, though.

[github-actions]

🎉 This issue has been resolved in version 1.0.0-beta.19 🎉

The release is available on:

• npm package (@beta dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[yassinedoghri]

Reverted to having i18next packaged with astro-i18next to have this fixed. Apparently the i18next instance is not shared with astro-i18next otherwise, thus the undefined.

[theprobugmaker]

@yassinedoghri For some reason I'm still getting this problem:

[...page].astro:

---
import i18next, { changeLanguage } from "i18next";
import { localizePath } from "astro-i18next";
import { getCollection } from "astro:content";
import Layout from "../../layouts/Layout.astro";

export async function getStaticPaths({ paginate }) {
  changeLanguage("en");

  const posts = await getCollection("blog", ({ id }) =>
    id.startsWith(i18next.language)
  );

  return paginate(posts, {
    pageSize: 1,
  });
}

const { page } = Astro.props;

const example = localizePath(`blog/${page.data[0].slug.split("/").slice(1).join("/")}`)

console.log(example);
---

WARNING(astro-i18next): "undefined" locale is not supported, add it to the locales in your astro config.

  "dependencies": {
    "@astrojs/mdx": "^1.0.0",
    "astro": "^3.0.7",
    "astro-i18next": "1.0.0-beta.21",
    "i18next": "^23.4.6",
    "i18next-fs-backend": "^2.1.5"
  }

[theprobugmaker]

I just noticed that it happens because of the i18next version 23+

[amosbastian]

I am getting this issue too

"astro-i18next": "1.0.0-beta.21",
"i18next": "^23.7.11",
"i18next-fs-backend": "^2.3.1",
"i18next-http-backend": "^2.4.2",