Adding langs and namespaces exports

[YPetremann]

This proposal add langs and namespaces exports to the bundle. This would allow to automaticaly set supportedLngs and ns while being tree-shaked

- import resources from "virtual:i18next-loader";
+ import { langs, namespaces } from "virtual:i18next-loader";
  i18next.init({
-   supportedLngs: Object.keys(resources),
-   ns: Object.keys(resources.key),
+   supportedLngs: langs,
+   ns: namespaces,
    fallbackLng: ["en"],
    detection: {
      order: ["htmlTag"],
      caches: [],
    },
    backend: { loadPath: "/api/locales/{{lng}}/{{ns}}" },
  });

This is usefull when the resources should not be in the client bundle and loaded from other ways.

[rosskevin]

Thanks @YPetremann - can you add some tests for the new features?

[YPetremann]

(just for note, it's maybe not important but it bugs me, I don't know "auto shipit", what are the required steps to not get the release fail ?)

I will do it soon.

[YPetremann]

I updated the assertCommon of thoses tests files to check for langs and namespaces:
basic.test.ts // infer namespaces from files
namespaceResolverBasename.test.ts // infer namespace from basename
namespaceResolverRelativePath.test.ts // infer namespace from first segment of path

[rosskevin]

(just for note, it's maybe not important but it bugs me, I don't know "auto shipit", what are the required steps to not get the release fail ?)

I will do it soon.

Yeah, this bugs me too. I love the tool, but for outside contributors I haven't figured out the right combination. It is set up with trusted OIDC but only works when I push.

Thank you, and sorry for the delay.

[github-actions]

🚀 PR was released in v4.1.0 🚀