Update react-i18next 16.5.8 → 17.0.11 (major)#3584
Open
depfu[bot] wants to merge 1 commit into
Open
Conversation
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
This file contains hidden or 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
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.
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ react-i18next (16.5.8 → 17.0.11) · Repo · Changelog
Release Notes
Too many releases to show here. View the full release notes.
Commits
See the full diff on Github. The new version differs by 54 commits:
17.0.11buildchore: html-parse-stringify ^4.0.1 + 17.0.11 changeloghtml-parse-stringify ^4.0.0: replace escapeLiteralLessThan with the parser's allowedTags optionci: types-compat falls back to latest when no @types/react pre-release tag exists17.0.10buildchore: sync package-lock with i18next ^26.2.0 devDependency bumpimprove instance warnings (monorepo hint) + dev-only suspense warning + weekly @types/react@next compat workflow17.0.9fix: support typescript 7 — widen peer range and fix Trans ns inference under TS7 (#1927)README: mention npx i18next-cli localize as the zero-to-localized path17.0.8update i18next depchangelog: 17.0.8 entry for #1921fix(types): accept selector i18nKey on <Trans> under enableSelector: 'strict' (#1921)Add Locize advice section near the top of README17.0.7feat: useTranslation([nsA,nsB]) routes selector secondary-ns prefix via getFixedT scopeNs (i18next#2429)Modernize locize.com URLs and refresh UTM tags17.0.6fix: scope indexed placeholders inside keep-tags at render time #191917.0.5fix: <Trans /> no longer breaks child rendering when a kept HTML node (transKeepBasicHtmlNodesFor) wraps a non-keep React element #1919chore: ignore .env*, *.pem, *.key in .gitignore17.0.4fix: avoid `React does not recognize the i18nIsDynamicList prop on a DOM element` warning #191517.0.3fix: avoid invalid prop on `React.Fragment` inside `<Trans />` #191417.0.2fix(types): `values` prop on `<Trans />` now only requires interpolation variables for the specific `i18nKey`, not all variables in the namespace #1913l10n: add Swedish language support to examples (#1912)17.0.1chore: bump minimum i18next peer dependencyupate github actions17.0.0fix: `transKeepBasicHtmlNodesFor` now correctly preserves HTML tag names when children contain interpolations or mixed content16.6.6fix(peer-deps): bump i18next peer dependency to `>= 25.10.9` to match required type exports (`ConstrainTarget`, `ApplyTarget`, `GetSource`) used by `TransSelector` #191116.6.5fix(types): selector keyPrefix overload in `useTranslation` no longer matches when `keyPrefix` is absent, fixing `defaultNS: false` with explicit `ns` option https://github.com/i18next/i18next/issues/241216.6.4allow TypeScript 6 as peer dependency #191016.6.3fix #190916.6.2address: https://github.com/i18next/i18next/issues/236716.6.1feat(types): i18nKey of `<Trans i18nKey={sk} />` to accept a `SelectorKey`update i18next dep16.6.0type-safe `values` prop on `<Trans />` component — interpolation variables are now inferred from the translation string when custom types are configured #1772warn when `t` is called before `ready` with `useSuspense: false` #1896update deps and adjust testsDepfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands