📜 Plans for v1.0.0 release

astro-i18next is currently in beta. Before releasing v1.0.0, some things need to be worked out, mainly to improve DX.

Developers should be able to translate their Astro website / app as fast as possible --> reduce manual tasks to setup / use the integration.

Roadmap:

• add i18next plugins to config 👉 removed in beta.13, astro-i18next takes care of the basic stuff (loading translation strings, locale detection, etc.) 👉 added back in beta.14 (https://github.com/yassinedoghri/astro-i18next/commit/5ddb1c779367148fb0e690cd6503cba32d2bee59)
• npx astro-i18next generate: generate localized pages using command (based on config file) (https://github.com/yassinedoghri/astro-i18next/issues/13)
• Translate routes, possible thanks to @Alexandre-Fernandez ! 👉 Having routes.json files alongside pages would be best for i18n collaboration (#29)
• Hot Module Reloading localized pages instead of running the npx astro-i18next generate command manually. ❌ MAYBE NO NEED: Probably by creating a Vite plugin and adding it to the astro:config:setup hook. 👉 use astro’s injectRoute function in the astro:config:setup to inject localized routes during build time. The generate CLI tool would most probably be discarded. pages folder wouldn’t need to include localized pages anymore!
• Test support for SSR ✅ Works with node adapter ❌ Doesn’t work with Netlify yet: https://github.com/yassinedoghri/astro-i18next/issues/26 - Reproduction 👉 Missing support for Deno
• Test client side i18n support ✅ Works with react 👉 try out with other frontend frameworks
• npx astro-i18next extract: extract the translation keys using the i18next-parser + @astrojs/compiler
• npx astro-i18next init: automatic astro-i18next setup / config
• Move the documentation from README.md to the website
• Release v1.0.0 🚀

---

EDIT 2022-11-06: beta.13 is now out and I’m getting closer to a clean and simple API for everyone. Any feedback is welcome!

[aFuzzyBear]

if there anything you need from us just let me know @yassinedoghri 👊

[yassinedoghri]

Is there any documentation for supporting plugins again? Using i18next-decode-postprocessor has been crucial for avoiding loading translated strings with special characters as html, e.g. via dangerouslySetInnerHTML.

Not in beta.13. I’ll add support for plugins in the next release. Sorry for the trouble.

Edit: it’s back on beta.14