[dependabot]

Bumps the frontend-runtime group with 3 updates in the /XE-Local-AI-Engine.Client.React directory: i18next, i18next-browser-languagedetector and react-i18next.

Updates i18next from 26.5.6 to 26.5.7

Release notes

Sourced from i18next's releases.

v26.5.7

• fix: with the default cacheInBuiltFormats: true, built-in formats now also work when the t() options contain a BigInt or a circular object. The cache key was built with JSON.stringify over all options, including the interpolation values, which throws on those, so every built-in format in that call returned the raw value: t('num', { val: 12345678901234567890n }) with 'Total: {{val, number}}' returned 'Total: 12345678901234567890' instead of 'Total: 12,345,678,901,234,567,890', and passing an object with a back-reference (like an ORM entity) left all numbers, dates and lists of that call unformatted. When the key cannot be built, the value is now formatted without the cache, as with cacheInBuiltFormats: false. This also applies to formatters added with addCached. Other calls still use the cache as before. Thanks @​nk-batman21 (#2457).

Changelog

Sourced from i18next's changelog.

26.5.7

• fix: with the default cacheInBuiltFormats: true, built-in formats now also work when the t() options contain a BigInt or a circular object. The cache key was built with JSON.stringify over all options, including the interpolation values, which throws on those, so every built-in format in that call returned the raw value: t('num', { val: 12345678901234567890n }) with 'Total: {{val, number}}' returned 'Total: 12345678901234567890' instead of 'Total: 12,345,678,901,234,567,890', and passing an object with a back-reference (like an ORM entity) left all numbers, dates and lists of that call unformatted. When the key cannot be built, the value is now formatted without the cache, as with cacheInBuiltFormats: false. This also applies to formatters added with addCached. Other calls still use the cache as before. Thanks @​nk-batman21 (#2457).

Commits

• 21f3b52 26.5.7
• 35b1cf3 build
• d1ae940 changelog for 26.5.7
• 48ac091 fix: format values when cached formatter options are not serializable (#2457)
• See full diff in compare view

Updates i18next-browser-languagedetector from 8.2.1 to 8.2.2

Changelog

Sourced from i18next-browser-languagedetector's changelog.

8.2.2

• fix: the path and hash detectors keep digits in a language segment, so /es-419/ and #/es-419 are detected as es-419 instead of es- (which i18next resolved to es). Segments that start with a digit (/2024/) still yield no language, and lookupFromPathIndex / lookupFromHashIndex point at the same segments as before. Thanks @​nk-batman21 327

Commits

• 6e4fa01 8.2.2
• e66a3af release
• feedf66 fix: keep digits of region subtags in path and hash detection (#327)
• a05f0c5 Bump brace-expansion from 1.1.18 to 1.1.21 (#326)
• ca2366c Bump js-yaml (#325)
• b1edea5 Bump browserslist from 4.28.2 to 4.28.9 (#324)
• b4b823e docs: "For AI assistants" paragraph in the README
• 8d55454 chore: keep dev-only and local files out of the npm package
• fa858b6 Bump brace-expansion from 1.1.14 to 1.1.18 (#323)
• 4515f87 Bump @​babel/core from 7.29.0 to 7.29.6 (#321)
• Additional commits viewable in compare view

Updates react-i18next from 17.1.4 to 17.1.5

Changelog

Sourced from react-i18next's changelog.

17.1.5

• fix(Trans): with an array of keys and no children, Trans now falls back to the last key when none of them has a translation, as t() does. It used the array itself as defaultValue, which i18next handles as an object, so <Trans i18nKey={['notifications.crm_item_created', 'crm_item_created']} components={[<strong />]} /> rendered key 'crm_item_created (en)' returned an object instead of string. instead of crm_item_created. An array of selectors falls back to the key of the last selector. The first key that has a translation still wins, and children, defaults and tOptions.defaultValue are used as before. With saveMissing, these calls now report the missing key, like a single i18nKey does. Thanks @​nk-batman21 (#1941).

Commits

• 396dba9 17.1.5
• 3d18890 build
• c8a4924 changelog for 17.1.5
• 7724d5a fix(Trans): fall back to the last key of an i18nKey array, like t() (#1941)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.