Update dependency i18next to v19

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
i18next (source)	dependencies	major	15.0.9 -> 19.5.4

---

Release Notes

i18next/i18next

v19.5.4

Compare Source

• typescript fix: getDataByLanguage typings & test 1472
• typescript fix: type declarion of exposed EventEmitter#off methods 1460

v19.5.3

Compare Source

• fix Macedonian plural formula 1476

v19.5.2

Compare Source

• fix nesting interpolation with prepended namespace, fixes #​1474 1475

v19.5.1

Compare Source

• getBestMatchFromCodes: use fallbackLng if nothing found, fixes #​1470 1471

v19.5.0

Compare Source

• language detectors can return an array of languages and let i18next figure out best match

• rename option whitelist to supportedLngs

• rename option nonExpicitWhitelist to nonExplicitSupportedLngs

• rename function languageUtils.isWhitelisted to languageUtils.isSupportedCode

This changes are made with temporal backwards compatiblity and will warn your for deprecated usage of old terms to give users and plugin providers some time to adapt their code base.

The temporal backwards compatiblity will be removed in a follow up major release.

Learn more about why this change was made here.

v19.4.5

Compare Source

• Add store events to typings 1451

v19.4.4

Compare Source

• typescript: Allow passing retry boolean to ReadCallback 1439

v19.4.3

Compare Source

• fix regression introduced in "support formatting in nesting" 1419

v19.4.2

Compare Source

• fix for deno 1428

v19.4.1

Compare Source

• add getLanguagePartFromCode as in language fallback resolution 1424

v19.4.0

Compare Source

• support formatting in nesting 1419

v19.3.4

Compare Source

• fix cloning of service.utils binding to clone 1415

v19.3.3

Compare Source

• backendConnector extend initial retry from 250 to 350

v19.3.2

Compare Source

• fix the nested string options parsing introduced in v19.2.0 which broke having multiple options

v19.3.1

Compare Source

• typescript: add options.interpolation.nestingOptionsSeparator

v19.3.0

Compare Source

• Double fix for 1395 issue 1399
• adds options.interpolation.nestingOptionsSeparator: ',' to specify that separator

v19.2.0

Compare Source

• Add ability to use commas in nested keys 1398

v19.1.0

Compare Source

• explict warning when no languageDetector is used and no lng is defined 1381
• Add option to always format interpolated values 1385
• pass all options to format function 992#issuecomment-577797162

v19.0.3

Compare Source

• fixes retry interval in backend connector 1378

v19.0.2

Compare Source

• typescript: Type ResourceStore 1366

v19.0.1

Compare Source

• ignore non valid keys in saveMissing 1359

v19.0.0

Compare Source

• typescript: Typescript use export default for esm-first approach 1352

v18.0.1

Compare Source

• check loadedNamespace only once per lng-ns inside using t for better performance

v18.0.0

Compare Source

• When calling i18next.changeLanguage() both i18next.language and i18next.languages will be set to the new language after calling loadResources -> means when accessing t function meanwhile you will get still the translations for the previous language instead of the fallback.

• When is this breaking? this does not break any current test - but if you depend on accessing i18next.language or i18next.dir during language change and expect the new language this will break your app.

• Reasoning: In react-i18next we get in a not ready state for loaded translations while we would prefer just waiting for the new language ready and trigger a rerender then - also a triggered rerender outside of the bound events would end in Suspense...

• How can I get the language i18next will be set to? i18next.isLanguageChangingTo is set to the language called

v17.3.1

Compare Source

• typescript: Add missing cleanCode option to TypeScript def 1344

v17.3.0

Compare Source

• pass used language & namespace to postprocessor 1341

v17.2.0

Compare Source

• Support using ImmutableJS Records as the data model in interpolation 1339

v17.1.0

Compare Source

DX improvements:

• warning if accessing t before i18next was initialized or namespace loaded
• warning and cancelling save if saveMissing key before i18next was initialized or namespace loaded

Both are a clear sign you render your app / call t to early not waiting for the callbacks or Promise.resolve on i18next.init, i18next.loadNamespace or i18next.changeLanguage.

v17.0.18

Compare Source

• Improve performance of EventEmitter.off 1333

v17.0.17

Compare Source

• fixes: missing nested key fails if no nested value found and defaultValue contains interpolation -> results in endless loop 1332

v17.0.16

Compare Source

• typescript: fix incorrect callback type for backend module read callback 1322
• typescript: add getDataByLanguage into index.d.ts 1326

v17.0.15

Compare Source

• Fixed default value as string in IE 1325

v17.0.14

Compare Source

• typescript: Allow TFunction to receive 1-3 parameters 1317

v17.0.13

Compare Source

• fixes: Interpolation defaultVariables not recognized on t() 1314

v17.0.12

Compare Source

• remove unused Interpolator#init reset param (only used internally) 1313
• Cope with null interpolation (unescaped case) 1310

v17.0.11

Compare Source

• fix issue with unset value in interpolation throwing exception
• typescript: Allow augmentation of TFunction to be able to add overloads 1308

v17.0.10

Compare Source

• Update Interpolator.js to use regexSafe for unescaped interpolation 1307

v17.0.9

Compare Source

• typescript: use() should accept a class or object 1301

v17.0.8

Compare Source

• typescript: Correct use(module) types 1296

v17.0.7

Compare Source

• typescript: Typescript imports 1291
• Disabled default returnedObjectHandler 1288

v17.0.6

Compare Source

• support montenegrien "crn" plurals

v17.0.5

Compare Source

v17.0.4

Compare Source

• typescript: ResourceKey type should allow top level string value 1267

v17.0.3

Compare Source

• don't do named exports for umd

v17.0.2

Compare Source

• typescript: Allow null as TResult 1263
• bring back ./i18next.js and ./i18next.min.js -> used by wildcard unpkg users...<= bad idea doing so
• main export in package.json points to cjs dist

v17.0.1

Compare Source

• Improve performance of EventEmitter.off 1333

v17.0.0

Compare Source

• removes checking in build files (umd) into source code - for CDN usage use: https://unpkg.com/i18next@16.0.0/dist/umd/i18next.js
• removes named exports in main file - avoids issues in mixed exports makes usage better in commonjs scenarios (node.js) - no strange const i18next = require('i18next').default;
• impact you can't no longer import { changeLanguage } from 'i18next'; changeLanguage('de'); you will have to import i18next from 'i18next'; i18next.changeLanguage('de');
• note if can create a own file providing the named bound functions and use that instead, sample: https://github.com/i18next/i18next/blob/v15.0.0/src/index.js#L5

v16.0.0

Compare Source

• removes deprecated jsnext:main from package.json
• Bundle all entry points with rollup 1256
• note: dist/es -> dist/esm, dist/commonjs -> dist/cjs (individual files -> one bundled file)

v15.1.3

Compare Source

• typescript: Fix type error when init with locize plugin options 1248

v15.1.2

Compare Source

• typescript: types(ReactOptions): Add missing props to React Options interface 1247

v15.1.1

Compare Source

• typescript: Update BackendModule interface to allow null or undefined for the callback 1244

v15.1.0

Compare Source

• trigger a languageChanging event

v15.0.10

Compare Source

---

Renovate configuration

📅 Schedule: 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 has been generated by WhiteSource Renovate. View repository job log here.