Loading
fix(deps): update i18next
This MR contains the following updates:
| Package | Change | Age | Confidence |
|---|---|---|---|
| i18next (source) | ^25.8.12 → ^25.10.10 |
||
| i18next (source) | ^25.8.12 → ^25.10.10 |
||
| i18next-http-backend | ^3.0.2 → ^3.0.4 |
Release Notes
i18next/i18next (i18next)
v25.10.10
- feat: suppress support notice automatically in production environments (
NODE_ENV=production)
v25.10.9
- feat(types): export
SelectorParam<Ns, KPrefix>helper type — a stable, readable alternative toParameters<TFunction<Ns>>[0]for typing selector function props 2414
v25.10.8
- fix(types): reorder
TFunctionSelectoroverloads soParameters<TFunction>resolves to the general selector signature instead of the brandedSelectorKeytype 2412
v25.10.7
- feat(types): support typescript 6 to address i18next/react-i18next#1910
v25.10.6
- feat(types): support typescript 6 to address i18next/react-i18next#1910
v25.10.5
- feat(types): selector functions as
keyPrefixingetFixedTnow provide full type-safe key narrowing — the returnedtfunction is scoped to the prefix subtree 2367
v25.10.4
- feat(types):
exists()is now a type guard that narrows the key toSelectorKey, so a validated key can be passed directly tot()2364
v25.10.3
- check also for I18NEXT_NO_SUPPORT_NOTICE env variable
v25.10.2
- feat(types):
keyFromSelectoris now type-safe — the selector callback is constrained against your resource definitions, catching invalid keys at compile time. Supports optionalnsandkeyPrefixoptions for non-default namespace/prefix contexts 2364
v25.10.1
- feat: suppress support notice automatically in production environments (
NODE_ENV=production)
v25.10.0
- feat(types):
keyFromSelectornow returns a brandedSelectorKeytype thatt()accepts directly, enabling pre-computed and reusable translation keys 2364 - feat: support selector syntax for
keyPrefixingetFixedTand per-call options 2367 - feat(types): interpolation values are now automatically typed based on built-in format specifiers —
{{val, number}}requiresnumber,{{val, datetime}}requiresDate,{{name}}requiresstring, etc. Custom formatters can be typed viainterpolationFormatTypeMapinCustomTypeOptions2378 - fix(types):
FilterKeysin selector mode now preserves non-context, non-plural leaf keys whencontextis provided, fixing incorrect type narrowing when combiningreturnObjects: truewithcontext2398
v25.9.0
- feat(types): selector API now enforces
{ count: number }when a key resolves to plural forms 2373 - fix(types): string unions with invalid members are now correctly detected as type errors when used as context option 2172
v25.8.20
- fix:
getFixedT()selector now resolves namespaces against the effectivensrather than the global init options 2406
v25.8.19
- fix: selector API namespace resolution regression for single-string
nsand primary namespace in array 2405. Reverts the broad namespace-prefix rewrite from v25.8.15 and replaces it with a targeted fix that only rewrites paths starting with a secondary namespace in a multi-namespace array, matching the type-level contract ofGetSource
v25.8.18
- improve selector api to accept array of selector functions, analogous to array of keys 2404
v25.8.17
- update deps
v25.8.16
- fix(types):
on()method now correctly returnsthisinstead ofvoid, matching the runtime behavior and enabling proper method chaining in TypeScript
v25.8.15
- fix: Selector API unable to resolve namespaces 2402
v25.8.14
- fix: getCleanedCode now replaces all underscores
v25.8.13
- improve support notice shown logic
Configuration
- Branch creation
- At any time (no schedule defined)
- Automerge
- At any time (no schedule defined)
- If you want to rebase/retry this MR, check this box
This MR has been generated by Renovate Bot.
Edited by Ghost User