React-intl seems overly complex and I find its documentation confusing, react-localisation looks simpler.
React-i18next by itself is relatively lite but it relies on i18next which is heavyweight.
Related libraries: [react-i18next vs react-intl vs react-localization vs react-localize-redux | npm trends](https://npmtrends.com/react-i18next-vs-react-intl-vs-react-localization-vs-react-localize-redux).
React-intl seems overly complex and I find its documentation confusing, react-localisation looks simpler.
React-i18next by itself is relatively lite but it relies on i18next which is heavyweight.
> The size and simplicity of react-localisation is such that I could probably fork the library and update it if needed.
That's been proven true, see [More robust support of objects in localization defs · Issue #31 · stefalda/localized-strings](https://github.com/stefalda/localized-strings/issues/31) !
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Related libraries: react-i18next vs react-intl vs react-localization vs react-localize-redux | npm trends.
React-intl seems overly complex and I find its documentation confusing, react-localisation looks simpler.
React-i18next by itself is relatively lite but it relies on i18next which is heavyweight.
The size and simplicity of react-localisation is such that I could probably fork the library and update it if needed.
That's been proven true, see More robust support of objects in localization defs · Issue #31 · stefalda/localized-strings !
In progress