react
- In this introduction into the topic of automating your internationalization codebase we cover how to replace hard coded strings with translation functions. We use ts-morph to parse, navigate and manipulate the AST and the examples should provide a general idea on how to get started with your own i18n transformations.
- Ensure that your React i18next application has valid and up to date translations by using i18n-check. In this post we will go through how to setup and run the checks to ensure that no broken, missing or unused keys exit in your localization files.
- A collection of tips and tricks to get more out of i18next and react-i18next when using it with your application or website. This post covers a wide range of topics, including pluralization, React components, hooks, validation, TypeScript and much more.
- The blog post explains how to validate react-intl applications and ensure that all keys are in a valid state and no keys are missing or broken for all translations.
- Localizing your React application requires more than replacing strings, it has to consider date and time, numbers, pluralization, grammar and other requirements. This checklist should help with getting started with your internationalization efforts and avoid pitfalls and blockers.
- With TypeScript being the de-facto standard way to write React applications it only makes sense to expand type-checking to translations. In this post we explore the tradeoffs of type-safe translation keys.
