Update React (major)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
react-i18next	11.18.6 -> 15.2.0
react-native-url-polyfill	1.3.0 -> 2.0.0

---

Release Notes

i18next/react-i18next (react-i18next)

v15.2.0

Compare Source

This version may be breaking if you still use React < v18 with TypeScript.
For JS users this version is equal to v15.1.4

• fix: Global JSX namespace is deprecated 1823 with 1822

v15.1.4

Compare Source

• Fix: warning each child should have a unique key 1820

v15.1.3

Compare Source

• fix: Self-closing REACT components in translation strings should not attempt to replace the component's children 1815 1816

v15.1.2

Compare Source

• fix: Attempted to assign to readonly property 1813

v15.1.1

Compare Source

• fix: Not all namespaces are loaded when passing the lng option to useTranslate 1809

v15.1.0

Compare Source

• fix: <Trans /> warns 'Each child in a list should have a unique "key" prop.' for react 19 1806

v15.0.3

Compare Source

• try to fix unexpected token issue

v15.0.2

Compare Source

• try to fix Trans handling with alwaysFormat set to true 1801

v15.0.1

Compare Source

• revert arrow function in class property to address this

v15.0.0

Compare Source

• use optional chaining, nullish coalescing and nullish coalescing assignment 1774
• Build config and optimizations 1769
• some dependency updates 1768
• use modern hasLoadedNamespace code (now requires at least i18next > v19.4.5 (introduced in june 2020))

v14.1.3

Compare Source

• create a isObject helper function 1766
• optimize nodesToString 1765
• Simplifies hasValidReactChildren 1764
• create a isString helper to avoid code duplication 1763
• use arrow functions where possible 1762
• use the commented out async code 1761

v14.1.2

Compare Source

• bring back internal interpolationOverride handling for Trans component (if there are childrens), fixes 1754

v14.1.1

Compare Source

• do not modify passed tOptions context property to address 1745

v14.1.0

Compare Source

• types(Trans): add typechecking on context prop 1732 (might brake if using "internal" Trans or TransProps)

v14.0.8

Compare Source

• fix: issue 1728 when useSuspense is false and default ns 1731

v14.0.7

Compare Source

• try to get rid of internal interpolationOverride handling for Trans component, fixes 1729

v14.0.6

Compare Source

• align context handling of Trans component with t function, fixes 1729

v14.0.5

Compare Source

• Fix 1691 for strict mode, by preserving change language binding 1720

v14.0.4

Compare Source

• fix interpolation of the count prop 1719

v14.0.3

Compare Source

• revert changes done in v14.0.2 since it breaks normal language change render updates

v14.0.2

Compare Source

• Fix/bug 1691 make returned t function identical upon second effect run in strict mode 1716

v14.0.1

Compare Source

• types: fix typo in CustomInstanceExtensions 1713

v14.0.0

Compare Source

• types: reportNamespaces is now optional, should fix 1693

v13.5.0

Compare Source

• self-closing components in translation strings should not attempt to replace the component's children 1695

v13.4.1

Compare Source

• types: use CustomInstanceExtenstions to extend reportNamespaces

v13.4.0

Compare Source

• fix: separate cjs and mjs typings

v13.3.2

Compare Source

• types: fix consider importing '*.js'

v13.3.1

Compare Source

• optimize defaultVariables feature introduced in last release

v13.3.0

Compare Source

• Respect defaultVariables in the interpolation options 1685

v13.2.2

Compare Source

• Fix missing TransWithoutContext type 1672

v13.2.1

Compare Source

• types: Allow iterable ReactI18NextChildren as children 1669

v13.2.0

Compare Source

• Don't use defaults prop as default key 1664

v13.1.2

Compare Source

• postpone usage of newer ES syntax

v13.1.1

Compare Source

• Render all children regardless of type when using i18nIsDynamicList prop 1661

v13.1.0

Compare Source

• Fix non-list dynamic content in Trans component 1660

v13.0.3

Compare Source

• fix unescape is not consistently called for all values 1657

v13.0.2

Compare Source

• export icu.macro 1652

v13.0.1

Compare Source

• types: Fix performance issue in Trans component 1646

v13.0.0

