Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Migrate to react-i18next v10
See original GitHub issueAs per discussion in #162, we’ll need to make core/breaking changes (internally) to upgrade to react-i18next v10. The end-user API should remain the same (as react-i18next, anyways).
Issue Analytics
- State:
- Created 5 years ago
- Comments:23 (16 by maintainers)
Top Results From Across the Web
Migrating v9 to v10 - react-i18next documentation
This is a specific migration guide regarding the complete react-i18next rewrite in v10. If you're looking for general release notes, please have a...
Read more >react-i18next-gitbook/migrating-v9-to-v10.md at master - GitHub
Migrating v9 to v10. v10 is a complete rewrite, taking the chance to clean up some complexity added from v1 to v9. This...
Read more >react-i18next - npm
Internationalization for react done right. Using the i18next i18n ecosystem.. Latest version: 12.1.1, last published: 19 days ago.
Read more >From react-i18next to Transifex Native: Migration Guide | CodeX
If you have your React application already internationalized (i18n) using React-i18next, there is a big chance you're thinking “why bother”?
Read more >react-i18next v10 without hooks - Stack Overflow
react -i18next v10 has been specifically refactored to work with hooks, so you'll need to either adapt your code to support hooks, ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’d say go for it, I’m ready for the update and besides some probable edge cases… there shouldn’t be much to worry about for anyone.
It’s been about two months since the React v16.8.0 release - how do people feel about me rolling this out?
It’d force all consumers to have their React peer dep at
>= 16.8.0. This is not the kind of peer dep discrepancy that will output warnings in youryarn installwhich you can ignore - it will be breaking.What version of React are consumers of this package using? Are people relatively up-to-date?