[dependabot]

Bumps the dependencies group with 5 updates:

Package	From	To
expo-dev-client	58.0.14	58.0.15
expo-image	58.0.16	58.0.17
i18next	26.5.7	26.5.10
react-i18next	17.1.5	17.1.8
@expo/cli	58.1.14	58.1.15

Updates expo-dev-client from 58.0.14 to 58.0.15

Release notes

Sourced from expo-dev-client's releases.

expo-dev-client@58.0.15

Patch Changes

• Updated dependencies. (#51670, #51669)
  • expo-dev-launcher@58.0.15

Changelog

Sourced from expo-dev-client's changelog.

58.0.15

Patch Changes

• Updated dependencies. (#51670, #51669)
  • expo-dev-launcher@58.0.15

Commits

• f6212ef Version packages (main) (#52021)
• See full diff in compare view

Updates expo-image from 58.0.16 to 58.0.17

Release notes

Sourced from expo-image's releases.

expo-image@58.0.17

Patch Changes

• [iOS] Fix bundled images not loading when the app compiles them into React Native's asset catalog with the RCTUseAssetCatalog Info.plist key. (#50723 by @​janicduplessis)

Changelog

Sourced from expo-image's changelog.

58.0.17

Patch Changes

• [iOS] Fix bundled images not loading when the app compiles them into React Native's asset catalog with the RCTUseAssetCatalog Info.plist key. (#50723 by @​janicduplessis)

Commits

• f6212ef Version packages (main) (#52021)
• a48b009 [image][ios] Load bundled images from React Native's asset catalog (#50723)
• See full diff in compare view

Updates i18next from 26.5.7 to 26.5.10

Release notes

Sourced from i18next's releases.

v26.5.10

• fix: when none of the detected languages is in supportedLngs, the best match no longer picks a different language whose code only starts with the same letters. The last fuzzy check took any supported code starting with the language part, so with supportedLngs: ['en', 'fil-PH'] a Finnish user (fi-FI) got Filipino instead of the fallback language, and ha (Hausa) picked haw-US (Hawaiian). Other regions of the same language still match as before (de-CH → de-DE, pt-PT → pt-BR, fil → fil-PH). Compatibility note: a two-letter code no longer matches a supported three-letter code that extends it, like ar → arz-EG, sw → swh-KE or no → nob-NO; list the two-letter code in supportedLngs (or map it with fallbackLng) if you relied on that. Thanks @​Pharex38 (#2460).

v26.5.9

• fix: nested lookups no longer resolve to methods inherited from the prototype, like constructor, toString or map. Only the top level was guarded, so {{constructor}} was treated as missing, but {{user.constructor}} rendered the function source (with a class instance, the full source code of the class), and {{user.toString}}, {{items.map}} or a class method like {{user.greet}} did the same. The same lookup is used for translation keys when ignoreJSONStructure is on (the default): a nested key named like an inherited method that is missing in the current language (t('roles.constructor') with roles.constructor only in the fallback language) returned function Object() { [native code] } instead of falling back, and exists('roles.valueOf') returned true. These keys are now missing, so the fallback language, missingInterpolationHandler, saveMissing and the missing key handler apply as for any other missing key. Getters defined on a class ({{user.fullName}} with get fullName()) still work. Nested lookups also no longer walk into the prototype via __proto__, so {{user.__proto__.constructor}} no longer prints the class source either. Thanks @​Pharex38 (#2459).

v26.5.8

• fix: arrays returned with joinArrays now get the same resolved details as strings. The joined value was extended with lastKey in the place of the resolved lookup, so with postProcessPassResolved a post processor got no usedLng, usedNS or exactUsedKey (t('steps', { joinArrays: ' / ' }) reported undefined/undefined:undefined). This affected the subliminal post processor used by the locize InContext editor, which could not map a joined array to its key. The nesting recursion guard did not get the parent key either, so arrays that nest each other (listA: ['a', '$t(listB)'], listB: ['b', '$t(listA)']) threw Maximum call stack size exceeded. They now stop at the guard, as strings do. An i18nFormat plugin with handleAsObject and parse also no longer throws Cannot read properties of undefined (reading 'usedNS') on joined arrays. Thanks @​nk-batman21 (#2458).

Changelog

Sourced from i18next's changelog.

26.5.10

• fix: when none of the detected languages is in supportedLngs, the best match no longer picks a different language whose code only starts with the same letters. The last fuzzy check took any supported code starting with the language part, so with supportedLngs: ['en', 'fil-PH'] a Finnish user (fi-FI) got Filipino instead of the fallback language, and ha (Hausa) picked haw-US (Hawaiian). Other regions of the same language still match as before (de-CH → de-DE, pt-PT → pt-BR, fil → fil-PH). Compatibility note: a two-letter code no longer matches a supported three-letter code that extends it, like ar → arz-EG, sw → swh-KE or no → nob-NO; list the two-letter code in supportedLngs (or map it with fallbackLng) if you relied on that. Thanks @​Pharex38 (#2460).

26.5.9

• fix: nested lookups no longer resolve to methods inherited from the prototype, like constructor, toString or map. Only the top level was guarded, so {{constructor}} was treated as missing, but {{user.constructor}} rendered the function source (with a class instance, the full source code of the class), and {{user.toString}}, {{items.map}} or a class method like {{user.greet}} did the same. The same lookup is used for translation keys when ignoreJSONStructure is on (the default): a nested key named like an inherited method that is missing in the current language (t('roles.constructor') with roles.constructor only in the fallback language) returned function Object() { [native code] } instead of falling back, and exists('roles.valueOf') returned true. These keys are now missing, so the fallback language, missingInterpolationHandler, saveMissing and the missing key handler apply as for any other missing key. Getters defined on a class ({{user.fullName}} with get fullName()) still work. Nested lookups also no longer walk into the prototype via __proto__, so {{user.__proto__.constructor}} no longer prints the class source either. Thanks @​Pharex38 (#2459).

26.5.8

• fix: arrays returned with joinArrays now get the same resolved details as strings. The joined value was extended with lastKey in the place of the resolved lookup, so with postProcessPassResolved a post processor got no usedLng, usedNS or exactUsedKey (t('steps', { joinArrays: ' / ' }) reported undefined/undefined:undefined). This affected the subliminal post processor used by the locize InContext editor, which could not map a joined array to its key. The nesting recursion guard did not get the parent key either, so arrays that nest each other (listA: ['a', '$t(listB)'], listB: ['b', '$t(listA)']) threw Maximum call stack size exceeded. They now stop at the guard, as strings do. An i18nFormat plugin with handleAsObject and parse also no longer throws Cannot read properties of undefined (reading 'usedNS') on joined arrays. Thanks @​nk-batman21 (#2458).

Commits

• 00b6a3f 26.5.10
• 9bdd4f6 build
• fb168f3 changelog for 26.5.10
• 2584a56 fix: don't match a supported language that only starts with the same letters ...
• 6c98e55 build
• 3465ae4 26.5.9
• 5888c16 changelog for 26.5.9
• db036c8 fix: don't walk into the prototype via proto in nested lookups
• 0815882 fix: don't interpolate inherited methods like constructor from nested values ...
• 45ae264 26.5.8
• Additional commits viewable in compare view

Updates react-i18next from 17.1.5 to 17.1.8

Changelog

Sourced from react-i18next's changelog.

17.1.8

• fix(Trans): an interpolation variable named format is no longer dropped. Trans reads format in an interpolation object as the formatter name ({{ value, format }}), so with {{ format }} as the only key nothing was left: <Trans>Export as {{ format }}</Trans> warned TRANS_INVALID_OBJ and used the default string Export as instead of Export as {{format}}. When format is the object's only key it is now treated as the variable. {{ value, format }} works as before. Without an i18nKey, the key derived from the children changes accordingly, from Export as to Export as {{format}}. i18next-cli serializes Trans children with react-i18next, so extracting with this version produces the same key. Thanks @​Pharex38 (#1944).

17.1.7

• fix(IcuTrans): each HTML entity in a translation is now decoded exactly once. Named, decimal and hexadecimal entities were decoded in three passes, and each pass decoded the output of the previous one, so an escaped numeric entity was decoded twice: "Write &[#169](https://github.com/i18next/react-i18next/issues/169); to get &[#169](https://github.com/i18next/react-i18next/issues/169);" rendered Write © to get © instead of Write &[#169](https://github.com/i18next/react-i18next/issues/169); to get ©, and &[#60](https://github.com/i18next/react-i18next/issues/60); rendered < instead of &[#60](https://github.com/i18next/react-i18next/issues/60);. This also hit interpolated values with escapeValue: true, where a value containing &[#60](https://github.com/i18next/react-i18next/issues/60); is escaped to &[#60](https://github.com/i18next/react-i18next/issues/60);. Escaped named entities like < already stayed <, as browsers and Trans decode them. Unknown named entities and entities above U+10FFFF still stay as written. Thanks @​Pharex38 (#1943).

17.1.6

• fix(Trans): a count passed in tOptions is now used. Trans spread tOptions and then set its own count prop, so a count only in tOptions was overwritten with undefined: <Trans i18nKey="items" tOptions={{ count: 5 }} /> rendered the key items instead of 5 items, and with children Trans could pick the wrong plural form. Like context, Trans now falls back to tOptions.count, handled the same way as the count prop. A count prop, a count in the children or values.count still take precedence, and tOptions is not modified. Thanks @​nk-batman21 (#1942).

Commits

• 3f0880e 17.1.8
• 9802f17 build
• fb5fa17 changelog for 17.1.8
• 63f4e41 fix(Trans): don't drop an interpolation variable named format (#1944)
• 8655c0f 17.1.7
• 5e2cf4a build
• 4745dc6 changelog for 17.1.7
• b708a76 fix(IcuTrans): decode each HTML entity only once (#1943)
• a8626e0 17.1.6
• c0cafdf build
• Additional commits viewable in compare view

Updates @expo/cli from 58.1.14 to 58.1.15

Release notes

Sourced from @​expo/cli's releases.

@​expo/cli@​58.1.15

Patch Changes

• Pass the matched route and its params to the server renderer. (#51961 by @​hassankhan)
• Updated dependencies. (4a6ae65, #51961)
  • @​expo/config@​58.0.8
  • @​expo/router-server@​58.0.17
  • expo-server@58.0.6
  • @​expo/prebuild-config@​58.0.16
  • @​expo/metro-config@​58.0.17

Changelog

Sourced from @​expo/cli's changelog.

58.1.15

Patch Changes

• Pass the matched route and its params to the server renderer. (#51961 by @​hassankhan)
• Updated dependencies. (4a6ae65, #51961)
  • @​expo/config@​58.0.8
  • @​expo/router-server@​58.0.17
  • expo-server@58.0.6
  • @​expo/prebuild-config@​58.0.16
  • @​expo/metro-config@​58.0.17

Commits

• f6212ef Version packages (main) (#52021)
• aa729f0 refactor(cli,router,router-server,server): avoid rebuilding navigation config...
• 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