Compare Source

• Update types to support t function redesign 1615
• requires i18next >= v23.0.1

v12.3.1

Compare Source

• optimization for optional lng prop for useTranslation, should now prevent missings when lazy loading translations 1637

v12.3.0

Compare Source

• optional lng prop for useTranslation (helping on server side 1637)

v12.2.2

Compare Source

• try to fix conditional exports in package.json

v12.2.1

Compare Source

• type fix: the type of defaultNS in I18nextProvider should support string[] 1633

v12.2.0

Compare Source

• if defaultValue is passed in not ready t functio (via useTranslation) return that instead of the key, even though the user-land could should be fixed 1618

v12.1.5

Compare Source

• fix react merged types 1606 originally introduced with #​1531 to address #​1506

v12.1.4

Compare Source

• fix crash in gatsby 1594

v12.1.3

Compare Source

• fix fallback of t function in Trans component

v12.1.2

Compare Source

• fix crash in gatsby 1594

v12.1.1

Compare Source

• fix for node resolution 1589

v12.1.0

Compare Source

• context-less version of Trans component to be used for environments without react context 1588

v12.0.0

Compare Source

• Update t function types to rely on types coming from i18next 1501

charpeni/react-native-url-polyfill (react-native-url-polyfill)

v2.0.0

Compare Source

Highlights

⚠️ It was released as a major version because it contains significant changes, but we don't expect any breaking changes. The upgrade should be seamless.

Official support for Expo & web.

We're now testing react-native-url-polyfill against latest versions of Expo to prevent any issues.

Also, previously, relying on react-native-url-polyfill/auto would also apply the polyfill if executed on the web (e.g., via react-native-web). Starting from now, react-native-url-polyfill/auto won't apply on the web platform and will be a no-op. If you would like to still apply it on web, you'll need to rely on setupPolyfill directly as such:

import { setupURLPolyfill } from 'react-native-url-polyfill';

setupURLPolyfill();

Moving away from React Native's internals

To better support different versions of React Native and web usages, we moved away from using polyfillGlobal, which is part of React Native's internals. Instead, we use globalThis. See https://github.com/charpeni/react-native-url-polyfill/pull/373 and https://github.com/charpeni/react-native-url-polyfill/pull/413.

What's Changed

• Remove usage of RN's polyfillGlobal by @​charpeni in https://github.com/charpeni/react-native-url-polyfill/pull/373
• Fix a phrasing issue in README by @​plbrault in https://github.com/charpeni/react-native-url-polyfill/pull/442
• Add test for Expo 48 by @​charpeni in https://github.com/charpeni/react-native-url-polyfill/pull/453
• Use globalThis instead of global in auto.js by @​staltz in https://github.com/charpeni/react-native-url-polyfill/pull/413
• Fix Typescript error by @​raykle in https://github.com/charpeni/react-native-url-polyfill/pull/444
• Add bundle-size script by @​charpeni in https://github.com/charpeni/react-native-url-polyfill/pull/455
• Don't auto polyfill on web by @​charpeni in https://github.com/charpeni/react-native-url-polyfill/pull/456
• Only default export is available soon by @​charpeni in https://github.com/charpeni/react-native-url-polyfill/pull/458

New Contributors

• @​plbrault made their first contribution in https://github.com/charpeni/react-native-url-polyfill/pull/442
• @​staltz made their first contribution in https://github.com/charpeni/react-native-url-polyfill/pull/413
• @​raykle made their first contribution in https://github.com/charpeni/react-native-url-polyfill/pull/444

Full Changelog: charpeni/react-native-url-polyfill@v1.3.0...v2.0.0

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

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

---

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

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 60.21%. Comparing base (a6ef6b1) to head (4a53c83).
Report is 11 commits behind head on master.

❗ Current head 4a53c83 differs from pull request most recent head dbcbf9e

Please upload reports for the commit dbcbf9e to get more accurate results.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #469   +/-   ##
=======================================
  Coverage   60.21%   60.21%           
=======================================
  Files          46       46           
  Lines         945      945           
  Branches      189      189           
=======================================
  Hits          569      569           
  Misses        341      341           
  Partials       35       35           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud