Examples updated to latest i18next #2058
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@adrai Thx for the i18next fix ! I feel it's relatively safe to prep the release 13.0.1 once I've merged. |
|
v13.0.1 is published... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A bug regarding key typings haven introduced in i18next v22.4.0. It's now fixed in latest
^22.4.3(upstream dep)If you are experiencing errors such as
TS2746: This JSX tag's 'children' prop expects a single child of type 'ReactI18NextChild | Iterable ', but multiple children were provided......simply ensure i18next is at version
^22.4.3in your package.json and run install.