Skip to content

chore(deps): update dependency react-i18next to v16.6.6#313

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/react-i18next-16.x-lockfile
Open

chore(deps): update dependency react-i18next to v16.6.6#313
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/react-i18next-16.x-lockfile

Conversation

@renovate

@renovate renovate Bot commented Jun 3, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
react-i18next 16.5.416.6.6 age confidence

Release Notes

i18next/react-i18next (react-i18next)

v16.6.6

Compare Source

  • fix(peer-deps): bump i18next peer dependency to >= 25.10.9 to match required type exports (ConstrainTarget, ApplyTarget, GetSource) used by TransSelector 1911

v16.6.5

Compare Source

  • fix(types): selector keyPrefix overload in useTranslation no longer matches when keyPrefix is absent, fixing defaultNS: false with explicit ns option 2412

v16.6.4

Compare Source

  • allow TypeScript 6 as peer dependency 1910

v16.6.3

Compare Source

  • fix(types): merge TransSelector overloads into a single signature so typeof Trans remains extendable 1909

v16.6.2

Compare Source

  • feat(types): useTranslation now accepts selector functions as keyPrefix with full type-safe key narrowing when enableSelector is enabled 2367

v16.6.1

Compare Source

  • feat(types): i18nKey of <Trans i18nKey={sk} /> to accept a SelectorKey 2364

v16.6.0

Compare Source

  • warn when t is called before ready with useSuspense: false 1896
  • type-safe values prop on <Trans /> component — interpolation variables are now inferred from the translation string when custom types are configured 1772

v16.5.8

Compare Source

  • A selector function cannot be resolved without an i18n instance... returning empty string is safer than leaking the raw function reference. 1907

v16.5.7

Compare Source

  • fix: <Trans> component with enableSelector: true does not support multiple selectors for fallbacks 1907

v16.5.6

Compare Source

  • fix: prevent crash in useSSR when init() hasn't been called before useSSR — now logs a warning instead of throwing 1604

v16.5.5

Compare Source

  • fix: prevent crash in useSSR, getInitialProps and Translation when no i18next instance is available (e.g. in monorepo setups with duplicate react-i18next copies) — now logs a clear warning instead of throwing 1604

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Between 02:00 AM and 02:59 AM, between day 1 and 3 of the month, Monday through Friday (* 2 1-3 * 1-5)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants